About testing

The server-side configuration does not have a Dev or QA environment, so testing your changes before releasing to production requires an extra step. With the power of badges and rules you can easily restrict new functionality to a Test User which can be identified any number of ways.

Configure a badge for testing

For this example, we will use a badge attribute called “Test User”. This badge uses a rule that evaluates on “Any Event” when a query string parameter contains tealium_test=true. This badge uses a second rule to indicate that it should be unassigned from a visitor when the query string parameter contains tealium_test=false.

The badge and rule condition can be customized, but they should be unique so that regular site visitors do not get this badge applied to them.

Configure an audience for testing

If you are looking to test a specific Audience, you can simply add a 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.

Configure an attribute for testing

To test a specific attribute, for example a String, you can include a specific rule that the Test User badge is assigned.

Test

When starting your trace session, you must satisfy the test condition used in your test configuration. In this example, you would navigate to your site and append the query string parameter and value used in the rule.

For example: http://www.example.com/?tealium_test=true

Once your trace starts, you should then see your Test User badge assigned.

Testing this way before publishing to production will allow you to do be confident in your configuration logic, help reduce errors, and increase the accuracy of your strategy.