When we talk about audiences in Tealium, we’re not talking about a theatre full of people watching the same movie. We actually mean more like “target audience”. According to Wikipedia, “A target audience is the intended audience or readership of a publication, advertisement, or other message catered specifically to said intended audience.”
In my last post I spoke about what to do when your QA test goes wrong. As you go through the process of testing your logic for assigning attributes and audiences, one important tool you need for validating end-to-end scenarios is Trace. That said, along the way, I have collected other tools that I rely on to ensure that everything is working as it should.
Building attributes and audiences in Tealium AudienceStream is pretty straightforward. But as your audiences get more advanced and you get more team members using the platform, you might run into issues with overlapping or conflicting rules that will impact the success of your solution. In this post I focus on how to build a solid test plan to avoid common pitfalls during an AudienceStream implementation.