Overview

This feature will let you generate or update conversions with a CSV upload. 

Below are the advanced options when using this tool. 

You can find it in the Reporting - Imports.


Step #1

Navigate to Reporting - Imports and click the Import button.

Step #2

Once you click the import button it will bring up the screen below. Please follow the steps to make sure you format the import correctly.


Formatting the Import

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

Templates for the Excel/CSV files can be found at the bottom of this article - [Jump to Templates]


Update Payout/Revenue/Sale amount values of existing conversions

**Please 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.

  • 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:

  • The following columns can be included when using the transaction_id + event_id format: advertiser_ip, advertiser_referer_url, unix_timestamp, notes, adv1, adv2, adv3, adv4, adv5, email, offer_url_id, sub1, sub2, sub3, sub4, sub5
  • 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

*IMPORTANT* If we cannot find a conversion for the supplied combo, we will create a new conversion.


Updating Conversion Status

**Please 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"

Updating Conversion Timestamp

Changing the timestamp of a Conversion or Event is a 2-step process. Both steps involve updating the conversion status.

For instructions, see the section above - [Updating Conversion Status]

Step #1

Use a CSV file to update conversion status to Rejected.

Step #2

Use a CSV file to update conversion status to Approved. This file needs to include the updated timestamp. Simply add a column to the CSV labeled unix_timestamp.


Adding Conversions using an existing Transaction ID

Please note that this may be done directly in the Portal for up to 50 conversions. For a detailed guide - [Click Here]

Please Note: 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
  • 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")

    **Please note that the Partner Postback will still have the timestamp of the upload time regardless of utilizing the use_click_time method.
  • transaction_id, event_id, payout (optional), revenue (optional), sale_amount, use_click_time (value MUST = "1")

Additional Instructions:

  • The following columns can be added to the sheet: advertiser_ip, advertiser_referer_url, unix_timestamp, notes, adv1, adv2, adv3, adv4, adv5, coupon_code, order_id, email, offer_url_id, sub1, sub2, sub3, sub4, sub5
  • 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

Please note that this may be done directly in the Portal for up to 50 conversions. For a detailed guide - [Click Here]

Please Note: 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, notes, adv1, adv2, adv3, adv4, adv5, order_id, coupon_code, email, offer_url_id, sub1, sub2, sub3, sub4, sub5
  • 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

CSV Upload Templates

Please note that the templates linked below are in spreadsheet form - be sure to save a single tab in .csv format before uploading.


NEED HELP? OUR CUSTOMER SUCCESS TEAM IS HERE FOR YOU!

We've assembled a superstar team of industry veterans that are available around the clock to make sure that your issues are resolved and questions are answered. You can reach out any time in-platform via Chat or by emailing support@everflow.io.

Did this answer your question?