We would like to use the privacy manager extension on each page of our domain.
The problem is that we use various tealium instances and profiles on this domain and it seems like the extension is linked to the instance used on the page.
The optout ids used in the optout cookie seem too simplily determinated to be reused.
Am I Right ?
Then, how could we share the client optouts between severals instances ?
(the idea would be to be able to determine a unique ID for optout categories, directly from the TealiuimIQ UI so that we can reuse them in the other instances without having to edit generated templates, the hash of the category name could be a temporary solution)
Solved! Go to Solution.
04-21-2017 11:48 AM - edited 04-21-2017 11:49 AM
Using Privacy manager on one domain with multiple profiles is not baked into the feature, but you could use 'Categories' in the 'Visitor Options Settings' and this would simplify the cookie key/values in the "OPTOUTMULTI" cookie that drives this feature.
Setting up 'Categories' creates key values that will be similar to this below in the OPTOUTMULTI cookie. The first 'default' category is 'c1' and as you add categories they are incremented up in value. From the example above the Analytics category list is 'c2' and 'Tealium' category list is 'c3'. You would have to be very careful to add categories in each profiles' privacy manager in the *exact* same sequence. As you add or delete a category this will increment a unique 'cX' value for that category. As always make sure to be careful, test and qa , and make sure *any* changes in the privacy manager settings are carefully monitored by your team. Any changes to one profiles' categories that was not duplicated in the other profiles would break this attempt to capitalize on the similarities in the OPTOUTMULTI cookie values created by each profile.