Connecting CJ Affiliate to 6sense
CJ operates at enterprise scale with sophisticated commissioning rules, which means the same publisher can be paid differently by product, by customer status or by placement — and getting those inputs wrong pays real money incorrectly. 6sense works at the account level rather than the person level, which inverts the usual assumption: the thing you are trying to identify is a company, and the individual is almost incidental. The join between them succeeds or fails on one thing: whether the resolved account, not a person reaches the CJ transaction before the conversion happens, because 6sense can only match a conversion it can tie back to a click it recognizes.
Free30 minutesNo obligation
Specific to this pair
CJ Affiliate and 6sense: when publisher sales mean account intent
For a retail CJ Affiliate program, send nothing to 6sense: household orders on personal emails cannot be placed on an account. For B2B or software programs, record the CJ publisher ID and cjevent on the lead in your CRM at signup, and let 6sense read account activity from the CRM rather than receiving CJ transactions directly.
Most CJ programmes sell to consumers, and a CJ transaction is a household order paid to a publisher. 6sense has no use for that: a Gmail address on a $60 order cannot be placed on an account, and pushing a few thousand of them only adds noise to intent models built for buying committees. If your programme is retail, the honest answer is to send nothing here.
The exception is a B2B or software programme on CJ, where review and comparison publishers send trial sign-ups or first purchases. There the useful join is the company domain on the converting email, plus the fact that a CJ publisher drove it. Record the publisher ID and the cjevent on the lead in your CRM at sign-up, and let 6sense read the account activity from the CRM rather than receiving CJ transactions directly. That way three sign-ups from one company through one comparison site show up as one account evaluating you.
The commissioning inputs CJ cares about do not carry over cleanly. CJ's new-versus-returning status is about the person's order history; 6sense cares whether the account is already a customer or in an open opportunity. A new person from an existing customer account can be commissioned as new in CJ while 6sense correctly treats it as expansion. Decide which definition your CJ rates are meant to reward before the two disagree in a commission review.
CJ → 6sense · what breaks
Why this join usually fails — CJ → 6sense
- 01
The resolved account, not a person never reaches CJ
The publisher click identifier must survive to checkout, and enterprise stores frequently have several checkout paths.
- 02
Commissioning rules fed the wrong inputs
A new-customer rate applied to returning customers because the status flag was never wired is a direct overpayment on every affected order, compounding quietly until somebody audits the programme.
- 03
Counting people when the buyer is a committee
Four people from one company downloading four things is not four conversions. It is one account in an active evaluation, and reporting it as four inflates every lead metric while hiding the only fact that matters — that one specific company is in market.
- 04
Nothing reconciles afterwards
6sense shows the account timeline with contributing events. Check the account, not the contact, and confirm the event resolved to the right company rather than to an ISP.
CJ → 6sense · the fix
What working looks like — CJ → 6sense
The resolved account, not a person on every conversion
Conversions arriving in 6sense
The event joins the account's intent profile and contributes to its predicted buying stage.
Reconciled against the source
CJ Affiliate's own records are the reference, not either dashboard.
CJ → 6sense · architecture
How CJ and 6sense actually connect
- 1
CJ Affiliate holds the truth
Rules commonly commission new customers differently from returning ones. If your order does not carry customer status correctly, publishers are paid the wrong rate systematically and neither side notices for months.
- 2
6sense needs a click to match
6sense needs the account identity — domain, or a resolved company — plus the event and its context. A conversion with only a personal email and no company context cannot be placed on an account.
- 3
The identifier is the bridge
The resolved account, not a person, captured at the visit and carried into the CJ transaction.
- 4
The event source decides reliability
Send orders net of commission, carrying the fields the commissioning rules depend on.
- 5
Deduplication at the destination
Deduplication is at the account level. Several people from one company converting is one account showing strong intent, not several conversions, and treating it as several is the fastest way to misread a single deal as a pipeline.
CJ → 6sense · normal or broken
Working vs. broken, side by side — CJ → 6sense
Normal, not a fault
The resolved account, not a person present on the conversion
Visible on the record itself in CJ Affiliate, not merely captured somewhere on the site.
Sent from your order record with CJ attribution
Deduplicated correctly
Deduplication is at the account level. Several people from one company converting is one account showing strong intent, not several conversions, and treating it as several is the fastest way to misread a single deal as a pipeline.
Reconciles with the source
6sense's count and CJ Affiliate's records agree within a few percent over a closed window.
Actually broken
The resolved account, not a person missing on most records
The publisher click identifier must survive to checkout, and enterprise stores frequently have several checkout paths.
Sent from the browser
A new-customer rate applied to returning customers because the status flag was never wired is a direct overpayment on every affected order, compounding quietly until somebody audits the programme.
Counted twice, or not at all
Four people from one company downloading four things is not four conversions. It is one account in an active evaluation, and reporting it as four inflates every lead metric while hiding the only fact that matters — that one specific company is in market.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to CJ Affiliate.
CJ → 6sense · diagnose
Diagnostic order — CJ → 6sense
- 01
Count conversions carrying the resolved account, not a person
- 02
Follow one real conversion end to end
From the ad click through CJ and into 6sense.
- 03
Verify that new-versus-returning status reaches CJ correctly
Sample recent transactions and compare against your own customer records. Mismatches are money.
- 04
Compare lead count against distinct accounts for a month
The ratio tells you how badly person-level counting is distorting your view of the pipeline.
- 05
Read the match rate, not the success message
6sense shows the account timeline with contributing events. Check the account, not the contact, and confirm the event resolved to the right company rather than to an ISP.
CJ → 6sense · prove
How it gets proven — CJ → 6sense
Against CJ Affiliate's own records, not against either platform's dashboard.
Source of truth
Orders flagged by publisher, with the commissioning inputs recorded on the order.
- The resolved account, not a person confirmed present on a live conversion.
- A real conversion followed from click through CJ to 6sense.
- Events confirmed on the correct account timeline, with lead-to-account ratios stated so person-level inflation is visible.
- Transactions reconciled per order with commissioning inputs verified against your own customer data.
CJ → 6sense · free audit
What we check in the free audit
- Count conversions carrying the resolved account, not a person
- Follow one real conversion end to end
- Verify that new-versus-returning status reaches CJ correctly
- Compare lead count against distinct accounts for a month
- Read the match rate, not the success message
Checked against
Orders flagged by publisher, with the commissioning inputs recorded on the order.
Free30 minutesNo obligation
CJ → 6sense · when not to buy
When you don't need this — CJ → 6sense
- If 6sense already reports conversions that reconcile against CJ Affiliate's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred conversions and count how many carry the resolved account, not a person.
- Simple flat-rate programmes have no commissioning inputs to get wrong.
- If you sell to individuals rather than to organizations, account-level resolution has nothing to resolve and this is the wrong shape of tool.
CJ → 6sense · what we deliver
What gets built — CJ → 6sense
Identifier capture into CJ
Capture the identifier and the customer status on the order, and verify both across every checkout path you operate.
Event source: your order record with CJ attribution
Send orders net of commission, carrying the fields the commissioning rules depend on.
Dispatch to 6sense
Server-side event push with the account identifier and event context, from your CRM or product.
Reversals where they exist
Refunds reverse and reverse the commission.
Written guarantee
95%+ tracking accuracy
Measured against Orders flagged by publisher, with the commissioning inputs recorded on the order.. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
CJ → 6sense questions, answered
Only indirectly. Store the CJ publisher on the CRM lead at sign-up and report against 6sense account segments from the CRM; 6sense itself has no field for an affiliate publisher.
Not for a consumer programme, because personal emails cannot be resolved to accounts. For B2B programmes, send the lead or account activity from your CRM with the company domain, not the CJ transaction itself.
Almost always because the resolved account, not a person never reached the CJ transaction. The publisher click identifier must survive to checkout, and enterprise stores frequently have several checkout paths. Measure coverage before debugging the dispatch.
6sense resolves traffic to companies through IP and identity graph data, then models buying stage from behaviour across the account. There is no click identifier and no individual to match. A conversion sent here is evidence about an organization, and sending it person-by-person misses the point of the product entirely.
Your order record with CJ attribution. Send orders net of commission, carrying the fields the commissioning rules depend on.
6sense shows the account timeline with contributing events. Check the account, not the contact, and confirm the event resolved to the right company rather than to an ISP.
More on CJ → 6sense
- CJ → Google AdsConnecting CJ Affiliate to Google Ads
- CJ → MetaConnecting CJ Affiliate to Meta Conversions API
- CJ → GA4Connecting CJ Affiliate to GA4
RELATED GUIDES
Where CJ → 6sense fits in the rest of your tracking
- Rewardful → 6senseConnecting Rewardful to 6sense
- LeadDyno → 6senseConnecting LeadDyno to 6sense
- Refersion → 6senseConnecting Refersion to 6sense
- CJ → SalesforceConnecting CJ Affiliate to Salesforce
- CJ → HubSpotConnecting CJ Affiliate to HubSpot
- SaaSConversion tracking for SaaS, from signup through to the payment that matters
- Tapfiliate → 6senseConnecting Tapfiliate to 6sense
- FirstPromoter → 6senseConnecting FirstPromoter to 6sense
Free · 30 min
Get CJ and 6sense joined properly
Free30 minutesNo obligation
