Is it possible to set up Target to deploy activities to multiple environments at the same time?
For example, everything we currently do goes straight to production after some local testing. I would like to update our staging and dev environments with the same test, but as far as I can tell the only way to do that is to duplicate every test for each environment and deploy separately.
Ideally I'd love it to work like Launch where I can deploy through each environment so that production always matches stage / dev.
Thanks!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hey @_Paul_S
Adobe target doesn't directly support deploying the same activity to multiple environments ( dev, stage, uat or prod) in single process like Adobe Launch however you can streamline this process somehow like
1) Using mbox parameters or URL's to restrict activity - Create a single activity in Adobe Target and setup the environment specific conditions through page delivery options (below screenshot) based on the URL or through adding mbox parameters like (env = stage) etc.
Please note - this delivers the same test across all the domains.
2) You can create activities on a specific environment by utilizing and combining Properties with Workspaces. A property is mapped to a workspace.
basically, a Property and a Workspace for each environment. When you create a property it will generate a unique id (at_property) and then implement this id into its relevant environment. For Ex: dev = id123, stage = id345, prod = id567 and while creating the activity in Adobe Target, you can assign as many properties so the test will deliver on that environment.
There is nice blog written by @Vaibhav_Mathur on property and workspace - you can go through it Building Safe and Secure Engaging Experiences - The Importance of Controlled Access in Experience Op... and I'm sure that will help.
Hope this helps.
Hey @_Paul_S
Adobe target doesn't directly support deploying the same activity to multiple environments ( dev, stage, uat or prod) in single process like Adobe Launch however you can streamline this process somehow like
1) Using mbox parameters or URL's to restrict activity - Create a single activity in Adobe Target and setup the environment specific conditions through page delivery options (below screenshot) based on the URL or through adding mbox parameters like (env = stage) etc.
Please note - this delivers the same test across all the domains.
2) You can create activities on a specific environment by utilizing and combining Properties with Workspaces. A property is mapped to a workspace.
basically, a Property and a Workspace for each environment. When you create a property it will generate a unique id (at_property) and then implement this id into its relevant environment. For Ex: dev = id123, stage = id345, prod = id567 and while creating the activity in Adobe Target, you can assign as many properties so the test will deliver on that environment.
There is nice blog written by @Vaibhav_Mathur on property and workspace - you can go through it Building Safe and Secure Engaging Experiences - The Importance of Controlled Access in Experience Op... and I'm sure that will help.
Hope this helps.
Views
Like
Replies