Unable to persist Dev AEP Tags environment across pages | Community
Skip to main content
M
MitchellTe1
Level 2
July 24, 2025
Solved

Unable to persist Dev AEP Tags environment across pages

  • July 24, 2025
  • 1 reply
  • 894 views

I can override the on-page Tags script environment on one page of the site frontier.com/shop however when I move to other pages, the Dev environment override jumps out and I'm reverted back to Prod environent.

 

I believe this issue is because on that single page frontier.com/shop the Tags script url is coded fully "https://..." and on other pages it's coded without the protocol (leading slashes only), so the debugger seems unable to handle this use case scenario.

 

Thanks for reviewing!

 

Community Discussion Ref:

Re: Adobe Experience Platform Debugger jumps envir... - Adobe Experience League Community - 765618

Best answer by bjoern__koth

Have you tried the suggested workarounds in the other thread like the Launch and DTM Switch?

Else, you might also use the Requestly extension to rewrite URL based on rules like "URL contains".

 

The // prefix is a relic from times when there were still non-https websites around and you wanted to load the script implicitly with the same protocol.

Nowadays I would always explicitly do https tbh. Maybe check with your devs to change it on their website as well.

 

But bottom line, it should ideally be handled properly by the extension.

 

You may post this as product idea as well

1 reply

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
July 25, 2025

Have you tried the suggested workarounds in the other thread like the Launch and DTM Switch?

Else, you might also use the Requestly extension to rewrite URL based on rules like "URL contains".

 

The // prefix is a relic from times when there were still non-https websites around and you wanted to load the script implicitly with the same protocol.

Nowadays I would always explicitly do https tbh. Maybe check with your devs to change it on their website as well.

 

But bottom line, it should ideally be handled properly by the extension.

 

You may post this as product idea as well

Cheers from Switzerland!
    Terms & ConditionsAccessibility statement

    Loading footer...