Submit Conversion Data via FTP or Email

Published on: Mon, 20 Feb, 2023 at 2:17 PM | Updated on: Fri, 26 Apr, 2024 at 7:09 AM

If you're collecting conversion data (i.e., Actions) server-side or through a cookie, you will need to submit your data to impact.com so you can visualize your program's performance, attribute credit to partners, and modify or reverse any actions before they lock. The required parameters for Web Actions and Mobile App actions are different. Navigate to Mobile-Specific Parameters for more information on submitting mobile app conversions.

Looking to create a Connection?

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.

You will be guided through formatting and submitting your conversion data, and this article assumes that you have already begun collecting data. If you need help with collecting conversion data with non-pixel tracking, reach out to your CSM (or contact support). impact.com recommends that you refer to the original Technical Integration Plan provided to you by our Technical Services team—this document describes your tracking method and integration.

Warning: We strongly recommend that you do not process actions older than 88 days, as impact.com currently does not process conversions submitted through FTP that have an event date older than 88 days.

Step 1: Prepare your data

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.

Select one of the links below to view the .csv file template that matches what level you track actions at.
Add your conversion data to the file.
- Refer to the impact.com Action/Conversion Data —Template and 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.
Append any optional parameters you want to report as new columns in your file.
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.

Step 2: Submit your data file

We recommend splitting FTP files to keep the maximum entries per file under 10000.
To submit a file to impact.com's FTP server, you will need to retrieve account credentials first. Follow the instructions below to learn how to have your existing credentials emailed to you.

From the left navigation bar, select [Menu] → Settings.
On the right, under Tracking, select Event Types.
Hover over the Event Type for which you want to submit server-side action tracking data, select [More] on the right and select View / Edit.
Next to Returns Processing, select [Edit].
Select Automate returns processing (advanced) → Upload file to system FTP server.
Select Email FTP Username and Password.
Once you have received your FTP credentials, use an FTP client to connect to impact.com with the following info:

Server

batch.impact.com

Port

21

Username

(Your case-sensitive impact.com FTP Username.)

Password

(Your case-sensitive impact.com FTP Password.)
Once connected, upload your file to the main directory of the server. After a successful upload, go to the Step 3: Review the file submission section below.

Note: If you have not received the FTP credentials email, contact the person who created your impact.com account. Alternatively, contact support.

From the left navigation bar, select [Menu] → Settings.
On the right, under Tracking, select Event Types.
Hover over the Event Type for which you want to submit server-side action tracking data, select [More] on the right and select View / Edit.
Next to Returns Processing, select [Edit].
Select Pull file from your own FTP server.
Enter the Server URL, Port, and directory path to the action data file on your FTP server. Enter the Username and Password that impact.com will use to connect to your FTP server.
Select Save and continue.
Upload your action data file to the directory you specified above (point 6). impact.com attempts to connect and download files from your FTP server every 24 hours. Wait at least 24 hours for impact.com to download your file.

From the left navigation bar, select [Menu] → Settings.
On the right, under Tracking, select Event Types.
Hover over the Event Type for which you want to submit server-side action tracking data, select [More] on the right and select View / Edit.
Next to Returns Processing, select [Edit].
Select Email file to system SMTP server, then copy your unique email address.
Using any email client, send an email to the unique address with your action 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: line.)

You can leave the subject field and message body blank.

Step 3: Review the file submission

From the left navigation bar, select [Menu] → Settings.
In the left column, scroll to the Technical section and select File Submissions.

Use the table to review recent file submissions that impact.com has received, including the current processing status.

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

Errors when reviewing file submissions

Some common errors when reviewing file submission may include:

Issue	Action to take
Records column shows 0	Make sure the file extension is .CSV or .XML.
`ActionTrackerId: Invalid Value`	The `ActionTrackerId` does not belong to the `Event Type` submitted. Navigate to [Menu] → Settings → Tracking. Select Event Types and check for the correct `Event Type`.
`NO_REFERRERS_FOUND` or one of the following parameters is required: `ClickId` `CustomerId` `CustomProfileId` `CustomClickId` `OrderPromoCode` `MediaPartnerId` `UniqueUrl` `CallerId` `GoogAId` `AndroidId` `AppleIfa` `AppleIfv` `WinId` `PhoneNumber` `Odin1` `DeviceId` `OpenUdId` `Mac` `MacMd5` is Required	You have not provided any attribution-related parameters. Provide at least one attribution parameter, so that the system can identify which partner to attribute to.
`OID_Duplicate`	The `OID` is already in impact.com system. Please provide a unique event type. Note: If you are attempting to upload unattributed conversions that were already reported to us in the past, use a slightly different OID. E.g. xxxxxx _1.
`CLICK_AFTER_CONVERSION_EVENT`	The clickid submitted occurred after the conversion event. Please make sure the `ClickId` and `EventDate` submitted are correct.
`NO_VALID_REFERRERS_FOUND ACTIONTERMS_NOT_FOUND`	The contract with the partner active during the `EventDate` does not include this specific event type. Make sure to check your contract with the partner under Contracts → Contract.
`NO_VALID_REFERRERS _ FOUND CONTRACT_NOT_FOUND`	There is no active contract with the partner during the `EventDate`. Select Contracts → Contracts, to check contract history.
`NO_VALID_REFERNO_VALID_REFERRERS_FOUND OUTSIDE_ASSOCIATION_WINDOW`	The conversion is outside the click referral window stated in the contract terms. The default setting is 30 days. Select Contracts → Contracts to check the referral window for a specific partner.

Related Articles