Conversion tracking requires a Business plan
subscription or higher.
lead event happens when a user performs an action that indicates interest in your product or service. This could be anything from:
- Signing up for an account
- Booking a demo meeting
- Joining a mailing list

Prerequisites
First, you’ll need to enable conversion tracking for your Dub links to be able to start tracking conversions:Option 1: On a workspace-level
Option 1: On a workspace-level
To enable conversion tracking for all future links in a workspace, you can do the following:
To enable conversion tracking for all future links in a workspace, you can do the following:
This option will enable conversion tracking in the Dub Link Builder for all future links.
- Navigate to your workspace’s Analytics settings page.
- Toggle the Workspace-level Conversion Tracking switch to enable conversion tracking for the workspace.
Option 2: On a link-level
Option 2: On a link-level
If you don’t want to enable conversion tracking for all your links in a workspace, you can also opt to enable it on a link-level.To enable conversion tracking for a specific link, open the Dub Link Builder for a link and toggle the Conversion Tracking switch.
Option 3: Via the API
Option 3: Via the API
Alternatively, you can also enable conversion tracking programmatically via the Dub API. All you need to do is pass
trackConversion: true when creating or updating a link:Set up Dub Analytics in Google Tag Manager
To track lead conversion events with Google Tag Manager, you’ll need to install the Dub analytics script and configure lead tracking tags.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.
Step 2: Create User-Defined Variable for dub_id Cookie
To read thedub_id cookie that Dub Analytics 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.

- Variable Type: Select 1st Party Cookie
- Cookie Name: Enter
dub_id - Variable Name: Name it “Dub ID Cookie”
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.Step 3: Tracking lead events
There are two ways to track lead events with Google Tag Manager:Option 1: Thank You Page Tracking (Recommended)
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: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.- 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
- Page URL contains
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: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.- 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
| Property | Required | Description |
|---|---|---|
clickId | Yes | The unique ID of the click that the lead conversion event is attributed to. You can read this value from dub_id cookie. If an empty string is provided (i.e. if you’re using tracking a deferred lead event), Dub will try to find an existing customer with the provided customerExternalId and use the clickId from the customer if found. |
eventName | Yes | The name of the lead event to track. Can also be used as a unique identifier to associate a given lead event for a customer for a subsequent sale event (via the leadEventName prop in /track/sale). |
customerExternalId | Yes | The unique ID of the customer in your system. Will be used to identify and attribute all future events to this customer. |
customerName | No | The name of the customer. If not passed, a random name will be generated (e.g. “Big Red Caribou”). |
customerEmail | No | The email address of the customer. |
customerAvatar | No | The avatar URL of the customer. |
mode | No | The mode to use for tracking the lead event. async will not block the request; wait will block the request until the lead event is fully recorded in Dub; deferred will defer the lead event creation to a subsequent request. |
metadata | No | Additional metadata to be stored with the lead event. Max 10,000 characters. |
Testing your setup
To test your GTM setup, you can use the Preview mode in Google Tag Manager:- Enable Preview Mode: In your GTM workspace, click the Preview button in the top right corner
- Enter your website URL and click Connect
- Test your chosen tracking method:
- For Option 1 (Thank You Page): Navigate to your thank-you page with query parameters (e.g.,
[email protected]&name=Test User) - For Option 2 (Form Submission): Navigate to a page with a form and submit a test form
- For Option 1 (Thank You Page): Navigate to your thank-you page with query parameters (e.g.,
- Check the GTM debugger to see if your tags are firing correctly
Verify lead tracking
You can also verify that leads are being tracked by:- Checking your browser’s developer console for any JavaScript errors
- Using the Network tab to see if requests are being sent to Dub’s analytics endpoint
- Viewing your Dub dashboard to confirm that lead 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
- Missing publishable key: Ensure you’ve replaced the placeholder with your actual publishable key
- Query parameters missing (Option 1): Ensure your form redirects to the thank-you page with the required query parameters
- Form data not captured (Option 2): Verify that your DOM selectors match your actual form field IDs or names
View your conversions
Once you’ve completed the setup, all your tracked conversions will show up in Dub Analytics. We provide 3 different views to help you understand your conversions:- Time-series: A time-series view of the number clicks, leads and sales.

- Funnel chart: A funnel chart view visualizing the conversion & dropoff rates across the different steps in the conversion funnel (clicks → leads → sales).

- Real-time events stream: A real-time events stream of every single conversion event that occurs across all your links in your workspace.
