Submit Conversion Data Retroactively

Take the PXA course

If your conversion data isn’t tracked automatically—whether you collect it server-side, rely on cookies, or a customer misses a partner’s promo code—you can submit it to impact.com retroactively. This lets you attribute credit to the right partners, keep your reporting accurate, and optionally modify or reverse actions before they lock.

This article explains how to format and submit your data via email, which is the simplest method for a 1-time retroactive upload.

What other methods can I use?

If you want to...	Use this method...
Submit a manual, one-time file with no coding	​Email batch processing or upload file via FTP
Set up automated conversion reporting	​Conversions API, push file via FTP, or pull file via FTP

Submit conversion data retroactively

• If you need help collecting conversion data with non-pixel tracking, reach out to your CSM or contact support. To learn more about your tracking method and integration, we recommend consulting the original Technical Integration Plan provided to you by our Technical Services team.
• If you have Connections turned on for your account, setting up a conversion data pipeline will look different for you. Learn how to create a Connection.
• The required parameters for web actions and mobile app actions are different. See Mobile-Specific Parameters for more information on submitting mobile app conversions.

Prerequisite: To use this feature, you need a product edition of Essentials or higher. Contact support to upgrade.

1

Prepare your data file

Follow the instructions below to view a template file, add in your conversion data, and save it in a .csv format. The template you need depends on whether you are tracking conversions at the item level (i.e., including the SKU, quantity, etc. of each item in an order) or at the order level (i.e., just tracking orders themselves, not the items within them). You can also submit chained action data.

Warning: We strongly recommend not submitting actions older than 88 days, as impact.com does not currently process FTP-submitted conversions with event dates beyond that window. Conversions up to 398 days old can be processed, but only if attribution is done using MediaId.

1. Select one of the links below to view the .csv file template that matches what level you track actions at.

   • Item-Level Actions/Conversion Data Template
   • Order-Level Actions/Conversion Data Template
   • Chained Actions Conversion Data Template
2. Add your conversion data to the file.

   • See the impact.com Action & Conversion Data Reference doc for examples, and use this file as a reference for accepted parameters. Reach out to your CSM to find out which parameters would be best to include in your conversion data template.
3. Append any optional parameters you want to report as new columns in your file.
4. Save your file in .CSV format with an easily identifiable title and date (e.g., 2020-01-01_ActionData.csv).

Note: For item-level batch files, Order IDs that have multiple associated SKUs must be listed consecutively. Not grouping together line-items with the same Order ID and different SKUs will result in a OID_DUPLICATE error for the SKUs listed farther down the file

2

Submit your data file via email

1. From the top navigation bar, select [User profile] → Settings.
2. In the right column, under Tracking, select Event Types.
3. Hover over the event type where you want to submit conversion data, select [More], then select View / Edit.
4. Next to Returns Processing, select [Edit].
5. Select Email file to system SMTP server, then copy your unique email address.
6. Before sending your file, confirm the following:

   • Your file is saved in .CSV format.
   • You've chosen the correct data level: item level for product details, or order level for order totals.
   • You're using the matching impact.com template for your chosen data level.
7. Using any email client, send an email to the unique address with your conversion data file as an attachment.

   • Only include the unique email address for the event type in the To: field. If you need to send this file to others, include them in the CC: field.
8. Leave the subject field and message body blank, and Send the email.

3

Review your file submission

1. From the top navigation bar, select [User profile] → Settings.
2. In the left column, under the Technical section, select File Submissions.
3. Use the table to review recent file submissions that impact.com has received, including the current processing status.

   1. Below, you can view various errors you may encounter when reviewing file submissions and actions you can take to rectify them.

Submission troubleshooting reference

Issue	Action to take
Records column shows 0	Make sure the file extension is . CSV or .XML.
NO_CHANGE	There is no change made to the action. Please ensure you enter the final amount into the Amount column (e.g., enter 0 if you want to reverse actions).
BAD_DISPOSITION	The reason code you provided is not valid. Please use one of the standard reason codes. Alternatively, you can set up a custom disposition code.
ALREADY_LOCKED	The action locking period has already passed. The action can no longer undergo modifications or reversals.
ActionTrackerld:ActionTrackerld value is invalid	This should correspond to the Event Type ID entered.
ACTION_NOT_FOUND	The OID you provided is incorrect. Please provide a correct OID.
ALREADY_REVERSED	The action has already been reversed.
ALREADY_APPROVED	The action has already been approved.