Time to read: 8 min

The article covers the following topics:

Import conversions

Import tool helps you to work with conversions, and it can be extremely helpful when you work with a massive number of them.

Using import tool, you can easily import the conversions that have never existed on your instance for some reason or to change the ones that already exist without any need to do it manually.

Below you can find the guide that describes 4 different scenarios:

  • Import conversions - import new conversions for clicks that have never been registered.

  • Import registered - import new conversions for clicks that have been registered.

  • Update - change existing conversions status.

  • Mixed mode - import new and update the existing conversions status at a time.

No conversion can be deleted from your instance. That’s why ensuring every step of the guide is clear to you and followed, respectively. Affise strongly recommends you proceed with an import of one conversion firstly to make sure that the file with conversions is updated correctly.

To work with import feature, you need to get Write access for Import.

Step 1. File creation

1. Create the file with all the data about the conversions you need.

Each type of data in the file must be indicated in a separate column:

2. Save the file.

The requirements you should take into account:

  • The file must have .CSV format.

  • The data in the file must have the semicolon ( ; ) or a comma ( , ) separator.

❗ If you use some other separator, you will not be able to import the file. You will need to delete all uploaded data and repeat your import after all.

The whole process of file creation might look like that:

Step 2. Scenario selecting

To start the import, you need to select the correspondent scenario.

1. In the Statistics -> Conversions slice, click Import.

2. Select the needed scenario:

You will see an example of a valid CSV file and required fields, according to the scenario you chose. It might look like that:

❗ Each scenario has its own required fields. You must fill all of them to import your file.

Scenario: Import conversions

You can import the conversions for the clicks that have never been registered in Affise system.

Required fields:

  • Offer - internal offer ID.

  • Affiliate ID - ordinal Affiliate ID can be taken from the list of affiliates in the 'Affiliates' section on your instance.

  • Conversion ID - action ID passed to you by your Advertiser via postback or any other ID you need to register the conversion under.

What to use as a conversion ID? It could be a conversion ID in the advertiser's system, a conversion ID from the tracking platform you used in the past or another value - whatever it seems convenient for you.

❗ When you import conversions without click ID, you will see '0' in 'Time to conversion' column of Conversion slice in Statistics.

Additional fields:

  • Click ID - click ID which conversion was made on.

  • Goal - goal value (not the title!) exists in your instance and is set in the payouts' settings of the offer.

  • IP - IP the conversion belongs to.

❗ If you make an import using click ids, the IP a click is made from, and the one you have in your file should be the same; otherwise, the import won’t take place. If you do not use click id value in your import, you can use any IP you need.

  • Status - conversion status.

❗ All the conversion statuses should be written only with digital values. Conversion statuses can be the following: approved - 1; pending - 2; declined - 3; hold - 5.

  • Comment - comment: UTF-8 file encoding is required.

  • Created at - date when a conversion was created (should be written in YYYY-MM-DD format). If no date is mentioned in the file, conversions will be imported for the day when the import takes place.

  • Count - number of duplicate records.

  • Sum - a sum that is paid for conversion by the Advertiser. Sum needs to be used when a percent type of payment in the offer's settings takes place. Once the sum is imported, conversion's revenue and the payout will be calculated based on the amount of sum which has been used in the file.

❗ The sum should not be used for a fixed type of payment. Once the offer has fixed type of payments, revenue and payout of conversion will be automatically assigned to it based on the payouts' settings (GEO, Device, Goal, etc.)

  • Custom field 1 - Custom field 7 - custom field 1 - custom field 7.

❗ When importing conversions without Click ID and IP, and with certain goal values, the first payout set up in the offer will be taken into account regardless of goals in the import file. In case of the CPS or RPS/CPA type of payments, numbers dependent on the Afprice value will be shown as 0.

  • Promocodes - the promocode of the conversion.

Scenario: Import registered

You can import the conversions for the clicks that have been registered in Affise system.

Required fields:

  • Offer

  • ClickID

  • Conversion ID

The following values could be used as a conversion ID in this case:

  • a conversion id in the advertiser's system

  • a conversion ID from the tracking platform you used in the past

  • a click ID

  • another value

The clicks will be imported under the Affiliate, GEO, IP, Subids, etc. they were registered earlier in the system.

Additional fields:

  • Goal

  • Affiliate ID

  • IP

  • Status

  • Comment

  • Created at

  • Count

  • Sum

  • Custom field 1 - Custom field 7

  • Promocodes

You can find the description of all the fields in the section above.

Scenario: Update

You can change the conversion's status of the conversions.

Required fields:

  • Offer

  • Conversion ID

  • Status

  • Click ID

  • Affiliate ID

❗ If the conversion has click ID and conversion ID, it's mandatory to indicate these values in the process of import.

Additional fields:

  • Promocodes

  • Goal

You can find the description of all the fields in the section above.

Scenario: Mixed mode

You can add new conversions and change the conversion's status of the conversions at a time.

The list of all required fields you can find in the corespondent scenario:

  • Go here to find the list of required fields for importing new conversions for clicks that have never been registered.

  • Go here to find the list of required fields for importing new conversions for clicks that have been registered.

  • Go here to find the list of required fields for updating existing conversions.

For example, you need to change the statuses of 3 existed conversions for clicks that have never been registered (1) and add 2 new conversions (2):

In this case, the required fields are Offer, Conversion ID, Affiliate ID, Status, and Click ID.

Step 3. File importing

After choosing the scenario, you can continue with file importing.

1. Select the Import with headers flag, if you have a header (name) for each type of data in the very first row, in the file (optional).

Once the flag is checked, the import is carried out starting from the second row.

2. Click Choose file to upload the file from your device and pick up the needed file. A matching window appears.

It might look like that:

The From your file column stands for values arranged in columns in the .CSV file.

The In our system column stands for the type of data in Affise, in the offer settings.

You need to match values in the .CSV file and types of data in Affise. The system takes the data from columns one by one.

3. Click Approve column to confirm that values to the left are considered as the selected type of data. If you want the system to ignore the values in the column, click Exclude column.

4. Review the matching. If you want to change the arrangement, click Back to edit mode.

5. If you want to send affiliate postbacks for imported conversions, check the correspondent checkbox:

6. Click Create ... new rows to start importing conversions.

The progress bar for the file uploading is shown. You can interrupt the uploading by clicking the cross icon.

Once the file is uploaded, the system starts importing values. Then you see how many conversions are uploaded.

Conversion's import/updating can take some time if it involves a great amount of data. Just take your time and let the import proceed.

You can always check your user activity logs to make sure that the import was successful. Go here to read more about the User logs.

❗ Only the user with the Admin role has access to the 'User activity log' section.

If you have any problems with importing conversions, read the guide on Import troubleshooting.

Import conversions by affiliates

Affiliates can simply import conversions in Affise from their side. It's can be only done by using API.

❗ All the conversions imported by affiliates are created in the ‘pending’ status by default.

To allow the affiliates to create conversions via API, you should enable the 'Enable import for affiliates' checkbox in the Settings -> Affiliates -> General (read more about this checkbox here).

If the conversion does not comply with the offer’s settings (e.g. payout restrictions set at the offer’s level), the system declines the conversion with the corresponding comment (e.g. ‘payments not found’).

Once the affiliate imports the conversion into the system, the ‘uploaded via affiliate API’ comment is assigned to the conversion.

In the User Activity logs, you will see the imported conversion. It will have the 'Conversion import api' type and the affiliate's id.

FAQ

1) Are imported conversions analyzed by Advanced Anti-fraud?

Such conversions are analyzed if they have the click ID. Thus, we recommend you to always import conversions with the click ID, if you want to fully use this feature.

2) Can I upload conversions for the clicks that have never been registered in Affise?

You can import the conversions for the clicks that have been registered earlier in Affise using the clickid value they belong to. But, on the other hand, you can import conversions without clickid values too. The conversions will be uploaded with clickid values omitted. Therefore conversions for the clicks that have never been registered in Affise can be uploaded.

3) Can I import conversions via API?

Yes, you can import conversions using our API. There are 2 methods described in our API doc which you can use while importing conversions:

  1. Import of a single conversion: POST /3.0/admin/conversion/import

  2. Import multiple conversions: POST /3.0/admin/conversions/import

If you import conversions with certain goals existent in the offer, the relevant payout value is depicted in Statistics.

The example of payouts and goals in the offer:

The imported conversion with the 1 goal value will have 100$ and 10$ in the relevant columns in Statistics.

The imported conversion with the 2 goal value will have 50$ and 5$ in the relevant columns in Statistics.

❗ In case of the CPS or RPS/CPA type of payments, numbers dependent on the Afprice value will be shown as 0.

Read more about how to proceed with both of the methods described above in our API doc https://api.affise.com/docs3.1/#conversions-managing

You may also find the following articles helpful:


If you have more questions on How to import conversion in Affise, feel free to contact the Affise Support Team via support@affise.com or your Dedicated Account Manager.

Did this answer your question?