We will demonstrate how to test changes in AudienceStream before they are published to production.


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 visitor profiles storing unwanted or incorrect data, users joining audiences they would not have joined otherwise, and connectors performing actions on actual site users before they are ready.


To test specific AudienceStream objects we need to create a special user that will be able to interact with these Attributes, Audiences, and Connectors. 


The best way to do this would be 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”.


image 1 - test user badge rules.png

  • The badge can be called whatever you like, and can use whatever conditions you choose.  Keep in mind that it should be something unique so that regular site visitors do not get this badge applied to them.


If we are looking to test a specific audience, we can set the audience up 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.


image 2 - test with  aud.png


If we are testing a specific attribute, let’s say a trait, we can either add a condition as a part of the rule the trait uses, or, we can create a specific rule that “Test User” is assigned and include that along with any other rules that the condition uses.  The latter makes it a bit more simple when moving to go live with the configuration.


image 3 - with rule.png




image 4 - added to trait, independant.png


When starting your test/trace, you must qualify for the condition to have this badge applied to you during your 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 domain and hit enter.




Your domain should look similar in format to the image below:


image 5 - qsp appended.png


When your trace starts, you should then see your “Test User” badge assigned.


image 6 - test user badge is assigned.png


Once the badge is assigned you are now set up to run through your logic and test your configuration.


In short, testing this way before going live will allow the person doing the configuration to perfect the logic at hand, reduce errors, and increase effectiveness of campaigns.