This article describes some techniques for testing your AudienceStream configuration before releasing it to your production environment.
In this article:
Unlike Tealium iQ, AudienceStream does not have DEV and QA environments for users to publish to and test. Sometimes, during configuration, a user may want to test to ensure that these attributes, audiences, or connectors are configured properly before going live.
If Attributes, Audiences, and Connectors are not properly tested before going live, this can lead to unexpected or unwanted behavior, such as visitor profiles storing unwanted or incorrect data, users joining audiences they would not have joined otherwise, or connectors performing actions on actual site users before the connectors have been properly configured.
To test specific AudienceStream objects, we need to create a new attribute that will allow you or your team to interact with these Attributes, Audiences, and Connectors, while also preventing live users from also doing the same.
The best way to do this is to create a badge specifically for testing purposes. For this example, we will call this badge “Test User.” This badge uses a rule that evaluates on “Any Event” when a Query String Parameter contains “tealium_test=true”. This badge is then set to be removed on any event where the query string parameter contains “tealium_test=false”.
The badge can be renamed as appropriate and can use whatever conditions you choose. Keep in mind that it should be something unique so this badge is not assigned to regular site visitors.
If we are looking to test a specific audience, we can set up the audience with desired conditions and simply add an additional condition that the “Test User” badge has to be assigned. This will prevent all other users from joining that audience, and will allow you to test any connector actions that are tied to that specific audience.
If we are testing a specific attribute, we can either add a condition as a part of the rule the attribute uses or we can create a specific rule that “Test User” is assigned and include that along with any other rules that the enrichment uses. The latter makes it a bit more simple when moving to go live with the configuration.
When starting your test and Trace, you must qualify for the condition to have this badge applied to you during this session. To do this, you will navigate to the site that you are testing and append the query string parameter used in the rule.
In this case, you would add the following text to the URL and refresh:
An example of what the URL will look can be seen in the image below:
When the Trace starts, you should see the “Test User” badge assigned:
Once the badge is assigned, you are now set up to run through your logic and test your configuration.
In conclusion, testing this way before going live will allow the person testing the configuration to perfect the logic at hand, reduce errors, and increase the effectiveness of campaigns.