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 Target end-users within/outside one or more countries/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: Not available for custom messages.

Consent Status (CCPA)

Target end-users who satisfy the selected CCPA Consent Gate option. Click here to learn more about Consent Gates.

  Note: Not available for custom messages.

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.
Social Gate Target end-users based on whether they arrive from a social media site.
Page URL Match Target end-users based on a specific URL or URL path. Click here for more information.
IDFA Gate

Target end-users who satisfy the selected IDFA Gate option. Click here to learn more about Consent Gates.

  Note: Not available for custom messages.

Number Range Targeting Target end-users when an integer passed as a key-value is written within a specific range. To target a specific integer, set the same value for the start and end values.
IP Targeting Target end-users based on one or more IP addresses.
First Page View Only search gate Target end-users that have come from search engines in their first pageview.
First Page View Only social gate Target end-users that have come from social sites in their first pageview.

Consent gate glossary

  Note: Consent gates are not available for custom messages.

A condition within a scenario is a constraint that must be satisfied before a message can be delivered. In this article, we will cover the various options your can configure for a GDPR TCF, CCPA, IDFA (iOS tracking message) consent gate condition in the scenario builder.

GDPR TCF consent gate

In the table below please find the options for the GDPR TCF consent gate condition:

GDPR TCF gate option Description
Consented to All The end-user has consented to all vendors and purposes.
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.
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.

CCPA consent gate

In the table below please find the options for the CCPA consent gate condition:

CCPA 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).

  Note: Currently, message frequency capping is not available for organizations utilizing our unified script.

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. 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 by n seconds.
None No delay is applied.
Was this article helpful?
0 out of 0 found this helpful