Rules in Prod but disabling for Non Prod Environments

Avatar

Avatar

justinj1698984

Avatar

justinj1698984

justinj1698984

26-08-2019

In Adobe Launch – if we have rules/tags that we want in production but don’t want active in Staging is that possible to do with only one “property” where we migrate from dev -> staging -> production?

  We don’t want the tags in staging because they go to the vendor if people are testing them and that skews true production results – we only want in staging to test, then promote to production and then disable just from staging.             

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

29-08-2019

You could add a condition to the rule which checks the environment and only returns true for production.

Answers (3)

Answers (3)

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

29-08-2019

Maybe someone from Adobe has a better idea, but it seemed the most simple solution and adding an option that checks a cookie or a js variable would make it more flexible.

Avatar

Avatar

justinj1698984

Avatar

justinj1698984

justinj1698984

29-08-2019

?Thanks Thomas for all the suggestions and advice -- much appreciated

Avatar

Avatar

justinj1698984

Avatar

justinj1698984

justinj1698984

29-08-2019

Is that the only way, because that means I have to create the rule without the condition, test it, and push it thru the environments to test in each non prod one - then finally all the way thru to prod. Then modify the rule to add the condition then again push it all the way thru?

If I?'m doing that maybe better then that seems to have it fire always in prod but also if a "javascript variable" or cookie or something else is set that way it can be tested in non prod environments simply by setting that vs having to do a push again.