1
Create a New Tag
First, navigate to your Google Tag Manager account and create a new tag:
- Click on Tags in the left sidebar
- Click the New button
- Select Custom HTML as the tag type

2
Add the Dub Analytics Script
In the Custom HTML section, you’ll need to add the Dub Analytics script. Copy and paste the following code into the HTML field:
If you’re using Dub Partners for affiliate management, you will also need to set up the

data-domains
property to enable client-side click-tracking.3
Configure the Trigger
To ensure the analytics script loads on all pages:
- Click on the Triggering section
- Select All Pages as the trigger type
- This will make the tag fire on every page load
4
Save and Publish
- Name your tag Dub Analytics
- Click Save to store your changes
- Click Submit to create a new version
- Finally, click Publish to activate the tag on your website
You can verify the installation with the following tests:
- Open the browser console and type in
_dubAnalytics
– if the script is installed correctly, you should see the_dubAnalytics
object in the console. - Add the
?dub_id=test
query parameter to your website URL and make sure that thedub_id
cookie is being set in your browser.
- The analytics script was added to the
<head>
section of the page - If you’re using a content delivery network (CDN), make sure to purge any cached content
Concepts
You can pass the following props to the@dub/analytics
script to customize its behavior:
The base URL for the Dub API. This is useful for setting up reverse
proxies to avoid
adblockers.
The attribution model to use for the analytics event. The following
attribution models are available:
first-click
: The first click model gives all the credit to the first touchpoint in the customer journey.last-click
: The last click model gives all the credit to the last touchpoint in the customer journey.
Custom properties to pass to the cookie. Refer to
MDN’s Set-Cookie documentation for
all available options.
Configure the domains that Dub will track. The following properties are available:
The query parameter to listen to for client-side click-tracking (e.g.
?via=abc123
).