QA Targeting between stage and production

[JPFiber]

I have two servers, a stage.example.com and example.com (a production site).

When testing an experience on stage, is it possible for the content to appear on production?

Here's the setup scenario.

Activity Location: stage.example.com

or any page where /sub-folder/, /purchase/

and url is not https://stage.example.com/sub-folder 

and url is not https://stage.example.com/purchase 

(no trailing slash intentional)

HOW is it possible when experience is live on stage that it can be seen on production?

[Gaureshk_Kodag]

Hi @JPFiber 

If you have same launch script added on the stage and prod, it is possible that activity created on stage would get delivered on prod as well.

As per below conditions 

Activity Location: stage.example.com

or any page where /sub-folder/, /purchase/

and url is not https://stage.example.com/sub-folder 

and url is not https://stage.example.com/purchase

activity is getting delivered on all the pages irrespective of stage or prod if it contains /sub-folder/, /purchase/

[JPFiber]

Hi @Gaureshk_Kodag - can you give me guidance on where to locate the launch script?   I'm guessing they should be different for each environment?

[Amelia_Waliany]

Thank you for posting your question here @JPFiber ! And thank you @Gaureshk_Kodag for weighing in! @JPFiber were you able to resolve the issue? If so, please feel free to share any updates or follow up Qs here by Replying to the thread so that others who may come across the same or similar issues can refer to your approach Otherwise @GaureshKodag do you have any other suggestions here?  Thanks!

[Eric_Vidana]

It sounds like you need to go through the Administration Panel and set up Environments / Hosts. By default, all hosts will qualify for the production environment unless you go in and configure them for an alternate environment. So in your example, I would set up stage for Development and then it should stop showing in your production environment. This feature allows for activities to be in the inactive state and still be visible in your non-prod environments.