Skip to Content
Developer DocsIntegrationsGoogle Tag Manager

// snippet import removed // snippet import removed // snippet import removed

💡

This feature is only available on Business plans and above .

Dub’s Google Tag Manager integration  allows you to track conversion events directly from Google Tag Manager.

Prerequisites

Install Dub via Google Tag Manager

There are 2 steps to install the Dub Analytics script via Google Tag Manager:

  1. Add Dub Analytics script to GTM
  2. Create User-Defined Variable for dub_id Cookie

Step 1: Add Dub Analytics script to GTM

First, you’ll need to add the Dub Analytics script to your website using Google Tag Manager.

In your GTM workspace, navigate to the Tags section and click New to create a new tag.

GTM New Tag

Select Custom HTML as the tag type and add the following code:

<script> (function (c, n) { c[n] = c[n] || function () { (c[n].q = c[n].q || []).push(arguments); }; var methods = ["trackClick", "trackLead", "trackSale"]; for (var i = 0; i < methods.length; i++) { (function (method) { c[n][method] = function () { var args = Array.prototype.slice.call(arguments); args.unshift(method); c[n].apply(null, args); }; })(methods[i]); } var s = document.createElement("script"); s.defer = 1; s.src = "https://www.dubcdn.com/analytics/script.conversion-tracking.js"; s.setAttribute("data-publishable-key", "dub_pk_xxxxxxxx"); // Replace with your publishable key document.head.appendChild(s); })(window, "dubAnalytics"); </script>
⚠️

Make sure to replace dub_pk_xxxxxxxx with your actual publishable key from your Dub workspace (under the Analytics settings page )

Configure the tag to fire on All Pages by setting the trigger to All Pages - Page View.

Name this tag “Dub Analytics script” and save it.

To read the dub_id cookie that Dub Analytics script sets, you’ll need to create a User-Defined Variable in Google Tag Manager.

In your GTM workspace, navigate to the Variables section and click New to create a new variable.

GTM Dub ID Cookie Variable

Configure the variable with the following settings:

  • Variable Type: Select 1st Party Cookie
  • Cookie Name: Enter dub_id
  • Variable Name: Name it “Dub ID Cookie”

Click Save to create the variable.

📝

This variable will automatically read the dub_id cookie value set by the Dub Analytics script. You can use this variable in your tags to pass the Dub ID when tracking conversion events.

Tracking lead events

There are two ways to track lead events with Google Tag Manager:

This method tracks leads when users land on a thank-you or success page after completing a form. This approach is more reliable as it’s less likely to be blocked by ad blockers and provides better data accuracy.

Create a Custom HTML tag with the following code:

<script> (function () { // Get query parameters from URL var params = new URLSearchParams(window.location.search); var email = params.get("email"); var name = params.get("name"); // Get dub_id from cookie using GTM variable var clickId = {{Dub ID Cookie}} || ""; // Only track the lead event if email and clickId are present if (email && clickId) { dubAnalytics.trackLead({ eventName: "Sign Up", customerExternalId: email, customerName: name || email, customerEmail: email, clickId: clickId, }); } })(); </script>
📝

Important: Make sure to pass along the email and name query parameters to the thank-you page so that the lead event can be attributed to the correct customer.

Configure this tag to fire on specific pages by creating a Page View trigger with conditions:

  • Trigger Type: Page View
  • This trigger fires on: Some Page Views
  • Add conditions like:
    • Page URL contains /thank-you
    • Or Page Path equals /success
    • Or whatever URL pattern matches your thank-you pages

Name this tag “Dub Lead Tracking - Thank You Page” and save it.

Option 2: Form Submission Tracking

This method tracks leads immediately when users submit forms on your website. Note that this approach may be less reliable due to ad blockers and timing issues.

Create a Custom HTML tag with the following code:

<script> (function () { // Get form data - customize these selectors based on your form var name = document.getElementById("name") ? document.getElementById("name").value : ""; var email = document.getElementById("email") ? document.getElementById("email").value : ""; // Get dub_id from cookie using GTM variable var clickId = {{Dub ID Cookie}} || ""; // Only track the lead event if email and clickId are present if (email && clickId) { dubAnalytics.trackLead({ eventName: "Sign Up", customerExternalId: email, customerName: name || email, customerEmail: email, clickId: clickId, }); } })(); </script>
📝

Important: You’ll need to customize the DOM selectors (getElementById('name'), getElementById('email')) to match your actual form field IDs or use different methods to capture the form data based on your website’s structure.

Configure this tag to fire on Form Submission by creating a new trigger:

  • Trigger Type: Form Submission
  • This trigger fires on: Some Forms (or All Forms if you want to track all form submissions)
  • Add conditions to specify which forms should trigger lead tracking

Name this tag “Dub Lead Tracking - Form Submission” and save it.

Tracking sales events

There are two ways to track sales events with Google Tag Manager:

This method tracks sales when users land on an order confirmation or success page after completing a purchase. This approach is more reliable as it’s less likely to be blocked by ad blockers and provides better data accuracy.

Create a Custom HTML tag with the following code:

<script> (function () { // Get query parameters from URL var params = new URLSearchParams(window.location.search); var customerId = params.get("customer_id"); var amount = params.get("amount"); var invoiceId = params.get("invoice_id"); // Only track if customer ID and amount are present if (customerId && amount) { // Track the sale event dubAnalytics.trackSale({ eventName: "Purchase", customerExternalId: customerId, amount: parseInt(amount), // Amount in cents invoiceId: invoiceId || undefined, currency: "usd", // Customize as needed paymentProcessor: "stripe", // Customize as needed }); } })(); </script>

Configure this tag to fire on specific pages by creating a Page View trigger with conditions:

  • Trigger Type: Page View
  • This trigger fires on: Some Page Views
  • Add conditions like:
    • Page URL contains /order-confirmation
    • Or Page Path equals /checkout/success
    • Or whatever URL pattern matches your order confirmation pages

Name this tag “Dub Sales Tracking - Order Confirmation” and save it.

Option 2: Checkout Form Submission Tracking

This method tracks sales immediately when users complete checkout forms on your website. Note that this approach may be less reliable due to ad blockers and timing issues.

Create a Custom HTML tag with the following code:

<script> (function () { // Get checkout data - customize these selectors based on your form var customerId = document.getElementById("customer_id") ? document.getElementById("customer_id").value : ""; var amount = document.getElementById("amount") ? document.getElementById("amount").value : ""; var invoiceId = document.getElementById("invoice_id") ? document.getElementById("invoice_id").value : ""; // Only track if customer ID and amount are present if (customerId && amount) { // Track the sale event dubAnalytics.trackSale({ eventName: "Purchase", customerExternalId: customerId, amount: parseInt(amount), // Amount in cents invoiceId: invoiceId || undefined, currency: "usd", // Customize as needed paymentProcessor: "stripe", // Customize as needed }); } })(); </script>
📝

Important: You’ll need to customize the DOM selectors (getElementById('customer_id'), getElementById('amount'), etc.) to match your actual checkout form field IDs or use different methods to capture the form data based on your website’s structure.

Configure this tag to fire on Form Submission by creating a new trigger:

  • Trigger Type: Form Submission
  • This trigger fires on: Some Forms (or All Forms if you want to track all form submissions)
  • Add conditions to specify which forms should trigger sales tracking (e.g., checkout forms)

Name this tag “Dub Sales Tracking - Checkout Form” and save it.

Testing your setup

To test your GTM setup, you can use the Preview mode in Google Tag Manager:

  1. Enable Preview Mode: In your GTM workspace, click the Preview button in the top right corner
  2. Enter your website URL and click Connect
  3. Test your chosen tracking method:
    • For Option 1 (Order Confirmation): Navigate to your order confirmation page with query parameters (e.g., ?customer_id=123&amount=1000&invoice_id=inv_456)
    • For Option 2 (Form Submission): Navigate to a checkout page and complete a test purchase form
  4. Check the GTM debugger to see if your tags are firing correctly

Verify conversion tracking

You can also verify that conversion events are being tracked by:

  1. Checking your browser’s developer console for any JavaScript errors
  2. Using the Network tab to see if requests are being sent to Dub’s analytics endpoint
  3. Viewing your Dub dashboard to confirm that sale events are appearing in your analytics

Common troubleshooting tips

  • Tag not firing: Check that your triggers are configured correctly and that the conditions match your page structure
  • Form data not captured (Option 2): Verify that your DOM selectors match your actual checkout form field IDs or names
  • Query parameters missing (Option 1): Ensure your checkout process redirects to the confirmation page with the required query parameters
  • Amount formatting: Ensure amounts are in cents (e.g., $10.00 = 1000 cents)
  • Multiple events: Make sure your tags aren’t firing multiple times by checking trigger conditions
  • Duplicate tracking: Verify you’ve only implemented one tracking method (Option 1 OR Option 2, not both)
  • Missing publishable key: Ensure you’ve replaced the placeholder with your actual publishable key
⚠️

Client-Side Tracking Limitations:

  • Ad blockers – Users with ad blockers may prevent tracking scripts from loading
  • JavaScript disabled – Events won’t be tracked if users have JavaScript disabled
  • Network issues – Failed network requests won’t retry automatically
  • Privacy concerns – Some users may block client-side tracking for privacy reasons

For more accurate conversion tracking, consider using server-side conversion tracking

View conversion results

And that’s it – you’re all set! You can now sit back, relax, and watch your conversion revenue grow. We provide 3 different views to help you understand your conversions: