Home

Support

How do you upload external conversions?

Home

Support

How do you upload external conversions?

Campaign

How do you upload external conversions?

Import conversion data retrospectively via CSV or XLSX file and assign it to your campaigns. Find out what data is required and what you should look out for when uploading.

Overview

With the external conversion upload, you can import conversions into AdUp retroactively – completely without a conversion pixel.

This function is particularly suitable if your conversion data is already available in a CRM, shop system, or another data source, and you want to transfer it to AdUp later.

The uploaded conversions flow into the campaign reporting and can be used to optimise your campaigns.

Note: If conversion data is to be transferred automatically and in real time, we recommend Server-to-Server (S2S) Conversion Tracking.

When is the external conversion upload suitable?

The external upload is particularly suitable when:

  • the conversion pixel is not yet integrated

  • conversion data is already available in an external system

  • conversions are to be collected and imported later

  • historical conversion data is to be transferred

Requirements

For the external conversion upload, you need:

  • at least one active conversion code

  • a valid transaction ID (click ID)

  • the time of the conversion

  • an upload file in XLSX or CSV format

Without a transaction ID, the conversion cannot be assigned to an ad click.

Uploading external conversions

Step 1: Open upload

In the advertiser frontend, navigate to:

Tools → Conversion Tracking

There you will find the area for the external conversion upload.

Step 2: Prepare file

The upload is done as an:

  • XLSX file

  • CSV file

Each row corresponds to one conversion.

Step 3: Upload file

Upload your prepared file.

After successful processing, the conversions are assigned to the respective campaigns and ads.

Mandatory fields

The following information is required:

Field

Description

Transaction-ID

Unique ID of the ad click

Conversion-Time

Time of the conversion (Unix timestamp)

These two fields are already sufficient to uniquely assign a conversion.

Optional fields

Additionally, further information can be transferred.

Field

Description

Description

Description of the conversion

Item-Number

Article number

Order-ID

Order number

Price

Unit price

Quantity

Quantity

Total

Total value of the conversion

This details improve the evaluation possibilities and provide additional information for reports.

Requirements

The following rules apply to the upload:

  • At least one active conversion code must be present.

  • Each conversion requires a valid transaction ID.

  • Conversion-Time must be specified as a Unix timestamp.

  • The counting method settings of the used conversion code apply (one-off or multiple).

  • Conversions can be processed retroactively for up to 30 days.

  • Only valid clicks can generate valid conversions.

  • View conversions cannot be imported retroactively.

Updating existing uploads

If you upload data again for a day that has already been imported, the existing data for that day will be completely replaced.

Therefore, every upload should always contain all conversions for the respective day.

Example:

Upload

Result

100 conversions

100 conversions saved

New upload with 120 conversions

The original 100 are completely replaced by 120

Differences to S2S Conversion Tracking

External Upload

S2S Conversion Tracking

Manual upload

Automatic transfer

XLSX or CSV

Direct server communication

Suitable for historical data

Suitable for real-time tracking

Data is imported in batches

Conversions are transferred immediately

Higher manual effort

One-off technical implementation

Best practices

Transfer data as complete as possible

In addition to the mandatory fields, please also submit if possible:

  • Order number

  • Article number

  • Order value

  • Quantity

This ensures that more detailed evaluations are available later.

Use daily uploads

Regular uploads facilitate campaign optimisation and ensure up-to-date conversion data.

Keep the transaction ID unchanged

The transaction ID forms the basis for the assignment between click and conversion.

It must not be changed after the ad click.

Prefer S2S tracking

If automatic data transfer is possible, server-to-server conversion tracking is recommended in the long term.

This ensures conversion data is available for campaign optimisation without delay.

Common error sources

Missing transaction ID

Without a transaction ID, no conversion can be assigned to an ad click.

Invalid timestamp

The Conversion-Time must be passed as a Unix timestamp.

Incomplete daily uploads

Since every new upload replaces existing data, all conversions for a day should always be uploaded together.

Conversion data too old

Conversions can only be processed retroactively for up to 30 days.

Frequently asked questions

Which file formats are supported?

Upload is currently possible as:

  • XLSX

  • CSV

.

Which fields are minimum requirements?

For a successful upload, you only need:

  • Transaction-ID

  • Conversion-Time

Can I correct an upload?

Yes. Upload the conversions for the relevant day again.

The new upload completely replaces the existing data for that day.

Can view conversions be imported?

No. Since view conversions do not have a transaction ID, they cannot be uploaded retroactively.

You might also be interested in this

5 min read

How do you use S2S conversion tracking?

Learn how to transmit conversions server-side via S2S tracking (postback) to AdUp and why this method can be a reliable alternative to the classic conversion pixel.

Advertiser