Build events, offers, quests, and live config changes from one visual campaign workflow.
Simple changes take too many steps
Campaign ideas turn into client and backend tickets
Hard to know what's live right now
Scaling shouldn't mean rethinking everything
Can't rethink your setup once running
Every change requires too much caution
From campaign setup to an in-game result.
Build campaign flows visually. Drag, connect, and configure repeatable player journeys.
Set triggers, conditions, offers, rewards, and player targeting before going live.
Test in staging, publish to production, and roll back when a campaign needs a fix.
Each capability is designed to be demonstrated as a short loop: configure it in Rudder, publish it, then show the result in the game.
Build a player flow from triggers, conditions, waits, notifications, stores, and game-side actions.
Comeback offer, starter pack, tutorial reward chain, seasonal event branch.
Show a flow in the editor, trigger it from a mock player event, and display the client action.
Expose typed config values and switches that the client can fetch at runtime.
Event tile toggle, economy tuning, unstable feature kill switch, onboarding values.
Flip a config value and show the game UI reacting to the live setting.
Configure offer shelves, contents, prices, purchase limits, and segment-specific stores.
Weekend bundle, comeback shop, starter pack, high-value player store.
Publish a bundle and show the offer card appearing in the client shop.
Route players by attributes and split campaign branches for experiment workflows.
New players, inactive players, high-level players, offer treatment variants.
Run two mock players through one campaign and show different branches.
Track mission progress from player events and connect it to rewards.
Daily quests, onboarding steps, event tasks, comeback quest chain.
Publish a quest chain and show progress updates in the live client.
Model seasonal progression, levels, rewards, and free or premium tracks.
Season pass, event pass, milestone rewards, premium upgrade flow.
Show configured levels and a mock player unlocking a reward.
Create ranked event surfaces and update scores from the game.
Weekend tournament, seasonal ranking, guild challenge, score contest.
Submit a score and show the player rank update in the client.
Group content changes into releases and promote tested work between environments.
Season launch, event update, emergency revert, staging-to-production publish.
Promote a release, then restore the previous version if a change is wrong.
Staging and production completely separate. Test changes safely before going live.
Group multiple changes into a single release. Ship atomically or not at all.
Restore a previous release when a campaign change needs to be reverted.
Keep release history visible so the team knows what changed and what is live.
Fast, safe, predictable — every time.
Use SDKs to connect Unity, browser games, or a C# runtime to Rudder.
using RudderSdk.Unity;
using UnityEngine;
async void Start() {
await Rudder.Auth.LoginViaDeviceAsync();
await Rudder.RemoteConfig.LoadAsync();
var shopEnabled = Rudder.RemoteConfig.Get("shop_enabled", false);
Rudder.Scenarios.OnStore += store => {
Debug.Log($"Show store: {store.Id}");
};
await Rudder.Scenarios.SendAsync("player_login");
}import { LiveOpsClient } from "@rudder/web-sdk";
const rudder = new LiveOpsClient({
projectKey: "project-key",
baseUrl: "https://api.rudder.build",
realtimeUrl: "wss://realtime.rudder.build/api/realtime/ws"
});
await rudder.auth.loginViaDevice({ region: "eu", language: "en" });
await rudder.remoteConfig.load();
rudder.scenarios.on("store", session => showStore(session.id));
await rudder.scenarios.send("player_login");using RudderSdk.Core;
var rudder = new RudderClient(new RudderClientOptions {
ProjectKey = "project-key",
BaseUrl = "https://api.rudder.build",
RealtimeUrl = "wss://realtime.rudder.build/api/realtime/ws",
Transport = transport,
TokenStore = tokenStore
});
await rudder.Auth.LoginViaDeviceAsync();
await rudder.RemoteConfig.LoadAsync();Start lightweight, then move to a pilot when a game needs custom integration help.
Up to 1,000 MAU
Try a game integration
Up to 10,000 MAU
Small games going live
Up to 100,000 MAU
Growing live titles
For larger live games
Pilot help or custom limits
Pricing is early-access and will be adjusted from real game pilots.
Teams with live or soft-launch games that need real LiveOps without a platform team
Studios that want faster campaign iteration without turning each idea into a sprint
Operators who want to configure offers, quests, events, and tuning in one place
Integrate the SDK once, then move repeatable campaign logic into Rudder
Start with a concrete LiveOps flow: comeback offer, quest chain, seasonal event, or live config change.