Common Use Cases for Multi Brand Preference Centers via Visibility Rules

Introduction

Preference center visibility rules allow for dynamic configuration that adapts to your business needs and multi brand organizations can benefit from the flexibility that these rules offer. When configured correctly, visibility rules can consolidate multiple preference centers into one, enhancing the user experience for your data subjects. This article details common use cases to transform your preference center.

For more information, see Configuring Visibility Rules for a Multi Page Preference Center.

Use Cases

To demonstrate these use cases, three brands (A, B, and C) belong to the same parent company. The screenshot below illustrates how this is displayed in a preference center.



In this example, each brand has a page under the Manage Pages section. Sections can be customized and/or hidden depending on the desired user interface. In this case, each section is customized as Brand A/B/C Section, where A/B/C is the specific brand. This facilitates the process to identify the relevant sections when configuring the visibility rules in the next step.

Note:

For this example and the following use cases, you can configure brands as additional sections within one page instead of separate pages. The visibility rules would be configured similarly in either case.

The image below shows a query parameter configuration that directs the data subject to the page for a particular brand while hiding pages for other brands. This is useful for creating a landing page specific to a particular brand without creating and maintaining separate preference centers for each.



If a query parameter of brand=A is included in the preference center URL, this will validate the condition and then apply the appropriate actions. The actions configured here hide pages for both Brand B and C. This can also be duplicated to create a similar experience when the query parameter of Brand is B or C as well.

When sharing magic links with data subjects, append the desired query parameter to the URL. Upon clicking the link, they will see the modified preference center as shown below. Despite having all brands configured on this preference center, only Brand A is shown below.



2: Display Pages/Sections for All Brands via a Custom Purpose

Building on the previous example, where data subjects see only one brand when accessing the preference center via the brand query parameter, we are adding the All Brands Page and corresponding visibility rules. When configured, this provides data subjects with the option to view all brands, regardless of their starting brand.

An additional purpose, See All Brands, is created to enable this feature. This is not an out-of-the-box purpose, it is a custom purpose created specifically for this use case by a OneTrust Consent Admin.

After creation, See All Brands is nested under the All Brands Page because a purpose can only be used once in a preference center, regardless of the number of pages.

Note:

You cannot replicate this purpose across each brand page. If you choose to use sections instead of pages, a new section should house this custom purpose.



The visibility rule below is configured to include this additional purpose. Because we are building on the previous example, we now introduce an AND clause to combine two conditional checks. By selecting ALL beside the condition below, the join is changed to AND instead of being an OR.



The See All Brands condition expects the purpose to be toggled off or have no interaction. In other words, the condition becomes false when the purpose is toggled on. If no interaction occurs on the See All Brands purpose, the preference center will still only show the brand passed in from the query parameter.

The image below shows the corresponding actions from the configured visibility rules which are the same as the prior use case. We are choosing to hide pages B and C.



Because the two conditions above are joined by an AND condition rather than an OR condition, the visibility rule will be evaluated as false if either condition is false. To display all brands, we need the visibility rule to be evaluated as false.

After logging in and toggling on the See All Brands purpose, all brand pages are now visible to the data subject, as shown below.



Continuing to expand on the prior use cases, we can also introduce two more purposes, Opt In to All Brands and Opt Out From All Brands, within the All Brands Page to provide data subjects with the ability to opt in/out of multiple brands with one toggle.

These purposes are nested under the All Brands Page, similar to See All Brands, to provide a consistent experience regardless of the starting brand.



The visibility rule below is configured so that when the Opt In to All Brands purpose is toggled on, it turns on all purposes for each brand and turns off the Opt Out From All Brands purpose. These two purposes are treated as opposite sides of the same coin to avoid conflicting visibility rule logic.





The images below show the visibility rule configuration so that when Opt Out From All Brands is toggled on, it turns off consent for each brand and turns off the Opt In to All Brands purpose.





Upon logging in, data subjects can interact with the toggles below to modify their consent across all brands with one toggle via the visibility rules.



This visibility rule is especially beneficial for Multi Page preference centers, as Subscription Settings only affect the visible page. You can also opt to hide the Subscribe All toggle within the Subscription Settings section so it does not conflict with the custom toggles we created.

When hiding the Subscription Settings via the built-in hide setting, this will apply to all pages. If you prefer to only hide Subscribe All on the All Brands Page, you can hide this toggle with custom CSS as shown in the example below.

JSON 
#[Enter_Your_SubscriptionsSettings_Section_ID] #subscription-settings #SubscriptionSettings .ot-preference-settings-unsubscribe
{
display:none;
}

4: Using Geolocation to create unique regional experiences

This use case leverages geolocation within the visibility rules to display distinct purpose choices based on the data subject’s geolocation.

For this example, our company contains data subjects in two countries: United States and Canada. A new purpose can be created specifically for Canadian data subjects. In this case, it is Brand A – CA.



The rule is configured so that if a data subject’s geolocation is detected as the USA, the Brand A – CA purpose remains hidden, and vice versa for Canada.



When logging in from the USA, the Brand A – CA purpose is not visible.



Testing Visibility Rules

Note:

We recommend not using live preference centers to test preference center visibility rules. Publishing test updates on a live preference center makes it immediately available.

You can follow the following testing best practices instead:

  • Use a testing environment such as UAT.

  • If testing within the production environment, create an unlisted preference center for testing.

  • Perform comprehensive testing, including regression testing, to ensure all rules function correctly.

Deployment

Once testing is complete, deploy the visibility rules to production.

Note:

There is no automated method to copy visibility rules. They must be manually reconfigured. Ensure all configurations are correct before publishing to production.

Final Considerations

The examples above illustrate specific use cases, but visibility rules can be adapted for various applications. Multiple configurations may achieve similar results and the best approach depends on your specific business needs.