Testing Explicit Consent Prompt // switch loaded profile

MountainMaster
Silver Contributor
Silver Contributor MountainMaster

Hi,

I would like to test the reaction rate to an "Explicit Consent Prompt".
Therefore it would be great to use the opt-in logic only to a small percentage of the website visitors.

Does anything speak against using the "Tealium Environment Switcher" code to not only change the enviroment but also the loaded profile? (e.g. 10percent load a copy of a profile with explicit consent turned on)

Thank you an advance

 

6 REPLIES 6

Testing Explicit Consent Prompt // switch loaded profile

Tealium Employee

Hi @MountainMaster,

That is a good question. The Environment Switcher tool we use is designed specifically for testing purposes and only changes the loaded environment, and not the profile.

To achieve switching more than just environment there are other tools available out there. One of my favourites is Charles Proxy, and this software contains a remote mapping tool which you can use to redirect a network request to another, simulating what you are after.

https://www.charlesproxy.com/documentation/tools/map-remote (Download)

Hope that helps!

Regards,

Ribal

Testing Explicit Consent Prompt // switch loaded profile

MountainMaster
Silver Contributor
Silver Contributor MountainMaster

Hi @rebman ,

Thank you for your fast reply.

Iam already using Charles for testing, but my question was regarding production use.
The Enviroment Switcher also has the capability to change the loaded profile. My concernes are about using the script in an live enviroment with a lot of users.

Do you see any other option to activate the feature for a small sample of the visitors?

Regards,
Tobias

Testing Explicit Consent Prompt // switch loaded profile

Tealium Employee

@MountainMaster I would refrain from using such redirect code in production. Not to say it is not a viable solution, however, I would try to approach it a different way.

The Consent Manager (CM) can have a Load Rule applied to it.

What you could try is creating a new variable (eg "consent_manager_test") and assign this a value of "true" for the test user base. Then in CM, assign a Load Rule that includes a condition that "consent_manager_test" EQUALS "true"

This way you retain all the functionality of your current profile but restrict displaying the CM to only that group of visitors.

Highlighted

Testing Explicit Consent Prompt // switch loaded profile

MountainMaster
Silver Contributor
Silver Contributor MountainMaster

@rebman as I understood the "Explicit Consent Promt" logic its opt in. So no Tags are fired until the user gives the consent via the promt. If a activate the "Explicit Consent Promt" for a profile that means none of the configured tags are send right?

So if I set up a loadrule, that would manage the displaying of the promt, but although the large part of visitors is not shown the promt the IQ Opt-In logic would still be active.

Please correct me, but in that case setting up a loadrule is not a solution.

Testing Explicit Consent Prompt // switch loaded profile

Tealium Employee

@MountainMaster the 'Display Rule' actually behaves as an 'Enforcement Rule'.  The opt-in requirement is only enforced when the rule evaluates to true (displaying the prompt to cookieless users is part of that enforcement logic).

@rebman's approach seems like a good one to me, and if you cookie each user with a random number (1-100) and use a range of those values for the rule, you'd be able to control the percentage of users you test on pretty cleanly.

Testing Explicit Consent Prompt // switch loaded profile

MountainMaster
Silver Contributor
Silver Contributor MountainMaster

@calebjaquith  thanks for clearing up. That behavior seems a bit counter-intuitive, but I am glad it works that way.

Thank you both very much.