Manual import is the fallback when no automated method is available: an advertiser who cannot implement a pixel or a postback, a batch that arrived by email, or a correction after something went wrong.
Import is in Reports, Transactions.
What an import does
An imported row behaves exactly like a tracking request, so it can do two things.
- Create: a new conversion is recorded. Commissions run on it and produce transactions.
- Update: an existing conversion is changed, typically to set the result or the value. The transactions under it are updated.
You do not create transactions directly. You import the conversion, and the commission creates the transaction under it. Rows that match no commission are still imported, they just produce no payout.
Before you start
- Make sure the commissions are set up and active for the conversion type you are importing.
- Decide which identifier each row will carry. Without one, nothing can be matched.
- Download the template and test with a few rows before importing a large batch.
What each row can contain
- Origin ID: links the row to the original click or lead.
- External ID: the advertiser’s own order ID. Needed for deduplication and for updating later.
- Conversion date (optional): the date the conversion happened. Without it, the current date is used.
- Result (optional): pending, approved, or rejected, applied to the transaction.
An update needs to point at exactly one conversion. When several conversions exist under the same origin, the Origin ID alone is not enough and you have to send the external ID as well. See Conversion IDs explained.
What happens after the upload
Each row goes through the same steps as a postback or a pixel request.
- The conversion is recorded or found.
- Deduplication on the advertiser’s external ID applies. A row for an order that already exists is stored as a duplicate and produces nothing.
- Commissions run, with their conditions, active periods, and recurrence limits.
- Matching rows produce transactions, which appear in the transaction report.
Nothing about an imported conversion is treated differently later. A postback can still update it, and it counts towards recurrence limits and deduplication like any other.
When rows produce no transaction
Check the conversion log first, then work through the usual causes:
- No commission matches that conversion type.
- The commission is inactive or outside its active period.
- The recurrence limit was already reached.
- The row was deduplicated on the external ID.
- The row was an update that found no conversion to update.
