Tracking ID

The Tracking ID (ta_tid) is the core identifier that links a click on a Taapit deeplink to a future conversion (lead or sale).

Prerequisites

For conversion tracking to work, you only need two things:

Create a Taapit deeplink

In your Taapit dashboard, create a deeplink pointing to your website or landing page (e.g. taap.it/my-campaign → https://yoursite.com/landing).Make sure Conversion Tracking is enabled on the link.

Install the Taapit SDK on your site

Add either the script tag or the NPM package to your website or app. This is what reads the ta_tid from the URL and stores it in a cookie automatically.Option A — Script tag (simplest, no build step):

<script src="https://taap.it/api/sdk" data-publishable-key="pk_..."></script>

Option B — NPM package (React / Next.js / Vue…):

npm install taapit-sdk

That’s it. Once the SDK is on your site and the user arrives via a Taapit link, the ta_tid is captured and persisted automatically — no extra code needed for that part.

The ta_tid is only generated when a user clicks a Taapit deeplink. If a user navigates directly to your site, there is no tracking ID and no conversion will be attributed.

What is it?

When a user clicks a Taapit deeplink (e.g. taap.it/abc), our system generates a unique ta_tid and appends it to the destination URL:

https://yoursite.com/landing?ta_tid=rLnWe1uz9t282v7g

This ID is then used to attribute any subsequent lead or sale event back to the original click — along with all its metadata: UTM parameters, geolocation, device type, link ID, and workspace.

How is it generated?

The tracking ID is a 24-character hexadecimal string generated server-side using Node.js cryptography:

const trackingId = crypto.randomBytes(12).toString("hex");
// Example: "rLnWe1uz9t282v7g4a3b1c2d"

It contains no personal information — it is purely random and cannot be reverse-engineered.

How is it persisted?

Once the user lands on your site, the Taapit SDK automatically:

Reads the ta_tid from the URL query parameter
Stores it in a first-party cookie on your domain

Cookie name:   ta_tid
Duration:      365 days
Scope:         Root domain (e.g. .yoursite.com)

Because it is a first-party cookie set on your own domain, it is not blocked by browsers or privacy extensions.

How to retrieve it

From the Taapit SDK (recommended)

If you use the Taapit script or NPM package, the SDK handles everything automatically. You can access the tracking ID via:

// Vanilla JS / Script tag
const trackingId = window.taapit?.getTrackingId();

// NPM package — browser
import { getTrackingId } from "taapit-sdk/browser";

const trackingId = getTrackingId();

If you are not using the SDK, you can read the cookie directly:

function getTrackingId() {
  const match = document.cookie.match(/(?:^|;\s*)ta_tid=([^;]+)/);
  return match ? match[1] : null;
}

From the URL parameter (on page load)

const params = new URLSearchParams(window.location.search);
const trackingId = params.get("ta_tid");

If both the URL parameter and the cookie are present, the URL parameter takes precedence and overwrites the cookie — ensuring the most recent click is always attributed.

Passing it to your backend

Once retrieved client-side, pass the ta_tid to your backend when a conversion occurs (e.g. on form submit or checkout):

// Example: send ta_tid alongside a signup form
await fetch("/api/signup", {
  method: "POST",
  body: JSON.stringify({
    email: userEmail,
    trackingId: getTrackingId(), // from SDK or cookie
  }),
});

Your backend then forwards it to Taapit when calling /api/events/lead or /api/events/sale.

Properties

Property	Value
Parameter name	`ta_tid`
Cookie name	`ta_tid`
Format	Hexadecimal string, 24 characters
Generated by	`crypto.randomBytes(12).toString("hex")`
Cookie duration	365 days
Contains PII	No
First-party	Yes — set on your domain

Getting started

Conversions

API Reference

Prerequisites

What is it?

How is it generated?

How is it persisted?

How to retrieve it

From the Taapit SDK (recommended)

From the URL parameter (on page load)

Passing it to your backend

Properties

Next Steps

Track Leads

Track Sales

​Prerequisites

​What is it?

​How is it generated?

​How is it persisted?

​How to retrieve it

​From the Taapit SDK (recommended)

​From the cookie manually

​From the URL parameter (on page load)

​Passing it to your backend

​Properties

​Next Steps

Track Leads

Track Sales

Prerequisites

What is it?

How is it generated?

How is it persisted?

How to retrieve it

From the Taapit SDK (recommended)

From the cookie manually

From the URL parameter (on page load)

Passing it to your backend

Properties

Next Steps