How LeadDyno Cookie Tracking Works (and Which Cookies We Use)

LeadDyno uses cookies to track visits, leads, and purchases so we can properly attribute them to your affiliates. This article explains how that tracking works and which cookies are involved.

All of the cookies listed in this article are required for LeadDyno tracking to function as expected.

How Cookie-Based Tracking Works

When a visitor clicks an affiliate link and lands on your website:

The click is recorded by LeadDyno, along with affiliate information and the landing URL.
LeadDyno sets tracking cookies in the visitor’s browser (described in detail below).
As the visitor browses and eventually submits a lead form or completes a purchase, those cookies are read to match the activity back to:
- The correct affiliate
- The original visit and traffic source

LeadDyno then records the visit, lead, and/or purchase in your account so you can accurately report and pay commissions.

First-Party vs Third-Party Cookies

LeadDyno’s tracking relies on cookies stored under the LeadDyno domain. When your visitor is on your website (e.g., yourstore.com), these cookies are treated by the browser as third-party cookies.

Your site domain: where the visitor is browsing (e.g., yourstore.com).
LeadDyno domain: the tracking/analytics domain (e.g., leaddyno.com).

Because of this:

Third-party cookies must be allowed for LeadDyno’s tracking to work as expected.
If a browser or privacy tool blocks third-party cookies, LeadDyno may not be able to:
- Recognize returning visitors
- Attribute leads or purchases to the original affiliate

We recommend documenting this behavior in your cookie policy and consent management tools, and ensuring that cookies from the LeadDyno domain are permitted when visitors provide consent.

LeadDyno Tracking Cookies

LeadDyno uses a small set of cookies, all starting with LD_. Each cookie has a specific role in tracking visits, leads, and purchases.

LD_U — Initial Landing Page

Name: LD_U
Purpose: Stores the initial landing page URL where the visitor first arrived on your site.
Used for:
- Understanding which page started the session
- Reporting on which landing pages convert best

When set: On the visitor’s first recorded visit.

LD_R — Original Referrer

Name: LD_R
Purpose: Stores the referrer (the page that sent the visitor to your site) on the first visit.
Used for:
- Identifying traffic sources (e.g., social, email, another website)
- Providing more detail on how the visitor originally found you

When set: On the visitor’s first recorded visit.

LD_T — Visitor Tracking ID

Name: LD_T
Purpose: Stores the unique ID generated by LeadDyno for each visitor.
Used for:
- Linking all subsequent actions (visits, leads, purchases) back to the same browser/device
- Ensuring that affiliate attribution remains consistent across pages

When set: As soon as LeadDyno first identifies a new visitor.

This is the core cookie that ties a visitor’s activity together over time.

LD_L — Lead Information

Name: LD_L
Purpose: Stores lead information captured by LeadDyno when a visitor becomes a lead (for example, by filling out a form).
Used for:
- Associating captured lead data (such as email) with the original visit and affiliate
- Ensuring that lead events are recorded correctly in LeadDyno

When set: When a new lead is captured via your site.

LD_P — Purchase Data (JavaScript Tracking)

Name: LD_P
Purpose: Stores purchase data captured by LeadDyno for orders tracked via JavaScript.
Used for:
- Associating purchase events with the correct visitor and affiliate
- Supporting JavaScript-based purchase tracking when native/platform integrations are not used

When set: When a purchase is captured using JavaScript-based tracking on your site.

This cookie is only used for JavaScript-based purchase tracking.

LD_EXT — External / Platform-Specific Tracking ID

Name: LD_EXT
Purpose: Stores a platform-specific tracking ID for certain integrations that require an additional external ID.
Used for:
- Handling platform limitations where LeadDyno must use an extra identifier
- Keeping LeadDyno’s internal visitor ID in sync with an external platform’s tracking ID

When set: When you’re using an integration that relies on an extra, platform-specific ID.

LD_S — Internal State for Visit/Lead Sync

Name: LD_S
Purpose: Stores internal state information used by LeadDyno to send visit and lead data periodically.
Used for:
- Managing background communication between the browser and LeadDyno
- Ensuring visits and leads are sent reliably, even if they happen over time

When set: During browsing sessions, as LeadDyno sends visit/lead data.

This cookie is used for internal state only and is part of the mechanism that keeps tracking reliable.

What Happens If Cookies Are Blocked or Cleared?

If third-party cookies or cookies from the LeadDyno domain are blocked:

New visitors may not receive a tracking ID, so:
- Visits may not be recorded
- Leads and purchases may not be attributed to affiliates
Returning visitors may appear as new visitors, breaking continuity.
If a user clears cookies or switches devices/browsers, LeadDyno can’t link the new session to the previous one.

To minimize issues:

Ensure your cookie banner/consent tool allows cookies from the LeadDyno domain once a visitor consents.
Document LeadDyno’s cookies in your privacy/cookie policy.
Avoid browser extensions or security settings that block all third-party cookies if you rely heavily on affiliate tracking.

FAQs

Are these cookies required?
Yes. All of the LD_ cookies listed above are required for LeadDyno tracking to function as expected.

Do these cookies store sensitive payment data like credit card numbers?
No. These cookies store IDs and tracking-related information (visits, leads, purchases, platform IDs), not full payment details.

Do I need to list these cookies in my Privacy Policy or Cookie Policy?
We strongly recommend that you do. You can list the cookie names (LD_U, LD_R, LD_T, LD_L, LD_P, LD_EXT, LD_S), along with a short description and purpose for each.

In This Article