Content Variables
Content Variables allow you to create and manage your own #-Variables. Where a built-in variable like #Firstname# pulls its value from the Player Segment or the Trigger, a Content Variable uses a value you yourself define and manage centrally.
You set the value once, and every Action that uses the Content Variable picks it up automatically. If you change the value, every message using the variable updates with it, so you don't have to edit each Action by hand.
You can also set different values per brand (Player Origin), and per language or market (Communication Profile), so the same variable is adjusted automatically for each recipient.
🤔 What are Content Variables?
A Content Variable is a reusable piece of content stored under one alias, for example #URL# or #SupportEmail#. Like all #-Variables, the alias is enclosed in # symbols and is replaced with its assigned value when the Action is sent.
The difference is the source of the value. Built-in #-Variables read from Player Segment data or Trigger data. A Content Variable holds a value you write yourself, with optional variations per Origin and Communication Profile, and a default that is used when no variation applies.
Example
Say your site URL is casinoexample.com and it appears across several Activities.
- Create a variable with the alias #URL# and set its value to casinoexample.com.
- Insert #URL# wherever you need the link, for example, in an email body.
- At send time, recipients see casinoexample.com.
- If the URL changes to casinoexample2.com, update the variable once and every message using #URL# reflects the new value.
- If you run more than one brand or market, set a different URL per Origin and per Communication Profile.
📍 Where to find Content Variables
Open System Settings > Content Variables in the side menu.
⚙️ Setting up a Content Variable
Select New Variable and fill in the details. You can save once the required fields are filled in.
| Field | Description |
|---|---|
Variable name | The display name shown on the card and in lists. |
Enable toggle | When on, the variable is available to insert into content. A variable can be saved while disabled. |
System alias | The unique identifier you type to insert the variable, triggered with #. It must be unique. You cannot reuse an alias already in use. Aliases are case sensitive. |
Default text | The value used when no Origin or Communication Profile specific value applies. It is a rich text field and acts as the fallback. |
Description | Explains what the variable is for. It appears in the variable tooltip in the platform and is not visible to players. |
🛠️ Setting values per Origin and Communication Profile
The lower panel lists the Origins available in your environment. Select an Origin to set the values used for its Communication Profiles.
- Toggle on a Communication Profile to enter a value for it. Active profiles move to the top of the list.
- Each value field has a translate action that converts the default text into the profile language, which you can then adjust.
- If a Communication Profile has no value, the default text is used.
The variable tooltip previews how the variable will appear. Its icon changes with the value type, for example, text or a hyperlink.
🚀 How to use Content Variables
In any Action Field that supports Variables, type # to open the Variable dropdown, then select the one you want. Your Content Variables appear in this list alongside the built-in Segment-based and Trigger-based #-Variables.
The Variable will appear once sent, based on the recipient's Origin and Communication Profile, falling back to the default text when no specific value has been set.
As with all #-Variables, aliases are case sensitive, and they apply in Action Fields rather than directly inside an Email Template. To use a Content Variable in an Email Template, add a placeholder in the template, and enter the variable in the matching Action Field instead.
See #-Variables for more information on the common behaviours.
✏️ Editing a Content Variable
Select the relevant variable to view its settings. Saved variables are locked by default. Unlock the variable to make changes.
Changes to a variable that is in use take effect immediately across every message that uses it. Because of this, the system shows a confirmation before you save so you can check the impact first. Plan edits to live variables with this in mind.
🚫 Disabling a Content Variable
Disabling a variable removes it from the # dropdown so it cannot be added to new content. It does not change content that already uses the variable, and existing messages keep sending the current value. Re-enable the variable to make it available in the dropdown again.
💡 Things to know
- Variables cannot be deleted once saved. This prevents breaking content that already references them. Disable a variable you no longer want to use for future communications.
- An alias must be unique, is case sensitive, and cannot match one already in use.
- Where no Origin or Communication Profile value is set, the default text is always used as the fallback.
- Content Variables are managed centrally and hold values you define, unlike Segment-based and Trigger-based #-Variables, which read from player or event data.