EF Helpdesk

‍Updated CSV Template for Clickless Conversions: You can now download an updated CSV template for adding clickless conversions using coupon codes. ‍
CSV Template for Importing Multiple Conversions: You can now download a CSV template for importing multiple conversions. ‍
Error Scanner for Bulk Add/Edit Uploads: An error scanner has been added to bulk add/edit uploads to help identify and resolve issues.

A Step-By-Step Guide

Find Conversion Imports

Navigate to Reporting -> Conversion Imports and click Conversion to select Bulk Add or Update.

Upload Your Template

Click Download Template to choose the desired template and ensure you upload a proper .csv file. Once you have prepared your .csv file, browse or drag and drop to upload it. Your file will be scanned for formatting errors.

If necessary, fix errors and re-upload your file.

When there are no errors, click Import.

Formatting errors include:

File format : Required value is missing

Unsupported layout = Columns are invalid

Max number of rows

Duplicate conversions (*applicable only with editing the status or the payout/revenue of existing conversions)

Continue reading for more information about formatting each type of import.

Continue reading for more information about formatting each type of import.

Pro Tip!

If you are encountering persistent formatting errors, try switching to Google Sheets. Some versions of Excel and associated language settings may inadvertently change the template formats.

Formatting the Import

There are several types of conversion imports. Below, you will find examples and instructions for each type.

Error Message Explained

"Incomplete Record - Optional header columns that are not being used, are still present."

What This Means

This error occurs when there's a mismatch between the columns defined in the CSV header and the actual data provided in the rows. It's not limited to unused optional headers being present.

Example

Header:

transaction_id,event_id,sale_amount,unix_timestamp,adv1

Actual Data:

TID,0,10TID,0,10

In this example, the header defines 5 columns, but the data only provides 3 columns per row.

How to Fix

Ensure all columns in the header are represented in your data rows.
Remove any unused columns from both the header and data.
Double-check that your data aligns correctly with each header column.

Heads up Remove all optional columns in the header that are not being used.

Update Payout/Revenue/Sale amount values of existing conversions

Note You CANNOT update non-approved conversions. The following formats will be accepted for this type of update. However, please note that when you have multiple conversions/events with the same transaction_id, you should use a list of conversion_ids for the update to avoid errors.

When updating existing conversions, Everflow will only process transaction_id, conversion_id, payout, revenue, and sale_amount columns. Other columns (including date and currency) cannot be updated, and will be ignored.

If you have a list of Conversion IDs, the following columns are required (in the specified order):

conversion_id, payout, revenue, sale_amount

If you have a list of Transaction IDs, the following columns are required (in the specified order):

transaction_id, event_id, payout, revenue, sale_amount

Additional Instructions:

event_id should be "0" if you wish to adjust the Base Conversion

adv_event_id may be used instead of event_id, but must include the Advertiser-level Event ID; never "0"

sale_amount is the amount that is passed back in the conversion or event postback for RPS conversions; this will be "0" if there was no amount required

Heads up If we cannot find a conversion for the supplied combo, we will create a new conversion.

Updating Conversion Status

Note When the status of a conversion is updated from rejected to active (and vice versa), the conversion will change the original payout and revenue associated to the conversion.

The following formats will be accepted for this type of update. However, please note that when you have multiple conversions/events with the same transaction_id, you should use a list of conversion_ids for the update to avoid errors.

If you have a list of Conversion IDs, the following columns are required (in the specified order):

conversion_id, status

If you have a list of Transaction IDs, the following columns are required (in the specified order):

transaction_id, event_id, status

Additional Instructions:

event_id should be "0" if you wish to adjust the Base Conversion

adv_event_id may be used instead of event_id, but must include the Advertiser-level Event ID; never "0"

Adding Conversions using an existing Transaction ID

This may be done directly in the Platform for up to 50 conversions. For a detailed guide - [Click Here].

All conversions added will be set to Approved regardless of offer settings (e.g. Postback Control, manually approve conversions, etc). All Partner postbacks will have the timestamp of the upload time.

The following formats will be accepted for this type of update:

If you wish to use the offer-level payout & revenue values, then the following columns are required (in the specified order):

transaction_id, event_id, sale_amount

If you wish to specify the payout & revenue values, then the following columns are required (in the specified order):

transaction_id, event_id, payout, revenue, sale_amount

Heads up If the transaction_id + event_id combination you are using already has an existing Conversion - you cannot include the column Payout or Revenue.

If you do this - you'll only update the Revenue, Payout, and Sale Amount of an existing Conversion instead of adding a new conversion.

If you wish to apply the timestamp of the click to the added conversion, then the following columns are required (in the specified order):

transaction_id, event_id, payout (optional), revenue (optional), sale_amount, use_click_time (value MUST = "1")

The Partner Postback will still have the timestamp of the upload time regardless of utilizing the use_click_time method.

‍

If you wish to customize the timestamp of the conversion, then the following columns are required (in the specified order):

transaction_id, event_id, payout (optional), revenue (optional), sale_amount, unix_timestamp

Additional Instructions:

The following columns can be added to the sheet: advertiser_ip, advertiser_referer_url, unix_timestamp, currency_id, notes, adv1, adv2, adv3, adv4, adv5, coupon_code, order_id, email, offer_url_id.
- Currency_id does not override the Offer Payout & Revenue Settings; typically only used for passing Sale amounts‍
event_id should be "0" if you wish to adjust the Base Conversion‍
adv_event_id may be used instead of event_id, but must include the Advertiser-level Event ID; never "0"‍
sale_amount is the amount that is passed back in the conversion or event postback for RPS conversions; this will be "0" if there was no amount required

Adding Clickless Conversions without a Transaction ID

Note This may be done directly in the Portal for up to 50 conversions. For a detailed guide - [Click Here]. All conversions added will be set to Approved regardless of offer settings (e.g. Postback Control, manually approve conversions, etc). The following method will create a unique transaction ID and conversion for each row in the file, and will attribute the Partner/Affiliate postback to the time of the upload.

The following format will be accepted for this type of update:

offer_id, affiliate_id, event_id, payout, revenue, sale_amount

Additional Instructions:

Payout, revenue and sale_amount are optional columns; if omitted, the conversion will use the offer-level value
The following columns can be added to the sheet: advertiser_ip, advertiser_referer_url, unix_timestamp, currency_id, notes, adv1, adv2, adv3, adv4, adv5, order_id, coupon_code, email, offer_url_id, sub1, sub2, sub3, sub4, sub5‍
- Currency_id does not override the Offer Payout & Revenue Settings; typically only used for passing Sale amounts
- Affiliate_id/partner_id will be overridden when email is used without a transaction_id
event_id should be "0" if you wish to adjust the Base Conversion‍
adv_event_id may be used instead of event_id, but must include the Advertiser-level Event ID; never "0"‍
sale_amount is the amount that is passed back in the conversion or event postback for RPS conversions; this will be "0" if there was no amount required

Adding Clickless Conversions Using Coupon Codes

All conversions added will be set to Approved regardless of offer settings (e.g. Postback Control, manually approve conversions, etc). The following method will create a unique transaction ID and conversion for each row in the file, and will attribute the Partner/Affiliate postback to the time of the upload.

The following format will be accepted for this type of update:

coupon_code, offer_id, event_id

Additional Instructions:

payout, revenue, sale_amount are optional columns; if omitted, the conversion will use the offer-level value
The following columns can be added to the sheet: advertiser_ip, advertiser_referer_url, unix_timestamp, currency_id, notes, adv1, adv2, adv3, adv4, adv5, order_id, email, offer_url_id, sub1, sub2, sub3, sub4, sub5‍
- Currency_id does not override the Offer Payout & Revenue Settings; typically only used for passing Sale amounts‍
event_id should be "0" if you wish to adjust the Base Conversion‍
adv_event_id may be used instead of event_id, but must include the Advertiser-level Event ID; never "0"‍
sale_amount is the amount that is passed back in the conversion or event postback for RPS conversions; this will be "0" if there was no amount required