Commission Junction

Commission Junction (CJ) provides a global affiliation network connecting businesses with customers. Using this destination you can implement server-side tracking.

Key features

The Commission Junction destination provides the following key features:

• Events structure: our Events reference covers Commission Junction server-side tracking, meaning that your data is properly bridged to the expected fields in an optimized way.

• Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

• Smart mapping: data mapping can be readjusted using your datalayer defined fields.

• Refined data: you can freely push additional information based on your specific needs.

• Support for multi-item data: information included in the item array is bridged to Awin.

Destination setup

Configuration

Settings	Description
CJ Enterprise Id	Required Your "Enterprise ID" as provided by Commission Junction. This setting supports dynamic values [1][2].
Mapping	Required Map your Commanders Act event(s) with CJ ActionId(s) by setting a Your Event Name and a CJ Action Id. At least one entry is required.
CJ Event Cookie Name	Enter a cookie name holding CJ Event value. This value is passed by Commission Junction in landings (E.g. https://www.example.com/?cjevent=656e8fa049ec11ea8237023d0a240612). This is required if the "Smart Mapping" field Click Id (cjevent) is empty. The field Click Id (cjevent) has priority over this field.
Custom Event Properties	Map your custom event properties by setting their field names in CJ property name and adding the field name holding the value in Your event property. E.g. if you inputsizein the CJ property name and items.0.product.size in Your event property, you'll have a custom event property in CJ calledsizewith a value based on the content of the field items.0.product.size [2].

[1] This feature allows you to set an event property holding a dynamic value by adding two open braces ({{) in front of your property name and two close braces (}}) at the end (E.g. {{myEventPropertyPathAndName}}). [2] Using "dots" (".") you can navigate deeper to the specific property you want to get the value of. See Events reference for more details on the standard field names by event. You can also freely set custom fields: there are no boundaries.

Field mappings

Most properties can be remapped using our "Smart Mapping" feature. Setting the configuration field CJ Event Cookie Name is not mandatory if the "Smart Mapping" field Click Id (cjevent) is set. The latter has precedence over the former.

Commanders Act Properties	CJ Properties
CJ Enterprise Id	CID
CJ Action Id	TYPE
Click Id (cjevent) [1] CJ Event Cookie Name	CJEVENT [2]
event_timestamp	eventTime [3]
id	OID
currency	currency
revenue	amount [4]
coupon	coupon
items.X.product.id	ITEMY [5]
items.X.product.price	AMTY [5]
items.X.quantity	QTYY [5]
items.X.discount	DCNTY [5]
Commanders Act event property or static value	Event property name [6]

[1] "Smart Mapping" field. [2] Click Id (cjevent) has priority over CJ Event Cookie Name . [3] Automatically converted in the ISO 8601 format. [4] If items are present, this property won't be included. [5] For each item: X and Y are incremental numbers, starting from0and1respectively. [6] See Custom Event Properties in Configuration for more details. The signature CJ optional property can be set using this feature.