Commission Junction

Send conversion and transaction data to Commission Junction (CJ Affiliate) server-to-server for affiliate tracking, commission attribution, and publisher reporting.

⚠️

This blueprint is currently alpha — schema and behaviour may change before GA.

Prerequisites

Complete these steps in the CJ Affiliate platform before configuring Signal.

Create a CJ Affiliate account

Find your Enterprise ID

Navigate to Account > Network Profile in the CJ Account Manager. Your Enterprise ID (also called Company ID) is displayed on the profile page. This identifies your organisation within the CJ network.

Find your Advertiser ID

Go to Account > Web Settings. Your Advertiser ID (also called CID) is shown in the account details. If you manage multiple advertiser accounts, select the correct one.

Create a Personal Key

Navigate to Account > Personal Key (or Account > API Credentials). Click Create Key to generate a new personal API key. Copy the key immediately as it will not be shown again. This key authenticates server-to-server conversion calls.

Define an Action ID

Go to Advertiser > Actions and create or locate the action (conversion type) you want to track. Each action has an Action ID that identifies the specific conversion type (e.g. sale, lead, registration). Note this ID for your Signal configuration.

Verify tracking parameters

Ensure your CJ tracking links include the required parameters (e.g. cjevent click ID). Server-to-server conversions require a valid click reference for attribution.

Configuration

Field	Type	Required	Description
`enterprise_id`	string	Yes	Your CJ Enterprise ID from Account > Network Profile.
`personal_key`	secret	Yes	Your CJ personal API key from Account > Personal Key.
`advertiser_id`	string	Yes	Your CJ Advertiser ID (CID) from Account > Web Settings.
`action_id`	string	Yes	The CJ Action ID for the conversion type being tracked.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Commission Junction or filter by Attribution.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/commission_junction/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Commission Junction",
    "variant": "default",
    "config": {
      "enterprise_id": "1234567",
      "personal_key": "your_personal_key",
      "advertiser_id": "7654321",
      "action_id": "12345"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The Retail variant maps the following Datafly events to CJ conversion events:

Datafly Event	CJ Event	Notes
`Product Added`	`add_to_cart`	Cart-stage event (no commission)
`Order Completed`	`purchase`	Requires `orderId`, `amount`, `currency`, `actionId`
Custom events	Passed through	Add the CJ action type in the blueprint event map

Identity

The default blueprint forwards the following identifiers to CJ:

Source	CJ field
`user_id`	`customer_id`
`context.ip`	`ip_address`
`context.user_agent`	`user_agent`

CJ’s cjevent click ID is the primary attribution token. Capture it from inbound URLs on your landing page and pass it via Datafly.js so it reaches CJ with each conversion.

Default consent category: advertising.

CJ requires the cjevent click ID to attribute conversions to the correct publisher. Ensure your site captures the cjevent parameter from landing page URLs and includes it in Signal events.

Verify it’s working

Generate a test click through a CJ tracking link to create a valid cjevent reference.
Complete a test conversion on your site that triggers a Datafly event.
In the Signal Management UI, open your Commission Junction integration and watch the Live Events stream.
In the CJ Account Manager, navigate to Reports > Transaction Detail to verify the test conversion (allow up to 30 minutes for processing).
Confirm 200 responses in Signal’s Live Events log.

Troubleshooting

Symptom	Cause	Resolution
`401 Unauthorized`	Invalid personal key	Regenerate the personal key in Account > Personal Key and update Signal.
`400 Bad Request`	Invalid Action ID or Advertiser ID	Verify `action_id` and `advertiser_id` match active values in CJ.
Conversions not appearing	Missing `cjevent` click ID	The CJ click event parameter must be captured and forwarded with the conversion.
Wrong action type	Incorrect `action_id`	Ensure the Action ID matches the conversion type (sale, lead, etc.).
Duplicate conversions	Same order ID sent twice	CJ deduplicates by order ID within an action; ensure unique order references.

Visit CJ Affiliate documentation for full API reference and credential setup instructions.

Blueprint

The CJ Affiliate blueprint version is 0.1.0 (alpha). It ships with a Retail variant covering add_to_cart and purchase conversion events.