This technique is called environment switching and will be helpful later, when you work with Launch on your own website. You will be able to load your production website in your browser, but with your development Launch environment. This enables you to confidently make and validate Launch 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 Launch in the first place!
At the end of this lesson, you will be able to:
In your Launch property, open the
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
Open the Luma demo site in your Chrome browser
Open the Experience Cloud Debugger extension by clicking the icon
Note that the currently implemented Launch 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 Launch 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 Launch 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 Launch 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 Launch property to validate your Launch implementation. When you start using Launch on your production website, you can use this same technique to validate changes.