Common Reasons for Capture Loss

Capture loss occurs when a cjevent is generated but never saved as a cookie. Causes fall into two categories: those the advertiser can address, and those driven by external factors.

The Click ID Is Lost During Redirects

Most common. Most preventable.

Many sites perform automatic internal redirects (HTTPS enforcement, URL normalization, load balancing, vanity URL forwarding). If any redirect strips query string parameters, the cjevent disappears before CJ's tracking code can read it.

The Landing Page Does Not Have CJ's Tracking Code

If the consumer lands on a page without the Universal Tag or server-side cookie logic, no cookies are written. Common causes:

• Destination URLs point outside the tag's deployment scope (blog subdomain, mobile domain, localized variant)
• Links use http instead of https, triggering a redirect to an untagged page
• The consumer passes through an intermediate page (interstitial, app-install prompt) before the tagged page

The Page Is Too Slow for the Tag to Fire

The Universal Tag runs asynchronously with other page scripts. On heavy pages, it may not finish before the consumer navigates away. The server-side cje cookie is not affected — another reason to implement both.

Cookie Consent Has Not Been Granted

In regions requiring opt-in consent (GDPR, IAB TCF), the Universal Tag may be blocked until consent is granted. If the consumer leaves or declines, no cookies are written.

• Advertisers cannot bypass consent requirements.
• Advertisers can influence how quickly the prompt appears and whether CJ's cookies are categorized correctly in the consent management platform.

Browser Privacy Features

These restrictions affect all affiliate and performance marketing platforms, not just CJ:

• Safari ITP — Shortens JavaScript-set cookie lifespans to as little as 24 hours; restricts cookies from known tracking redirect chains.
• Firefox ETP — Blocks known tracking scripts; limits cross-site cookie access.
• Consumer extensions and settings — Ad blockers and aggressive privacy settings can block first-party cookies and JavaScript entirely.
• Private/incognito browsing — Cookies persist only for the session and are deleted when the window closes.

Third-Party Plugins and Platform Apps

Marketplace plugins, extensions, and apps on ecommerce platforms are independently developed and can interfere with tracking:

• URL rewrites or query parameter stripping on redirect
• JavaScript conflicts with the Universal Tag
• Platform-level caching that skips server-side cookie logic

💡

The best defense is testing the full click-to-cookie flow after any change to your tech stack.

Actions Advertisers Can Take

Not all capture loss is preventable, but a significant portion is. These best practices are listed in order of impact.

Implement the Server-Side cje Cookie

Highest impact action.

• Set the cje cookie via HTTP set-cookie header at the server level, before the page loads.
• Not affected by slow JavaScript, ad blockers, or tag manager misconfiguration.
• Works even when the Universal Tag cannot.

🔧

This is a development task — your engineering team will need to add logic to read the cjevent from the inbound URL and set the cookie in the HTTP response.

Preserve Query String Parameters Through Redirects

• Ensure all internal redirects (HTTPS, URL normalization, vanity URLs, load balancers) carry query string parameters forward.
• The cjevent must be present in the URL when the final landing page loads.

💡

Quick test: Click a CJ tracking link and check the URL in your browser's address bar. If cjevent= is missing, your redirect chain is stripping it.

Deploy the Universal Tag on All Possible Landing Pages

Audit destination URLs. Common gaps:

• Subdomains (blog.example.com, m.example.com)
• Localized variants (/en-us/, /de-de/)
• Pages behind protocol redirects (http → https)

If using a tag manager (e.g., Google Tag Manager), confirm the container fires on all relevant templates and is not blocked by consent gating before the consumer navigates away.

Align Consent Management With Tracking Execution

• Ensure the Universal Tag fires as soon as consent is granted, not only on the next page load.
• Verify CJ's cookies are assigned to the correct consent category and the category name matches your CMP's configuration.

Test After Any Change to Your Tech Stack

• Click a CJ tracking link, land on your site, and verify cookies are written.
• Check for URL rewrites, JavaScript errors, and caching behavior.
• Make this part of your standard deployment checklist.