Guides
  1. Concurrent Tracking & Server-Side
  2. New Orders Data File

Implementation

📋Before You Implement
  • Each order requires a unique combination of actionTrackerId, enterpriseId, subscriptionId, and orderId to be processed.
  • Replace all placeholder values with your actual data. Brackets are for illustration only and should not appear in your final file.
  • Orders must use past dates — future event times are not accepted.
  • Only CSV (Comma Separated Values) format is accepted. Do not include commas within field values, as they will break parsing.

New Orders File Example

Orders Data File - Sample CSV
UTF-8 · comma-delimited · 2 sample rows
Standard e-commerce order with line items, quantities, and subtotals.
Fields - hover for details
companyId
enterpriseId
subscriptionId
actionTrackerId
orderId
cjEvent
eventDate
amount
currency
itemSku
itemQty
itemUnitPrice
itemDiscount
coupon
companyIdenterpriseIdsubscriptionIdactionTrackerIdorderIdcjEventeventDateamountcurrencyitemSkuitemQtyitemUnitPriceitemDiscountcoupon
3982101234567398210398210ORD-100421a2d5f1109a2b11ef9b21002590943fe42025-06-15T14:22:00Z149.98USDSKU-BLK-LG274.990.00SUMMER10
3982101234567398210398210ORD-204532ef34bc20b22a11ec957a0242ac1200022025-06-14T19:11:00Z51USDSKU-GRN-SM424.9920.00SUMMER10

Building Your New Orders File

Header Row

The first row of your file must contain the field names you intend to submit. Only include fields you are populating — unused fields do not need to appear in the header. The order of columns in the header determines the order of values in every data row.

Header Fields

Click any row to see type, format, and value examples.
Parameter
Description
Required
companyId
Return either companyId or enterpriseId — at least one account identifier must be present.
Required
enterpriseId
Return either companyId or enterpriseId — at least one account identifier must be present in each record.
Required
subscriptionId
The Subscription ID for this new order data file - only one subcriptionId is accepted per file.
Required
actionTrackerId
This is a static value provided by CJ. Each account may have multiple actions and each will be referenced by a different actionTrackerId value.
Required
orderId
Your internal Order ID that uniquely identifies the transaction. Used to reconcile orders between your system and CJ.
Required
Type: StringFormat: Alphanumeric only. Truncated after 96 characters.
Examples
Order145683
ORD-2024-001234
Note: Do not include PII such as full or partial email addresses.
eventTime
The date and time the order was placed. Future dates are not accepted.
Required
Type: numberFormat: ISO 8601 preferred. Multiple formats supported — see note.
Examples
1970-03-27T12:13:14-05:00
1970-03-27T12:18:14Z
09/15/2023 14:30:45
2023-09-15 14:30:45
15-Sep-2023 14:30
Note: ISO 8601 with Z as the UTC zone designator is preferred. If no time zone offset is provided, CJ interprets the time as UTC. Future dates are rejected.
cjEvent
The unique CJ-generated token passed to your site on click. Stores referring publisher data and is the primary attribution signal.
Required
Type: String
Examples
adlj3gw5WWjns97fgwsf
Note: Either cjEvent or the adId + promotionalPropertyId combination must be provided. If cjEvent and AID/PID are all passed, cjEvent takes precedence. If none are provided, the order will fail in processing.
adId
The CJ Link ID passed in the affiliate click-through URL to your site. Used as a fallback attribution signal when cjEvent is unavailable.
Conditionally Required
Type: Integer
Examples
9876543
Note: Must be provided together with promotionalPropertyId if cjEvent is not available.
promotionalPropertyId
The referring publisher's Promotional Property ID passed in the affiliate click-through URL. Used as a fallback attribution signal when cjEvent is unavailable.
Conditionally Required
Type: Integer
Examples
1122567
Note: Must be provided together with adId if cjEvent is not available.
sid
Shopper ID supplied by the publisher and passed in the click-through URL. Include this only if it was passed on click-through.
Optional
Type: StringFormat: Alphanumeric, max 64 characters, case sensitive
Examples
shoPPer8675309
amount
The order subtotal of the transaction. Do not include shipping, tax, or fees. Required for standard (non-item-based) actions.
Recommended
Type: DecimalFormat: Numeric only — no dollar signs, commas, or currency symbols
Examples
19.99
124.50
Note: Values default to the advertiser's functional currency if currency is not specified.
discount
Whole order discount applied to the transaction. Supported for both standard and item-based orders.
Recommended
Type: DecimalFormat: Numeric, max 2 decimal places
Examples
10.99
Note: For item-level discounts on advanced actions, use itemDiscount or the discount value within the items field instead.
currency
Three-character ISO 4217 code representing the currency in which the transaction should be processed.
Required
Type: StringFormat: ISO 4217 three-letter currency code
Examples
USD
GBP
EUR
Note: Refer to the CJ Support Center for the full list of supported currency codes.
coupon
The coupon or promotional code applied to the order.
Recommended
Type: StringFormat: Max 256 characters
Examples
SPRING25
Note: Omit this field if no coupon was applied.

Item-Level Fields

Item-level data is required for Advanced Sale Actions (item-based commissions). You can provide item data using either the combined items field or the four separate item fields (itemSku, itemUnitPrice, itemQuantity, itemDiscount). Do not mix both approaches in the same file.

Click any row to see type, format, and value examples.
Parameter
Description
Required
items
Combined field for passing all item-level data in a single column. Includes SKU, unit price, quantity, and optional item discount per line item. Separate multiple items with double semicolons (;;).
Required
Type: StringFormat: sku;unitPrice;quantity or sku;unitPrice;quantity;discount — separate multiple items with ;;
Examples
sku123;19.99;1
sku123;19.99;1;1.99
sku123;19.99;1;;sku456;10.47;3
sku123;19.99;1;1.99;;sku456;10.47;3;2.99
Note: SKU values must be alphanumeric, max 100 characters, and must not contain semicolons. SKU values must exactly match values in your CJ item lists and product catalog for item-based commissions to function correctly. Item discount applies to the total for that SKU — a 2.56 discount on quantity 2 distributes to 1.28 per unit.
itemSku
Item SKU for each product in the cart. Use as an alternative to the combined items field. Multiple values separated by a semicolon.
Required
Type: StringFormat: Alphanumeric, max 100 characters per SKU, semicolon-delimited
Examples
sku123;sku456;sku789
Note: SKU values must exactly match values in your item lists and product catalog. Do not include semicolons within individual SKU values.
itemUnitPrice
Unit price for each item in the cart. Corresponds positionally to itemSku values. Multiple values separated by a semicolon.
Required
Type: DecimalFormat: Numeric, semicolon-delimited
Examples
10.99;19.99;25.55
Note: Represents the unit price of one item — do not multiply by quantity.
itemQuantity
Quantity of each item purchased. Corresponds positionally to itemSku values. Multiple values separated by a semicolon.
Required
Type: IntegerFormat: Whole numbers ≥ 1, semicolon-delimited
Examples
2;1;4
Note: Decimal quantities are not supported.
itemDiscount
Item-level discount for each SKU. Applies to the total for that SKU across all units. Multiple values separated by a semicolon. Use 0 for items with no discount.
Recommended
Type: DecimalFormat: Numeric, semicolon-delimited
Examples
1.50;0;3.25
Note: A discount of 2.56 on an item with quantity 2 distributes to 1.28 per unit. Can be used alongside the whole order discount field to track both levels of discount simultaneously.
📘

Track additional order details by prefixing any custom column name with cp. — for example, cp.customer_preference or cp.campaign_status. Custom parameters can be added to any vertical and will be passed through alongside your standard fields.

Updated 11 days ago

What’s Next