What Is Commission Junction?

Commission Junction provides a platform that connects advertisers with a network of publishers, making it easier for both parties to find suitable partnerships. Publishers promote the advertisers’ products through various channels such as websites, blogs, social media, email marketing, etc. When a user clicks on an affiliate link and completes a desired action, the publisher earns a commission.

What are the benefits of integrating MetaRouter with Commission Junction?

MetaRouter’s integration provides a straightforward way to send customer data to Commission Junction. Collect data on websites, control your data with event mappings customized to your business's needs, and send it to Commission Junction without the use of Commission Junction’s tag.

Key Features:

Enables Commission Junction tag removal.
No effect on website load latency.
Ensures event data is streaming into Commission Junction for accurate commission reporting.

Getting Started - From Your Commission Junction Account

Grab an access token
- Log in to the developer portal and create a new access token here: https://developers.cj.com/account/personal-access-tokens
  - Please make sure to store it somewhere safely as once they navigate away from this page the token will now be hidden for security purposes.

Please contact your Commission Junction support team to get the following:
- Enterprise ID
- Action Tracker ID
  - Important note on the action tracker: Please communicate to your Commission Junction support team about the kinds of parameters you will be sending them. If you are sending parameters such as SKU, qtyx, and amtx, then you will need an Advanced Integration action tracker ID. If you are sending basic information about a transaction and not tracking item-level data about a purchase or lead, then you will ask for a Simple Integration action tracker ID.
  - The default playbook uses Simple Integration actions. If you are using Advanced Integration actions, item-level parameters must be included in your events. Please reach out to your Commission Junction rep for a full list of supported parameters.

Getting Started - From Your MetaRouter Account

Adding a Commission Junction integration.

From the integration library, add a Commission Junction integration. Then, fill out the Connection Parameters:

Connection Parameter	Description
`ACCESS_TOKEN`	Token obtained from the Commission Junction developer portal.
`ACTION_TRACKER_ID`	This will be provided to you by your Commission Junction support team.
`ENTERPRISE_ID`	This will be provided to you by your Commission Junction support team.
`ENDPOINT`	This will be `graphql`.

Adding a Commission Junction Sync

To gather the cjevent value, you must add a Commission Junction sync.

From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three-dot dropdown and select “Build AJS File.”
In the Identity Syncs section, select the Commission Junction sync.
Fill out the following fields:
1. Cookie Lifetime (in days) - 390 days is recommended
Scroll down and click the Save and Build File button.
Deploy your AJS file to propagate changes to your web property.

Event Mappings

MetaRouter provides all of the event mappings that Commission Junction integrations typically require. You may add custom events, parameters or mappings following Commission Junction’s API documentation.

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output Key	Description	Expected Input
enterpriseID Required	Type: String This is will pull the value of the Enterprise_ID as set in the Connection Parameters.	Enterprise_ID
orderID Required	Type: String The advertiser-supplied Order ID number that identifies the transaction Text string, truncated after the 96th character. CJ prohibits the submission of personally identifiable information—such as a full or partial email address—in the OID value. Note: Include only alphanumeric characters within the OID field to avoid errors. You must URL-encode any special characters or extra spaces used in this field.	properties.order_id
actionTrackerID Required	Type: String The CJ-assigned Action ID for the commissionable sale or lead.	NA - Expression

Output Key

Description

Expected Input

enterpriseID Required

Type: String
This is will pull the value of the Enterprise_ID as set in the Connection Parameters.

Enterprise_ID

orderID
Required

Type: String
The advertiser-supplied Order ID number that identifies the transaction Text string, truncated after the 96th character.

CJ prohibits the submission of personally identifiable information—such as a full or partial email address—in the OID value.

Note: Include only alphanumeric characters within the OID field to avoid errors. You must URL-encode any special characters or extra spaces used in this field.

properties.order_id

actionTrackerID
Required

Type: String
The CJ-assigned Action ID for the commissionable sale or lead.

NA - Expression

Event Specific

The events below are required for accurate reporting within Commission Junction.

order_completed

Output Key	Description	Expected Input
cjEvent Required	Type: String Unique CJ-generated token passed to your site, on click, that stores referring publisher data for cookieless attribution.	cjevent
amount Required, if using Simple Integration Action Tracker	Type: Number The data you provide must correspond to the associated Action Tracker ID. All values must be in decimal format. If not specified, prices default to the advertiser's functional currency. No other characters, such as dollar signs or commas are supported. Simple Sale Actions The subtotal of a sale or lead-based action.	properties.revenue
discount Optional	Type: Number This is an optional field used to track whole order discounts for simple and item-based orders.	properties.discount
coupon Optional	Type: String This is used to track a coupon applied to the order, ie SPRING25 Field length: 256 characters	properties.coupon
currency Required	Type: String Three-character code representing the currency in which your transaction should be processed.	properties.currency
eventTime Required	Type: String Timestamp of when event occured.	timestamp
verticalParameters.orderSubtotal Optional	Type: Number Revenue ($) associated with the transaction, excluding shipping and tax.	properties.revenue
verticalParameters.taxAmount Optional	Type: Number Total tax associated with the transaction.	properties.tax
verticalParameters.itemId Optional	Type: String Id for the item. (Simple Actions Only).	N/A - Expression

order_updated

Output Key	Description	Expected Input
amount Required, if using Simple Integration Action Tracker	Type: Number The data you provide must correspond to the associated Action Tracker ID. All values must be in decimal format. If not specified, prices default to the advertiser's functional currency. No other characters, such as dollar signs or commas are supported. Simple Sale Actions The subtotal of a sale or lead-based action.	properties.revenue
discount Optional	Type: Number This is an optional field used to track whole order discounts for simple and item-based orders.	properties.discount
coupon Optional	Type: String This is used to track a coupon applied to the order, ie SPRING25 Field length: 256 characters	properties.coupon
currency Required	Type: String Three-character code representing the currency in which your transaction should be processed.	properties.currency
updateTime Required	Type: String Timestamp of when event occured.	timestamp
verticalParameters.orderSubtotal Optional	Type: Number Revenue ($) associated with the transaction, excluding shipping and tax.	properties.revenue
verticalParameters.taxAmount Optional	Type: Number Total tax associated with the transaction.	properties.tax
verticalParameters.itemId Optional	Type: String Id for the item. (Simple Actions Only).	N/A - Expression

order_canceled

Output Key	Description	Expected Input
updateTime Required	Type: String Timestamp of when event occured.	originalTimestamp

Required Identifiers

These identifiers must be mapped to Commission Junction in order for successful user matching to occur.

Attribute	Example	Sync Injector Required?
cjevent Required	`&cjevent=adlj3gw5WWjns97fgwsf`	Yes

Additional Commission Junction Documentation