Click Events (cjevent)
What is cjevent?
When a customer clicks an affiliate link, CJ appends a unique identifier — cjevent — to the destination URL. This value is the click ID: a compact token that ties a specific publisher click to a specific customer session. Everything downstream — conversions, commissions, and attribution — traces back to this ID.
How it flows through your integration
click
is clicked
on your site
in query string
set
cookie, 13 months
fires
with order data
the sale
commission
Capture Rate Definition
Every time a consumer clicks a publisher's affiliate link, CJ creates a unique click event ID called a cjevent. For CJ to credit that click when the consumer later makes a purchase, the cjevent must be saved as a first-party cookie in the consumer's browser.
- Capture rate is the percentage of clicks where the
cjeventwas successfully saved. - If the
cjeventis not saved, CJ cannot match the click to a conversion and the publisher does not receive attribution. - A rate below 100% does not necessarily mean something is broken — some loss is expected across all click-based affiliate platforms.
- The goal is to minimize the loss that is within your control.
How CJEVENT Tracking Works
When a consumer clicks a publisher's link:
- CJ creates a click ID. CJ's tracking servers generate a unique
cjeventvalue. - The consumer is redirected. CJ sends the consumer to the advertiser's landing page with the
cjeventappended to the URL (e.g.,?cjevent=abc123). - The click ID is saved. Two mechanisms write the
cjeventas a cookie:- Server-side (
cjecookie) — The advertiser's server reads thecjeventfrom the URL and sets a cookie via HTTPset-cookieheader before the page loads. Fast and resilient. - Client-side (Universal Tag) — CJ's JavaScript tag reads the
cjeventfrom the URL after the page loads and writes two cookies:cjevent_dcandcjevent_sc. Thecjevent_sccookie requires a reverse proxy deployment.
- Server-side (
- CJ confirms the result. The Universal Tag checks for cookies beginning with
cjand reports whether they were written. This is how capture rate is measured.
Why Both Mechanisms Matter
- The server-side
cjecookie is set before the page renders — it works even if JavaScript is slow or blocked. - The Universal Tag cookies are set after the page loads — they depend on JavaScript executing before the consumer navigates away.
- Having both in place provides the best coverage.
Industry-Wide Tracking Limitations
Some tracking gap will remain after all preventable causes are addressed. These factors affect every affiliate and performance marketing platform.
Browser Privacy Is Getting Stricter
- Safari ITP, Firefox ETP, and Chromium-based changes all reduce cookie-based tracking reliability over time.
- First-party cookies (CJ's approach) are more resilient than third-party cookies, but not immune — Safari limits JavaScript-set cookie lifespans and scrutinizes redirect-chain cookies.
- These changes respond to consumer privacy expectations and are unlikely to reverse.
Consumer Behavior Creates a Baseline Level of Loss
- Clearing cookies, private browsing, device switching, and ad-blocking extensions all cause loss.
- None of these behaviors can be detected or prevented by the advertiser or CJ.
- This affects all browser-based measurement: affiliate, display, paid search, and social.
Privacy Regulations Are Expanding
- GDPR, ePrivacy, CCPA/CPRA, and similar regulations give consumers the right to decline tracking.
- Consent management adds a step between click and cookie.
- As more jurisdictions adopt privacy regulations, consent-gated traffic will continue to grow.
What This Means for Your Program
- Some tracking gap is normal — it reflects how the modern web works, not a broken integration.
- CJ continues to invest in server-side click ID storage and monitoring of browser and regulatory changes.
- Your CJ account team can review your capture rate data and help identify actionable areas for improvement.
Updated 11 days ago
