How do you use the 3 different publish environments? Is anyone using the Dev environment, or do you stick to using QA and Prod only for publishing?

[joseph_brown · Accepted solution]

We are currently using all 3. At Lincoln we have 6 environments including production that our code moves through DEV, TEST, QA, UAT, PREPROD, then PROD. We have Tealium setup so our Tealium Dev publish environment matches up with our DEV environment. I then use the Tealium QA tag across TEST, QA, UAT, PREPROD. Then we use the Tealium Prod environment in our Production environment.

[nicholas_earl]

We've got a three tier environment here at A+E (Dev, Stage, Production), so Tealium's setup aligns perfectly with our existing workflow. We could probably make do with just dev/prod environments for Tealium if we needed to, but on the other hand I don't feel like we'd be able to make efficient use of more than three.

[robert_alderson]

At EA we use all three environments. However we had an issue where each developers' local environment was set to communicate with the the dev environment for Tealium, and ongoing development would sometimes break javascript that another developer was coding. We had to switch to point the local environments to Tealium Stage (stable) and to only point them to Tealium Dev if they are working on something specifically for Tealium.

[landin_gee]

I do not have a Dev environment but the Dev option in Tealium is awesome because I can use the Tag Companion and switch profiles to test, which in a way, does everything I need it do to.

[Clint]

Landin, love that you are using the combined functionality as your own virtual sandbox for testing!