Import lets you create, update, or delete records in bulk from a file instead of one row at a time. The Import button appears in the tables that manage those records.
Where import is available
- Affiliates and advertisers
- Commission groups
- Commissions
- Conversions
- Offers
- Tools: structures, integrations, designs, feeds
- Settings: fields, tags, users
How it works
- Click Import in the table.
- Download the template. It is offered as CSV or XLSX and contains exactly the columns that table accepts.
- Fill it in.
- Upload it back.
- Choose the mode.
Import modes
- Create: adds new rows. IDs are generated by PalDock.
- Update: changes existing rows. Every row has to carry an ID.
- Delete: removes records. Every row has to carry an ID.
An update or a delete without an ID has nothing to match against, so the row is refused.
Importing conversions
Conversions are the one import most workspaces use regularly, and they work differently from the rest.
You do not import transactions. Every transaction belongs to a conversion, so you import the conversion and the commission creates the transaction under it. Rows that match no commission are still imported, they simply produce no payout.
An imported row is matched the same way a tracking request is:
- External ID, together with the advertiser ID. The usual pairing.
- Origin ID or Send ID, when you are pointing at a specific click, lead, or delivery.
- Conversion ID, for conversions that cannot be addressed any other way. This is the fallback when a row has no external ID and no usable origin.
Full detail, including what each row can contain and why a row produced no transaction, is on Manual Tracking and Transaction Import.
What to expect
- An imported conversion behaves like any other from that point on. It counts towards deduplication and recurrence limits, and a later postback can still update it.
- The result of the import is recorded, so you can see which rows went through and which were refused, and why.
