Hello Arya, You're correct that EventStream, by default, has only one publish environment: production. While you cannot create a custom publish environment specifically for QA within EventStream, there are alternative methods to achieve a similar result. One option is to use load rules and/or extensions within Tealium iQ Tag Management to manage your testing environment. Here's how: Use Load Rules to control tag firing: You can create load rules that will only fire tags when certain conditions are met, such as when a specific hostname, query parameter, or cookie value is present. This way, you can test the tags in a QA environment by using a specific hostname or adding a query parameter to your URL. For example, you can create a load rule that only fires the tag when the query parameter "env" is set to "qa", like this: env=qa Utilize Extensions for conditional data mapping: You can create extensions to manage your data mappings based on the same conditions you've used in load rules, like a specific hostname or query parameter. This allows you to control which data is sent to specific connectors or data layers in your QA environment. Leverage Tealium iQ Environments: Even though EventStream doesn't have multiple publish environments, Tealium iQ Tag Management does. You can set up a QA environment within Tealium iQ, where you can test your changes before pushing them to production. This can help you ensure that your tags, load rules, and extensions are working as expected. While this approach may require some manual configuration, it allows you to create a flexible testing environment without duplicating all your tags, connectors, and event feeds. By using a combination of load rules, extensions, and Tealium iQ environments, you can test your implementations in a QA environment before pushing them live to production. I hope this helps! If you have any further questions or need more information, please don't hesitate to ask.
... View more
Expand/CollapseMenu
