The Campaigns page is where you create and manage LiveOps campaigns. A campaign is a scheduled, targeted event that automatically enrolls players and assigns each of them to one of its scenarios. Each scenario can override global properties, cash product prices, and item prices, so you can run themed events, limited-time sales, or A/B tests without deploying a new app build.
When an eligible player triggers a campaign (on login or on account creation), brainCloud randomly assigns them to a scenario based on the allocation percentages you configure. The Control scenario (code _) is the baseline: players in it get the normal, unmodified experience. Every other scenario is a variation you want to run or test against it.
LiveOps Campaigns are an Enterprise feature. If your app's plan does not include it, the page shows an Upgrade Plan... option instead.
Campaigns List
The main table lists all campaigns for your app with the following columns (all sortable):
Campaign Code: the unique code identifying the campaign (up to 15 characters, uppercase).
Name: the campaign's display name.
Scenarios: the number of scenarios in the campaign, including Control.
Purpose / Hypothesis: an optional description of the campaign's goal. Hover to see the full text.
Status: the campaign's current state (see Campaign Status below).
Start: when the campaign starts. Hover to see local and UTC times.
Duration: how long the campaign runs. Hover to see the end time.
Use the Search box to filter by Campaign Code or Name. Sort By Newest (on by default) lists the most recently created campaigns first, and the Refresh button reloads the list.
Campaign Status
Each campaign's status is based on whether it is enabled and on its schedule:
Disabled: not enabled, and the start time has not been reached yet.
Scheduled: enabled, waiting for its start time.
In Progress: enabled and currently running.
Suspended: disabled while it would otherwise be running.
Completed: enabled and its end time has passed.
Cancelled: its end time has passed while it was disabled.
Campaign Details Panel
Click any row to open the details panel on the right. It shows the campaign's Status, Start Time, End Time, Purpose / Hypothesis, Key Metric, Enrollment Trigger, Target Segment, and the allocation for each scenario. The panel's actions are:
View...: opens a read-only summary of the full campaign configuration.
Edit...: opens the campaign editor. Not shown for Completed campaigns.
View Analytics: opens the campaign's analytics (also available in a new tab). Not available until the campaign has started.
Clone...: creates a copy of the campaign (see Cloning a Campaign).
Enable / Disable: turns the campaign on or off.
Delete...: permanently deletes the campaign.
Creating a Campaign
Click New Campaign... to open the Create a New Campaign wizard. First, choose a setup type:
Themed Event: a scheduled theme or limited-time game mode for your whole target audience. Every enrolled player gets the same overrides.
A/B Test: one Control group plus up to 3 test groups, each with its own overrides, so you can compare which one performs better.
Advanced Setup: opens the full campaign editor with every option, including custom JSON data for the campaign and for each scenario. Click
Open Advanced...to continue.
For Themed Event and A/B Test, also tick which types of values you want to override: Global Properties, Cash Product pricing, and/or Inventory Item pricing. At least one is required. The wizard then walks you through these steps (only the steps that apply to your choices are shown):
Basic Information: Name (required, up to 50 characters), Campaign Code (required, up to 15 characters; letters, numbers, hyphens and underscores only; converted to uppercase; must be unique and cannot be changed later), Purpose / Hypothesis, Key Metric (optional), and the Date Range. The start date cannot be in the past, the end must be after the start, and the campaign cannot run longer than the maximum duration for your app (90 days by default). All day sets the start to 00:00:00 and the end to 23:59:59.
Trigger & Target: choose when players are enrolled, Login (new and current users) or Account creation (new users only), and who is eligible, All users or Users in a Specific Segment (select the segment). Segments are configured under App > Design > Segmentation > Segments.
Allocation (A/B Test only): add test scenarios with
+ Scenario(they are named A, B, C), give each a description, and set its allocation percentage. The Control percentage is calculated automatically, and the total must be exactly 100%.Global Properties, Cash Products, Items / Bundles: select the values to override and set the override for each scenario. Every cell must be filled in before you can continue. A warning is shown if an override matches the default value, since it would have no effect.
Summary: review everything, then click
Create.
New campaigns are created disabled. After you create one, you are asked whether to enable it now or leave it disabled.
Key Metric
Set a Key Metric (Revenue, Engagement, Retention, or Conversion) when you are comparing test scenarios against the Control group. Campaign analytics use it to show which scenario performs best on your primary goal.
Viewing and Editing a Campaign
View... shows a read-only summary of the campaign, including its schedule, trigger, target, allocation, and every override. From the summary you can switch the campaign on or off, open its analytics, delete it, or click Edit.
The campaign editor has three tabs: Basic, Scenarios, and Campaign JSON. The Purpose / Hypothesis field appears above the tabs. Click Save to apply changes. Any tab with a validation error shows a red error icon, and the message "Fix errors in marked tabs to continue." is displayed until it is fixed.
Completed campaigns are read-only. For a campaign that has already started, the start date can no longer be changed, but the end date and scenarios can still be edited.
Basic Tab
Status: switch to enable or disable the campaign. A campaign must be enabled to enroll players.
Name (required): up to 50 characters.
Campaign Code (required, set at creation only): same rules as in the wizard.
Key Metric: optional, see Key Metric above.
Date Range (required): the start and end of the campaign, with the same rules as in the wizard. The calculated duration is shown next to the dates.
Automatically to: All Players, or Users in a Specific Segment, who also complete the enrollment trigger (select the segment).
Enrollment Trigger: On player login (new and current players) for broad campaigns such as seasonal sales, or Account creation (new players only) for onboarding experiments and welcome offers.
Scenarios Tab
Scenarios are the variations served to enrolled players. brainCloud assigns each enrolled player to one scenario based on the allocations, and tracks analytics per scenario so you can compare them.
Every campaign includes the built-in Control scenario (_), which applies no overrides. Its allocation is always 100 minus the sum of all other scenario allocations, and it updates automatically when you change or delete another scenario. Control cannot be deleted or edited.
The scenarios table shows:
ID: the scenario's code (Control, A, B, C).
Description: what this scenario tests or offers.
Global Property Overrides, Cash Products, Items: the number of overrides of each type.
Allocation: the percentage of enrolled players assigned to this scenario. Edit it directly in the table. The non-Control allocations cannot add up to more than 100%.
A campaign can have up to 4 scenarios, including Control (Control plus 3 variations). If a campaign has no scenarios besides Control yet, click New Scenario... to add the first one. Use the row icons to Edit, Clone, or Delete a scenario.
Campaign JSON Tab
Shows the custom JSON data for the campaign. Use the Compare Campaign dropdown to show another campaign side by side, which is useful for checking differences between campaign versions. The JSON must be valid before saving.
Configuring a Scenario
The scenario dialog has a Description field and four tabs: Global Properties, Cash Products, Items / Bundles, and Scenario JSON. The scenario's code is assigned automatically. A scenario must have at least one override before it can be saved.
Global Properties Tab
Override global property values for players in this scenario, for example difficulty, reward multipliers, or feature flags, without changing anything for other players.
The table shows each property's Name, Category, the Default Value, your Override, and its Description. Use the source dropdown to compare against another scenario's values instead of the default. Click Add... to select properties. An override cannot be the same as the default value, and properties that no longer exist in the app are flagged and must be removed before saving.
Cash Products Tab
Override the price of cash products (IAP products) for players in this scenario, for targeted sales or limited-time offers.
The table shows the Product Title, its List Price, the New Price you select from the product's available price points, and the calculated Discount. Pricing rules:
The New Price must be lower than the List Price. Higher prices and $0.00 cannot be selected, and selecting the same price as the List Price is an error.
Select Not For Sale to hide the product from players in this scenario.
If the product is normally not for sale, setting a price makes it a Limited Offer that only players in this scenario can buy.
Tick Show as list Price to present the new price as the regular price, hiding the discount and the original List Price from players.
Items / Bundles Tab
Override the virtual currency prices of item catalog entries (items and bundles) for players in this scenario. The table shows each item's Icon, Name, Definition ID, Category, List Price, and Sale Price.
Newly added items show Set Sale Price and must be priced before saving. Click the Sale Price to set a price per currency, use Discount... to apply a discount, or choose Not For Sale. An item with all currency prices cleared is shown as FREE. Tick Show as list Price to present the sale price as the regular price.
Scenario JSON Tab
Shows the custom JSON data for this scenario. Use the Compare Scenario dropdown to show another scenario from the same campaign side by side. The JSON must be valid before saving.
Cloning a Campaign
Select Clone... from the details panel to copy a campaign with all of its scenarios and overrides. Enter a Name and a unique Campaign Code (they default to the original values with _COPY added, so shorten the code if it exceeds 15 characters), an optional Campaign Purpose, and a Start Date (today or later). The clone keeps the original's start time of day and duration, and you can adjust the dates after cloning. The new campaign opens in View mode when it is created.
Enabling, Disabling, and Deleting
Enable: an enabled campaign starts enrolling eligible players at its start time.
Disable: stops the campaign. No new players are enrolled and its overrides are no longer applied. Players who were already enrolled keep their scenario assignment.
Delete: permanently removes the campaign. If the campaign is enabled, a warning explains that deleting it removes the campaign for all players who have it. This action cannot be undone.
Campaign Analytics
Once a campaign has started, click View Analytics or go to App > Reports > Analytics > LiveOps Campaigns to see how each scenario is performing against Control, including results for your Key Metric, daily active users, revenue, retention, and product and item sales.
Billing
Campaigns use bulk API counts. By default, each player enrolled in a campaign costs 10 bulk API counts (once per player per campaign), each enrolled player active on a given day costs 2 per campaign, and the daily analytics processing costs about 1 per participant per day.
Permissions
Accessing this page requires the DESIGN_LIVEOPS_CAMPAIGN permission. Write access is required to create, edit, clone, enable, disable, or delete campaigns and scenarios. Users with read-only access can view all campaign and scenario details, but all modification controls are disabled.