Permission: Campaign entities
A scenario allows your organization to define the logic that controls when a messaging experience should be presented to an end-user who visits you property. Sourcepoint's scenario builder is a feature rich and highly customizable area of the platform. Please refer to the following glossaries to inform your configuration process.
Condition glossary
A condition within a scenario is a constraint that must be satisfied before a message can be delivered. In the table below, we detail the various conditions that are available to your organization when building the logic of your scenarios.
| Condition option | Description |
| Geo targeting (Country) | Target end-users within/outside one or more countries. Condition is determined by the IP address of the end-user. |
| Geo Targeting (US State) | Target end-users within/outside one or more states in the United States. Condition is determined by the IP address of the end-user. |
| Consent Status (GDPR) |
Target end-users who satisfy the selected GDPR Consent Gate option. Click here to learn more about Consent Gates. Note: Only available for GDPR scenarios. Every scenario step which includes a GDPR message will need to include this condition. |
| Consent Status (U.S. Privacy (Legacy)) |
Target end-users who satisfy the selected U.S. Privacy (Legacy) consent gate option. Currently, Sourcepoint supports CCPA regulations within U.S. Privacy (Legacy) regulations. Click here to learn more about Consent Gates. Note: Only available for U.S. Privacy (Legacy) scenarios. |
| Device | Target end-users based on whether they are using desktop or mobile. |
| Key Value Pair Targeting | Target end-users based on a string (passed as a key-value pair). Click here to learn more. |
| Page URL Match | Target end-users based on a specific URL or URL path. Click here for more information. |
| GPC Gate |
Target end-users based on the Global Privacy Control signal from their browser. Click here for more information. Note: Currently available for U.S. Privacy (Legacy) scenarios only. |
| IDFA Gate |
Target end-users who satisfy the selected IDFA Gate option. Click here to learn more about Consent Gates. Note: Only available for iOS Tracking Authorization scenarios. |
Consent gate glossary
A condition within a scenario is a constraint that must be satisfied before a message can be delivered. In this section, we will cover the various options your organization can configure for a GDPR, U.S. Privacy (Legacy), IDFA (iOS tracking message) consent gate condition in the scenario builder.
- GDPR consent gate
- U.S. Multi-State Privacy consent gate
- U.S. Privacy (Legacy) consent gate
- IDFA gate
GDPR consent gate
Note: Every scenario step which includes a GDPR message will need to include a GDPR consent gate.
In the table below please find the options for the GDPR consent gate condition:
| GDPR TCF gate option | Description |
| Not Consented to All |
The end-user did not consent to all of the settings. Enables you to ask for consent again. Note: Sourcepoint recommends that if you use this option to also consider utilizing a message delay event within the same step to allow for time between messages. |
| Consented to Any |
The end-user has consented to at least one vendor on the vendor list. Note: This gate option does not cover an event where the end-users consents to all vendors and purposes. |
| Rejected to All | The end-user has rejected all vendors and purposes. |
| Rejected to Any |
The end-user has not consented to at least one of the settings. Using this option, users that have fully consented will not be shown a message. Note: If you would like to message ALL users after making any changes/updates to the vendor list (adding a vendor/purpose), Sourcepoint recommends the vendor list additions and legal basis changes options. |
| Not Rejected to Any | The end-user has not rejected any vendor or purpose. |
| Vendor List Additions | New vendors have been added to the vendor list since the last time the end-user consented to all vendors on the vendor list. Use this option to request consent for the new vendors. |
| Legal Basis Changes | The end-user previously consented to vendor on the vendor list but the legal basis used by a vendor has since changed (e.g. legitimate interest --> consent) and requires new consent. |
| No Action |
The end-user has not interacted with your message. Note: Sourcepoint strongly recommends that this option is included in your scenario for GDPR TCF implementations. This option ensures your message continues to displays for the end-user until they make consent choices. |
U.S. Multi-State Privacy consent gate
In the table below please find the options for the U.S. Multi-State Privacy consent gate condition:
| U.S. Multi-State Privacy consent gate option | Description |
| No Action | The end-user has not interacted with your message. |
| Vendor List Additions | New vendors have been added to the vendor list since the last time the end-user consented to all vendors on the vendor list. Use this option to request consent for the new vendors. |
| Legal Basis Changes | The end-user previously consented to vendor on the vendor list but the legal basis used by a vendor has since changed and requires new consent. |
U.S. Privacy (Legacy) consent gate
In the table below please find the options for the U.S. Privacy (Legacy) consent gate condition:
| U.S. Privacy (Legacy) gate option | Description |
| No Explicit Accept | The end-user has not explicitly accepted the purposes and/or vendors. |
| Not Rejected to Any | The end-user has not explicitly rejected a purpose and/or vendor. |
| No Action | The end-user has not interacted with your message. |
IDFA gate
In the table below please find the options for the IDFA consent gate condition:
| IDFA gate option | Description |
| Unset | End-user has not provided a response to allow or not allow tracking. |
| No | End-user has elected to not allow tracking. |
| Yes | End-user has elected to allow tracking. |
Message delivery glossary
Note: Your organization should include the message delivery event after the condition event in a scenario. By structuring a scenario this way you are building the following logic: If [condition is met] then [deliver a message at this frequency].
Alternatively, for GDPR Standard implementations, your organization can elect to use a message delivery with a frequency cap (e.g. show message every 3 months) without utilizing a condition.
The message options in the scenario builder allow your organization to control the delivery of a message. Configuring the message delivery option entails setting both the frequency and message. In the table below, please find the various frequencies that you can select when configuring your message delivery:
| Message delivery option | Description |
| Show Message Always | If the condition(s) of the scenario are satisfied, always show the message. |
| Show Message Once | If the condition(s) of the scenario are satisfied, should the message once. |
| Message Frequency Cap |
If the condition(s) of the scenario are satisfied, show a message a finite number of times across a set interval of time (e.g. show message every 3600 seconds for a maximum of 4 times). |
| Session Message Number Limits | If the condition(s) of the scenario are satisfied, show a message a finite number of times during an end-user's session. |
Message delay glossary
The time delay event in the scenario builder allows your organization to build in a buffer between messages and is triggered immediately whenever an end-user falls into a particular scenario step.
Note: Time delay events will only trigger the first time and only once whenever an end-user satisfies a scenario step.
In the table below please find the time delay options available in the scenario builder:
| Message delay option | Description |
| Pageviews | If all condition(s) of the scenario are satisfied, delay showing the message for n pageviews. |
| Time |
If all condition(s) of the scenario are satisfied, delay the showing of the message. Note: Please be aware that there can be a ~20 minute variance for the delay that can be noticeable if using a shorter time delay. |
| None | No delay is applied. |
Comments
0 comments