Salesforce

Configuring Audience Logic Using Geolocation Rules

« Go Back
Information
Configuring Audience Logic Using Geolocation Rules
UUID-35dcf48b-97af-38c8-1ef2-39f3da694732
Article Content

Audience Logic allows you to define attributes and logic to deliver a specific CMP experience to your applications’ visitors. You can configure the Audience Logic using Geolocation Rules.

Note

Audience Logic is only available for use with the Consent Rate Optimization add-on. To enable Consent Rate Optimization, contact OneTrust Support.

To configure the Audience Logic

  1. On the Cookie Consent menu, select Geolocation Rules. The Geolocation Rule Groups screen appears.

  2. Select a geolocation rule group from the list. The Geolocation Rule Group Details screen appears.

    Note

    For information on creating a new rule group, see Configuring Geolocation Rules.

  3. Select the Use Audience Logic checkbox to enable Audience Logic.

  4. Enter a name and define the logic for your condition.

    audience_manager_1.png
  5. Click the Save button. Your Audience Logic condition displays.

    audience_manager_2.png

    Tip

    A limit of five audience logic conditions per geolocation rule is recommended to maintain optimal performance.

Each condition has its own set of geolocation configurations. Else configurations will load if the Audience Logic condition is not met or is unknown.

Example Configuration: GPC

When the Global Privacy value is TRUE, the condition will be hit.

If TRUE:

audience_manager_gpc_1.png
audience_manager_gpc_2.png

You can leverage the following code in the JavaScript entry field to load your configurations for the GPC condition:

navigator.globalPrivacyControl

If Else (FALSE/undefined):

audience_manager_gpc_3.png
audience_manager_gpc_4.png

Example Configuration: Mobile Devices

Present the end user with a different CMP experience when the browser user agent is in the defined mobile device list.

audience_manager_mobile.png

You can leverage the following code in the JavaScript entry field to load your configurations for the mobile condition:

/Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i.test(navigator.userAgent)

Things to Know

  • When consent logging is enabled, a collection point will be created per condition. You cannot use the field to write a cookie or a variable.

  • Any browser values or custom variables must be available prior to the variable when using Audience Logic.

  • Audience Logic is not currently compatible with our CSP feature.

  • A limit of five audience logic conditions per geolocation rule is recommended to maintain optimal performance.

 
Article Visibility
4,415
Translation
English
Checked

Powered by