Switch Launch Environments with the Experience Cloud Debugger
In this lesson you will use the Adobe Experience Cloud Debugger extension to replace the Launch 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 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:
- Use the Debugger to load an alternate Launch environment
- Use the Debugger to validate that you have loaded an alternate Launch environment
Get the URL of your Development Environment
- In your Launch property, open the Environments page
- 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 Launch URL on the Luma Demo Site
- 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
- Click Adobe Launch > Dynamically Insert Launch > Embed Code button to open the text input field:
- Before you paste your embed code, make sure the Chrome tab with the Luma site the one 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
- Click the disk icon to save
- 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 "X" 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 you make to your Development and Staging Environments before you publish them to Production.