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 retroactively import conversions into AdUp – entirely 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 are incorporated into the campaign reporting and can be used to optimise your campaigns.

Note: If conversion data should 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 if:

  • the conversion pixel has not yet been integrated

  • conversion data is already available in an external system

  • conversions need to be collected and imported later

  • historical conversion data needs to be transferred


Prerequisites

For the external conversion upload, you require:

  • 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 attributed to an ad click.


Uploading external conversions

Step 1: Open upload

In the advertiser front end, navigate to:

Tools → Conversion Tracking

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

Step 2: Prepare file

The upload is carried out as an:

  • XLSX file

  • CSV file

Each row corresponds to one conversion.

Step 3: Upload file

Upload your prepared file. Following successful processing, the conversions are attributed to the corresponding 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 attribute a conversion.


Optional fields

Additional information can also be transferred.

Field

Description

Description

Description of the conversion

Item-Number

Item number

Order-ID

Order number

Price

Unit price

Quantity

Quantity

Total

Total value of the conversion

This information improves analysis capabilities and provides additional information for reports.


Requirements

The following rules apply to the upload:

  • At least one active conversion code must exist.

  • Each conversion requires a valid transaction ID.

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

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

  • Conversions can be processed up to a maximum of 30 days retroactively.

  • Only valid clicks can generate valid conversions.

  • View conversions cannot be imported retroactively.


Updating existing uploads

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

Therefore, each 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 compared 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 that is as complete as possible

In addition to the mandatory fields, transfer the following wherever possible:

  • Order number

  • Item number

  • Order value

  • Quantity

This ensures more detailed analyses 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 attribution between the click and the conversion.

It must not be modified 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 makes conversion data available for campaign optimisation without any time delay.


Common sources of error

Missing transaction ID

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

Invalid timestamp

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

Incomplete daily uploads

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

Conversion data too old

Conversions can only be processed up to 30 days retroactively.


Frequently asked questions

Which file formats are supported?

Uploading is currently possible as:

  • XLSX

  • CSV

.

Which fields are required at a minimum?

For a successful upload, you only need:

  • Transaction ID

  • Conversion-Time

Can I correct an upload?

Yes. Re-upload the conversions for the relevant day. The new upload completely replaces the existing data for that day.

Can view conversions be imported?

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