Manual & CSV Conversion Import
Updated August 5, 2026
When to import conversions
The Import Conversions button lets you record offline conversions that happen outside the tracked web flow — phone orders, in-store sales, manual reconciliation, or iGaming GGR adjustments. You can import a single record or a whole batch via CSV.
Where to find it
- Influencer detail page — click Import Conversions in the header to import for that specific influencer, with an optional campaign selector.
- Campaign detail page — same button in the header; you select which influencer in the campaign each conversion belongs to.
Manual Entry tab
- Customer ID — required; any unique identifier (order ID, email, CRM ID).
- Conversion Value — optional; defaults to the influencer's configured value per conversion.
- Date — optional; defaults to today. Use a past date to attribute the conversion to the correct calendar month for payout calculations.
- Reference / Order ID — optional but recommended. Enables deduplication — submitting the same reference twice skips the second entry.
- Campaign — optional (influencer page only); links the conversion to a specific campaign.
CSV Import tab
Click Download Template to get a starter CSV with the correct column headers, then fill in your data and upload the file.
customer_id,conversion_value,date,reference_id
customer_id— required on every row.conversion_value— optional; blank rows use the influencer's default.date— optional; any parseable date string (e.g. 2026-03-15).reference_id— optional; recommended for deduplication.
A preview of the first 5 rows appears before you confirm. Invalid rows are highlighted in red with an inline error message and are excluded from the import count. The Import N valid rows button only processes clean rows.
Deduplication
- With a reference ID — the hash is deterministic (
import:influencerId:referenceId), so re-uploading the same CSV safely skips already-imported rows and reports them as skipped. - Without a reference ID — each row always creates a new conversion. Re-uploading the same file will create duplicates.
Date attribution & payouts
The date field sets the conversion's createdAt timestamp. Payouts are grouped by calendar month, so a conversion dated March 15 will appear in the March payout run even if imported in April. Use this to backfill historical months accurately.
Monthly conversion limits do not apply to manual imports. The monthly limit exists to prevent automated API abuse; backdated offline conversions entered by an authenticated brand admin are always accepted regardless of your plan's limit.