Running a product tour on your website or application used to mean waiting on a developer to deploy an SDK. Not anymore. With Google Tag Manager (GTM), you can deploy DoBeacon, our no-code product tour builder, in about five minutes flat. You don't need to write a single line of code or open a pull request.
This is a superpower for product managers, marketing pros, and operations teams who need to move fast. GTM is designed for this kind of agility, letting you centralize your scripts and manage them visually. It's truly a secret weapon for getting things done without blocking engineering cycles. Let's get you set up.
What You'll Need
Before we dive in, make sure you have two things ready:
- A DoBeacon Account: If you don't have one, sign up for free at dobeacon.com/signup. You'll need to create a project to get your unique Project Key.
- Google Tag Manager Access: You'll need admin or edit access to the GTM container associated with your website.
That's it. No special permissions for your website's codebase are needed. Just GTM access.
Step 1: Grab Your DoBeacon Project Key
First, we need to get the unique identifier for your DoBeacon project. Think of this like a secret handshake that tells DoBeacon which tours to load for your site.
- Log into your DoBeacon Dashboard at dobeacon.com.
- On the left sidebar, navigate to Projects. Select the project you want to integrate with GTM. If you haven't created one yet, click "New Project" and give it a name that makes sense (e.g., "Production Website" or "Staging App").
- You'll see your Project Key (it starts with
pk_live_). Copy this to your clipboard. You'll need it in the next step.
Keep this key safe. It's how DoBeacon knows who you are.

Step 2: Create a New Tag in Google Tag Manager
Now, let's head over to Google Tag Manager and tell it to load the DoBeacon SDK.
- Log into your Google Tag Manager account.
- Select the container for your website.
- In the workspace overview, click "New Tag".
- Name your tag something clear, like
DoBeacon SDK.
Step 3: Configure the Custom HTML Tag
This is where we tell GTM to inject the DoBeacon SDK script into your page.
-
Click "Tag Configuration".
-
Choose "Custom HTML" as the tag type. This is my go-to when I need to deploy any third-party script that isn't already a built-in GTM template. It's incredibly versatile.
-
Paste the following script into the HTML field. Remember to replace
YOUR_PROJECT_KEYwith the key you copied from the DoBeacon dashboard in Step 1.
<script>window._dobeaconProjectKey = 'pk_live_YOUR_PROJECT_KEY';</script>
<script src="https://dobeacon.com/v2/dobeacon.min.js" async></script>
A quick note on script placement: This approach uses a global JavaScript variable (window._dobeaconProjectKey) to pass your project key before the main dobeacon.min.js script loads. This is the most reliable method in GTM for asynchronous script injection, ensuring the SDK correctly identifies your project. The SDK loads asynchronously (async) and will not block your page rendering.
- Leave "Support document.write" unchecked unless you have a specific, very old reason to enable it (you probably don't).
Step 4: Set the Trigger
We want DoBeacon to load on every page of your website where tours might run.
- Click "Triggering".
- Choose "Initialization - All Pages" (or "All Pages" if Initialization isn't an option in older GTM containers). This ensures the DoBeacon SDK loads as early as possible on every page view, making sure it's ready before any user interaction occurs.
- Click "Save" in the top right corner.

Step 5: Test and Publish Your GTM Container
This is the final, crucial step to make your changes live.
- Before publishing, use GTM's "Preview" mode. Click the "Preview" button in the top right of your GTM dashboard. This will open your website in a new tab with the GTM debugger running.
- On your website, check the GTM debugger pane (usually at the bottom of the page). You should see your
DoBeacon SDKtag fire under the "Initialization" event. - Open your browser's developer tools (usually F12 or right-click -> Inspect, then go to the "Network" tab).
- Filter for
dobeacon.min.js. You should see it loading successfully, typically with a 200 status code. - If you have a tour already published and set to trigger on a matching URL, try navigating to that page. You should see your DoBeacon tour appear!
- Once you've confirmed everything is working as expected in preview mode, close the preview tab.
- Back in GTM, click "Submit".
- Give your version a descriptive name (e.g., "Added DoBeacon SDK") and an optional description. Click "Publish".
That's it. DoBeacon is now live on your site, ready to deliver interactive tours to your users.
What's Next?
Now that the SDK is loaded, you can:
- Build tours: Head back to the DoBeacon dashboard or install the Chrome Extension to start creating your first tour. Since the SDK is live, any tours you publish will immediately appear on your site.
- Identify users: If you need to track user progress or personalize tours, use
DoBeacon.identify()through GTM. You can pass user data from your data layer to DoBeacon by creating new data layer variables and then pushing them with a Custom HTML tag. - Start tours programmatically: Use
DoBeacon.startTour(tourId)if you want to trigger specific tours from custom buttons or events on your page.
Deploying DoBeacon through GTM is a powerful way to put product tours directly into the hands of the teams who need them, without waiting for developer resources. It's how modern web operations should work.
Ready to see it in action? Build your first tour for free at https://dobeacon.com/signup.
