Implementation

This page covers how to build and submit an extension data file to CJ. Follow each step in order.

You have read the Overview page and understand the transaction state requirement (NEW and ACCEPTED only) and the 10th-of-the-month deadline.
Your advertiser account is active and you have a data transfer subscription for extension data. Contact your CJ account representative to obtain your Subscription ID (SUBID) if you do not have one.
You have the TID or OID (or both) for each transaction you intend to extend. If you plan to use OID only, confirm that each OID is unique for the transactions you are targeting.
Verify the current state of each transaction in CJ Account Manager before building your file. Only NEW and ACCEPTED transactions can be extended.

Step 1: Confirm Eligible Transaction States

Before building your file, log in to CJ Account Manager and review the current state of the transactions you plan to extend. Navigate to your transaction report and filter by the relevant time period.

Extension is permitted only for transactions in the following states:

NEW: Posted but not yet reviewed.
ACCEPTED: Reviewed and accepted, not yet locked for payment.

Remove any transactions in a LOCKED or CORRECTED state from your list before including them in the file. Including ineligible transactions will not cause the entire file to fail, but those individual records will be rejected and reported in the Results email.

Step 2: Obtain Your Subscription ID

Your extension data subscription is separate from any action data or correction data subscription you may already have. Contact your CJ account representative if you have not yet set one up. CJ will provide a numeric Subscription ID (SUBID) that must appear in the header of every extension file you submit.

Step 3: Build Your Data File Header

Every extension data file begins with a header that identifies your account. The header must appear once per file, before any extension records.

Parameter

Description

Required

cid

Your advertiser account number with CJ.

Required

subid

Your subscription ID for extension data transfers, provided by CJ.

Required

encoding

The character encoding of your file. Required only when using a non-default encoding. The default is CP1252 (Microsoft Codepage 1252). Include this field in the header when using a non-default character set.

Conditional

Step 4: Build Your Extension Records

Each record in the file body identifies one transaction to extend. Records must include placeholders for both the tid and oid fields in that order, even when one of the values is not provided. At least one of the two must contain a value.

Parameter

Description

Required

tid

The unique Transaction ID that CJ assigns to each posted transaction. This value appears in the CJ Account Manager transaction report under the Transaction ID column. If both TID and OID are supplied in the same record, the TID takes precedence for matching. Required if OID is not supplied. Include an empty placeholder if this field is omitted.

Conditional

oid

The advertiser-supplied Order ID as it appears in the CJ Account Manager transaction report under the Order ID column. If only OID is used (without TID), each OID must be unique per transaction to ensure correct matching. Must not contain personally identifiable information. Required if TID is not supplied. Include an empty placeholder if this field is omitted.

Conditional

TID and OID placeholder scenarios

Because both fields must be present in the record in column order, the following examples show how to handle each scenario correctly:

Scenario	Example Record
Both TID and OID supplied (TID takes precedence)	`136841,OTZ1641541E`
TID only (OID placeholder)	`136841,`
OID only (TID placeholder)	`,OTZ1641541E`

Step 5: Format and Structure Your File

Header format for delimited files

For all delimited formats, header field names must be prefixed with &:

&CID=2539845
&SUBID=143

Full CSV file example

&CID=2539845
&SUBID=143
136841,OTZ1641541E
137002,
,OTZ1641598B

The first record supplies both TID and OID. The second supplies TID only with an OID placeholder. The third supplies OID only with a TID placeholder.

Format rules

Each record must appear on a single line. Line breaks within a record are not permitted.
No control characters or extra spaces may appear in field values.
Header and body lines must not end in trailing whitespace, commas, or pipes.
For CSV files exported from Excel, open the resulting file in a text editor and remove any trailing commas Excel adds to the header row before submitting. Files with malformed headers will not generate a Receipt email from CJ.

Step 6: Submit Your File to CJ

Transfer your file to CJ using the delivery method specified in your extension data subscription. Remember that prior-month transactions must be extended by the 10th of the current month. After the file is received, CJ sends a Receipt email confirming it was accepted for processing. After processing completes, a Results email details the outcome of each record.

See the Testing page for guidance on interpreting these emails and resolving errors.