Submit Conversion Data via FTP or Email

Take the PXA course

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.

This document guides you through formatting and submitting your conversion data, and assumes that you have already begun collecting data.

Before you start

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

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.

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.

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.

Step 2: Submit your data file

Upload via FTP/SFTP

• We recommend splitting FTP/SFTP files to keep the maximum number of entries per file under 10000.

• To submit a file to impact.com's FTP/SFTP server, you will need to retrieve account credentials first. Follow the instructions below to learn how to have your existing credentials emailed to you.

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 for which you want to submit server-side action tracking data, select [More] on the right, and select View / Edit.

4. Next to Returns Processing, select [Edit].

5. Select Automate returns processing (advanced) → Upload file to system FTP server.

6. Select Email FTP Username and Password and Save.

   • Once you have received your FTP/SFTP credentials, use an FTP/SFTP client to connect to impact.com with the following info:

   	FTP	SFTP
   Server	batch.impact.com	sftp://batch.impact.com
   Port	21	22
   Username	(Your case-sensitive impact.com FTP Username.)	(Your case-sensitive impact.com SFTP Username.)
   Password	(Your case-sensitive impact.com FTP Password.)	(Your case-sensitive impact.com SFTP Password.)

7. 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/SFTP credentials email, contact the person who created your impact.com account. Alternatively, contact support.

Pull file via FTP/SFTP

Attach file via email

Step 3: Review the 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.

   • 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. 1. Navigate to [User profile] → Settings → Tracking. 2. 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 [Engage] → Contracts → Contracts.
NO_VALID_REFERRERS _ FOUND CONTRACT_NOT_FOUND	There is no active contract with the partner during the EventDate. • Select [Engage] → 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 [Engage] → Contracts → Contracts to check the referral window for a specific partner.