Skip to main content
After every campaign event, the ACI Platform automatically creates a CSV return file containing the records for that event. These files are saved to the ACI Return File folder and delivered to your FTP destination via Good Sync. You do not need to manually export or move these files — the process runs automatically as your campaign progresses.

​
When CSV Files Are Generated

A CSV file is created after each of the following campaign events:

Initial Campaign Send

A CSV is generated after the campaign emails are sent, containing the full list of email addresses included in the send.

Bounce Detection

A CSV is generated when a bounce is detected for an email address in the campaign.

Email Open Event

A CSV is generated when a recipient opens a campaign email.

Consumer Opt-Out

A CSV is generated when a consumer unsubscribes or opts out of campaign communications.
Each event type generates its own separate CSV file — there is one file per event, not one cumulative file for the entire campaign.

​
What’s Included in the File

Each CSV file contains the full list of email records for that specific event:
  • Initial send — The file includes all email addresses that were sent the campaign message.
  • Bounce — The file contains the record for the specific email address that bounced.
  • Open — The file contains the record for the specific email address that opened the message.
  • Opt-out — The file contains the record for the specific email address that opted out.
This per-event structure keeps your return files focused and easy to process downstream — each file represents a discrete action taken during the campaign lifecycle.

​
File Location

The CSV return file is saved to the ACI Return File folder on the platform. Once saved, Good Sync picks it up on its configured schedule and delivers it to your FTP destination automatically. You do not need to move or rename the file. As long as it is present in the ACI Return File folder, Good Sync will detect and deliver it.
See Good Sync for details on how files are synced and delivered to your FTP destination.

​
Using the Return File

Once the CSV return file is delivered to your FTP destination, you can use it to:
  • Reconcile campaign activity — Match sent, bounced, opened, and opt-out records against your internal systems.
  • Update external systems — Feed the data into your CRM, collections platform, or other downstream tools.
  • Archive campaign records — Store the files as a historical record of campaign activity for compliance or auditing purposes.
Because a separate file is generated for each event, you can process each file type independently as it arrives at your FTP destination.