The Breakout script is a lightweight, stable snippet that only needs to be added once. It won't change as new features are released.
If you're already using Adobe Tags to manage scripts on your site, this is the recommended approach for adding Breakout without touching your site's source code.
Prerequisites
Access to Adobe Experience Platform Data Collection (the Tags interface)
Your Breakout tenant ID and agent ID (you can find these in your Breakout dashboard under Settings → Install)
Publishing rights to the Adobe Tags property for your website
Procedure
Open your Adobe Tags property
Sign in to Adobe Experience Platform at experience.adobe.com
From the left navigation, go to Data Collection→Tags
Select the property associated with the website where you want the Breakout agent to appear
Create a new rule
In the left sidebar of your property, click Rules→Add Rule
Give your rule a descriptive name, for example "Load Breakout Agent"
Configure the event (when to load)
Under the Events section, click Add. Configure it as follows. This ensures the Breakout script loads as early as possible on every page.
Extension: Core
Event Type: Library Loaded (Page Top)
Click Keep Changes
Note: If you prefer the script to load later in the page lifecycle, you can choose "DOM Ready" or "Window Loaded" instead. "Library Loaded (Page Top)" is recommended for the best visitor experience since it allows the Breakout agent to be ready as soon as the page renders
Add the Breakout script as an action
Under the Actions section, click Add. Configure it as follows:
Extension: Core
Action Type: Custom Code
Language: HTML
In the code editor that opens, paste the following snippet:
<script async src="https://script.getbreakout.ai/command_bar_widget.js" tenant-id="YOUR_TENANT_ID" agent-id="YOUR_AGENT_ID"> </script>
Replace the following:
YOUR_TENANT_IDwith your company's Breakout tenant IDYOUR_AGENT_IDwith the agent ID you want to deploy
Note: You can find both of these values in your Breakout dashboard
Click Keep Changes and then Save
Build and Test in a Development Environment
In the left sidebar, click Publishing Flow
Click Add New Library (or open an existing development library).
Give it a name such as "Breakout Agent - Dev" and set the environment to Development
Under Resource Changes, click Add All Changed Resources to include your new rule
Click Save & Build to Development
Notes:
Once the build completes, you can test it by loading your site with the development embed code.
To find your development embed code, go to Environments in the left sidebar, and click the install icon next to your Development environment
Use a browser extension like Adobe Experience Platform Debugger to confirm the Breakout script is loading and the agent widget appears on the page
Approve and publish to staging
Once you've confirmed everything works in Development, return to Publishing Flow. Click the arrow on your library and select Submit for Approval
After approval, click Build for Staging
Test again using your staging environment embed code to verify the agent loads correctly in a production-like setting
Publish to Production
When you're satisfied with staging, return to Publishing Flow and click Publish for your library
The Breakout agent will now be live on all pages served by your production Adobe Tags embed code.
Troubleshooting
If the Breakout agent doesn't appear after publishing, check the following:
Verify the embed code is present. Use your browser's developer tools (View Source or the Elements panel) to confirm the Adobe Tags library script is loading on the page
Use the Adobe Experience Platform Debugger browser extension to check that your rule is firing and the custom code action is executing
Check the browser console for errors. Look for any network errors related to
script.getbreakout.aior JavaScript errors that might indicate a conflict with other scriptsConfirm your tenant ID and agent ID are correct. A typo in either value will prevent the agent from loading. Cross-reference with your Breakout dashboard under Settings → Install
Check your environment. Make sure you are testing against the correct Adobe Tags environment (Development, Staging, or Production) and that the latest library has been built and published
