Importing Conversions

Once you’ve prepared an input file, you can import your conversions. From the main navigation, go to Reports > Conversion Report. Then click the Conversion Upload button at the top of the table.

For notes on importing errors, pixel-based offers, and creating multiple conversions per transaction ID, skip to Additional Notes below.

Deprecation notice: We are deprecating the Conversion ID (corresponding to the id header) and migrating to the TUNE Event ID (corresponding to the tune_event_id header).  Throughout the document, you will see TUNE Event ID (tune_event_id) instead of Conversion ID (id).

Formatting Your Input File

As a best practice, we recommend using separate input files for each task. This facilitates any future troubleshooting or investigation you may want to do. Only highly advanced users should attempt to combine multiple formatting methods below in the same CSV file.

Your input file must be a comma-delimited CSV file containing the conversions you want to import. It must also:

• Contain no more than 10,000 conversions
• Match accepted value restrictions (case-sensitive)
• Include headers for each column/field
• Separate records using newline characters

Creating Conversions by Transaction ID

To create conversions in your platform by transaction ID, your input file should contain only transaction IDs. This creates conversions in each session with a matching transaction ID and pulls in any available session data. A common use case for this is to process clicks that don’t yet have conversions.

New conversions added with this method default to the “approved” conversion approval status. For offers with the Approve Conversions tracking setting enabled, new conversions are instead set to “pending.”

When you use the tool to create new conversions for three existing transaction IDs, your input file should look something like this:

transaction_id
102b3t4hj545lbgl4v9833
102kjluwer0935842083g
1024235t9078tw987697

Important: If you attempt to create a conversion for a previously converted session using this method, that session may be updated instead. Existing conversions that match an uploaded transaction ID and have a conversion approval status of “pending” are set to “approved.”

Exception When Using Payout & Revenue Groups

When creating a conversion for an offer that uses payout and revenue groups, you must include fields for payout and revenue values. As with the above method, conversions must not exist for the referenced sessions. Otherwise, the conversion for that session will be updated instead.

For example, the above input file looks like this when including fields and values for payout and revenue:

transaction_id,payout,revenue
102b3t4hj545lbgl4v9833,3.25,5.5
102kjluwer0935842083g,0.80,1.30
1024235t9078tw987697,1.00,2.00

Updating Existing Conversions

To update conversions, your input file must contain a reference to an existing conversion and additionally contain values for status, payout, revenue, or sale amount. This reference is almost always a transaction ID. However, if you need to update goal conversions or conversions created without a transaction ID, you can use the TUNE Event ID (formerly Conversion ID) instead.

The TUNE Event ID can be found by exporting the conversion report and is used to identify each unique conversion in your platform. It’s often used when updating goals, as different goals can have the same transaction ID but different TUNE Event ID values.

The example below shows how your file could look when updating the conversion approval status, payout, and revenue of three sessions by transaction ID. In the second record, we plan to reject the conversion and intentionally leave the payout and revenue values blank:

transaction_id,status,payout,revenue
102b3t4hj545lbgl4v9833,approved,3.25,5.5
102kjluwer0935842083g,rejected,,
1024235t9078tw987697,approved,1.00,2.00

To update using TUNE Event IDs, the first field instead uses tune_event_id as the header and contains TUNE Event ID values.  We no longer support Conversion ID (with id as a header), according to the Deprecation notice above. TUNE Event ID now replaces Conversion ID.

Important: If you enter reference a transaction ID that doesn’t have an associated conversion, that conversion is created instead. The approval status of the new conversion is based on the Approve Conversions offer tracking setting and ignores the status field of the input file. To ensure no new conversions are created with incorrect statuses, you can upload the same CSV file again.

Required Fields (include one or the other):

Other Fields (must include at least one):

Exception for CPS / RPS Offers

For cost per sale (CPS) and revenue per sale (RPS) offers, the sale amount must be included and the payout and revenue excluded. Because the payout is based on the sale amount for CPS offers and revenue is based on the sale amount for RPS offers, those values are recalculated when the sale amount is reset.

The example below shows how your file could look when updating an offer with CPS and RPS by transaction ID. We include the sale amount field and avoid using the payout and revenue fields. In the second record, we plan to reject the conversion and intentionally leave the sale amount value blank:

transaction_id,status,sale_amount
102b3t4hj545lbgl4v9833,approved,19.00
102kjluwer0935842083g,rejected,
1024235t9078tw987697,approved,2.00

Creating Conversions without Transaction IDs

To upload new conversions without transaction IDs, your input file must contain the partner ID, offer ID, payout, and revenue fields. Payout and revenue values can be left blank, but the headers must be in place. A common use case for creating conversions this way is to add conversions to offers with expired sessions.

The example below shows how your file could look when creating three conversions. In the second record, we plan to reject the conversion and intentionally leave the payout, revenue, and goal ID values blank:

affiliate_id,offer_id,payout,revenue,status,goal_id
100,42,2.00,4.00,approved,2
102,46,,,rejected,
114,42,2.00,4.00,approved,4

Important: If you omit the status field for a given conversion, then that conversion defaults to “approved.” This method of creating conversions ignores the Approve Conversions offer tracking setting.

Required Fields:

Other Fields:

Additional Notes

Issues with the conversion import process may be due to server-side limitations, improperly formatted input files, or specific aspects of your offers. In this section, we briefly cover those cases. For any issues not covered here, contact our support team with your CSV file and any error messages you encounter.

Pixel-Based Offers

The upload process uses server-side information to determine the validity of a transaction ID. If you need to upload a transaction ID from pixel-based offers, pass the transaction ID macro in the offer URL to generate a server-side session. For more information, read our section on cookieless tracking for pixels.

Known Issues with CSVs

If a text field contains line breaks: The import process does not support line breaks within text fields.

Using Date Fields in Spreadsheets

Most spreadsheet software (such as Microsoft Excel and Google Sheets) will format any dates entered in a way that makes them incompatible with our system. When using expiration_date and other date fields, you must set those columns strictly text-only.

• Microsoft Excel: The steps may vary depending on which version of Excel you use. For current versions, select the columns for the date fields and go to the Cells option in the Format menu. In the Number tab, click on the Custom option in the Category list. Then, in the Type box, enter “yyyy-mm-dd hh:mm:ss” (without quotation marks), then click OK. The dates will then appear as expected when exported to CSV.
  For older versions, select the columns for the date fields, right-click or command-click on the selected area, and click on Format Cells. In the pop-up that appears, click on the Number tab and select Text.
• Google Sheets: Select the columns for the date fields, then go to the Format menu, select Number, and click on Plain Text.
• Apple’s Numbers: Numbers preserve the date formatting as you enter them. No special menu command is needed.

In all cases, you may have to re-enter any dates put in before changing the formatting to correct the entries and have your upload succeed. If you continue to have problems, open your .csv file in a plain text editor to make adjustments.

Errors in Uploading

You may be notified of errors during the conversion import process. Once you start the upload, the conversion upload page can be refreshed to see the task progress:

• Queued – The file is uploaded and is waiting to be processed.
• Processing – The file is being processed, and the results for the total processed count and the failure count will update on each page refresh.
• Finished – The file has finished processing, and the final count for lines, processed, and failed lines are displayed. The employee who uploaded the conversion file receives an email notification when the process has finished.

An error before uploading completion could be caused by one of the following reasons:

• The file contains more than the maximum of 10,000 lines.
• Headers contain invalid fields or are not formatted correctly.
• The file type is not valid. Make sure you’re uploading a comma-delimited CSV file.

Lines failing to update could be caused by one of the following issues:

• The click session has expired or isn’t active.
• The transaction ID is invalid or doesn’t match any recorded sessions in your platform. Pixel-based sessions aren’t recorded until the transaction ID is passed in an offer URL.
• Data for a field is invalid or formatted incorrectly. For example, using “Pending” or “123” as a value for the status field instead of “pending.”
• Conversions already exist for the transaction ID. The upload won’t record duplicate transaction IDs unless the Multiple Conversions offer tracking setting is enabled.