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.
  • Integration IDs: All advertiser implementations require unique integration IDs. Request your IDs from CJ’s Technical Support team when you are ready to begin your setup.
  • Tracking Continuity: Maintain your existing tracking until your new integration is fully implemented, tested, and confirmed as active. This ensures uninterrupted attribution and reporting.

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
eventTime
amount
currency
itemSku
itemQuantity
itemUnitPrice
itemDiscount
coupon
companyIdenterpriseIdsubscriptionIdactionTrackerIdorderIdcjEventeventTimeamountcurrencyitemSkuitemQuantityitemUnitPriceitemDiscountcoupon
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.
coupon
The coupon or voucher code used in the transaction.
Recommended
Type: String
Examples
SAVE20
WELCOME10
Note: Leave empty or omit if no coupon was used.

Custom Parameters can be included by prefixing any custom field name with cp. — for example, cp.UTM_TERM, cp.Approved_Date, cp.funded_flag. Please do not use this prefix when using any of the official vertical parameters referenced below.

Vertical-specific parameters (e.g. travel, finance, retail) are not included here. To view the full list of available vertical parameters that can be appended to your data file, see the Vertical Parameters page.

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
itemId
The identifier for the individual item purchased, such as a SKU or product ID.
Required
Type: StringFormat: Alphanumeric, dashes, and underscores only
Examples
SKU-001
PROD_4521
Note: Maximum 100 items per order. SKU values must be 100 characters or fewer. Spaces and special characters are not permitted.
unitPrice
The price of a single unit of the item. Do not multiply by quantity.
Required
Type: DecimalFormat: Numeric only, no currency symbols or commas
Examples
13.49
3.00
Note: Pass the price of one item regardless of quantity. For example, pass 3.00 for two items at 3.00 each — not 6.00. Maximum 100 items per order.
quantity
The number of units purchased for this item. Multiplied by unitPrice to calculate the item total.
Required
Type: IntegerFormat: Whole numbers only
Examples
1
3
Note: Decimal quantities are not supported. For example, quantity=1.0 is read as quantity=10. Maximum 100 items per order.
discount
Discount applied to this specific item in the transaction. Use this for product-level promotions such as a sale price on an individual SKU. For order-wide discounts, use the top-level discount parameter.
Optional
Type: DecimalFormat: Numeric, max 2 decimal places
Examples
5.00
Note: The discount is divided evenly across all units. For example, a 5.00 discount on 2 units at 10.00 each reduces each unit to 7.50, giving a subtotal of 15.00.

Updated 6 days ago

What’s Next

Did this page help you?