Introduction

If you're tracking online sales, you can submit a batch of conversion data from your site via a .CSV file uploaded via an FTP/SFTP/FTPS connection. This integration method is useful in circumstances where you can't integrate JavaScript (e.g., impact.com's Universal Tracking Tag) or server-side API calls onto your site.

Note: This article covers the FTP Integration for a Performance Program. Learn more about how to Integrate with SFTP for your Advocate Program.

How it works

1. impact.com tracking links will dynamically populate your site's landing page URLs with an im_ref value. Store the im_ref value in a first-party cookie or server-side session. For single-domain sites, no special handling is required. If your checkout is on a different top-level domain, pass the im_ref value via a URL parameter or a server-side session, as cookies cannot be transferred across distinct domains. For subdomains, set the cookie at the top-level domain (e.g., .yourbrand.com).
2. Online sales that occur on your site (conversions) are recorded via the system you use to track your conversions. This data needs to be populated in a .CSV file, along with the recorded im_ref value (among other required parameters) present when a visitor converted.
3. You’ll submit a .CSV file with your conversion data and other required parameters that’s uploaded to impact.com. This file can be submitted in three ways:

   • Upload directly via an FTP/SFTP/FTPS to impact.com's server
   • Email the file as an attachment to a unique address assigned to your account
   • Have impact.com pull the file from your own FTP server

Server and connection rules

To ensure reliable file delivery and avoid system lockouts, configure your file transfer client according to these network requirements:

• SFTP Failback: If you experience connection failures when using SFTP (sftp://batch.impact.com, port 22), this may be due to host key algorithm compatibility. Use standard FTP (ftp://batch.impact.com, port 21) instead.
• Connection Limits (421 Lockout): impact.com's FTP servers enforce connection limits. Exceeding concurrent connections or accumulating failed login attempts will trigger a 421 lockout. If you're automating uploads, use retry logic with back-off delays rather than rapid reconnection.

Warning: Integrating with impact.com requires web development expertise — it's strongly recommended to enlist the help of a skilled web developer to complete the integration.