Switch tag environments with the Experience Cloud Debugger
In this lesson you will use the Adobe Experience Platform Debugger extension to replace the tag property hardcoded on the Luma demo site with your own property.
This technique is called environment switching and will be helpful later, when you work with tags on your own website. You will be able to load your production website in your browser, but with your development tag environment. This enables you to confidently make and validate tags changes independently from your regular code releases. After all, this separation of marketing tag releases from your regular code releases is one of the main reasons customers use tags in the first place!
Adobe Experience Platform Launch is being integrated into Adobe Experience Platform as a suite of data collection technologies. Several terminology changes have rolled out in the interface which you should be aware of while using this content:
- Platform Launch (Client Side) is now tags
- Platform Launch Server Side is now event forwarding
- Edge configurations are now datastreams
Learning Objectives
At the end of this lesson, you will be able to:
- Use the Debugger to load an alternate tag environment
- Use the Debugger to validate that you have loaded an alternate tag environment
Get the URL of your Development Environment
-
In your tag property, open the
Environmentspage -
In the Development row, click the Install icon
to open the modal -
Click the Copy icon
to copy the embed code to your clipboard -
Click Close to close the modal
Replace the tag URL on the Luma Demo Site
-
Open the Luma demo site in your Chrome browser
-
Open the Experience Platform Debugger extension by clicking the
icon
-
Note that the currently implemented tag property is shown on the Summary tab
-
Go to the Tools tab
-
Scroll to the section Replace Launch Embed Code
-
Make sure the Chrome tab with the Luma site is in focus behind the Debugger (not the tab with this tutorial or the tab with the Data Collection interface). Paste the embed code that is in your clipboard into the input field
-
Toggle on the “Apply across luma.enablementadobe.com” feature so that all pages on the Luma site will map to your tag property
-
Click the Save button
-
Reload the Luma site and check the Summary tab of the Debugger. Under the Launch section, you should now see your Development Property is being used. Confirm that both the Name of the property matches yours and that the Environment says “development.”
The Debugger will save this configuration and replace the tag embed codes whenever you come back to the Luma site. It will not impact other sites you visit in other open tabs. To stop the Debugger from replacing the embed code, click the Remove button next to the embed code in the Tools tab of the Debugger.
As you continue the tutorial, you will use this technique of mapping the Luma site to your own tag property to validate your tag implementation. When you start using tags on your production website, you can use this same technique to validate changes.
