> ## Documentation Index
> Fetch the complete documentation index at: https://lyntex.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Good Sync: Automated Return File Sync and FTP Delivery

> Good Sync runs on a schedule to analyze and sync ACI Return Files, then delivers them to your FTP destination via FileZilla automatically.

Good Sync is a scheduled process within the ACI Platform that picks up completed return files and delivers them to your FTP destination. It runs automatically after every campaign event that generates a return file — you do not need to initiate or monitor the process manually. Once a CSV return file is saved to the ACI Return File folder, Good Sync takes over and handles delivery end to end.

## How Good Sync Works

Good Sync follows a three-step process each time it runs:

**1. Analyze**

Good Sync scans the ACI Return File folder for new or updated files. Any file that has not yet been delivered — or that has changed since the last sync — is flagged for processing.

**2. Sync**

Good Sync synchronizes the identified files to prepare them for delivery. This step ensures the files are complete, consistent, and ready to transfer before they are sent to FTP.

**3. Send via FileZilla**

The return file is sent to your configured FTP destination using FileZilla. Once the transfer is complete, the file is available at your FTP for downstream processing.

> [!NOTE]
>
> Good Sync is fully automated — you do not need to manually trigger it. It runs on its configured schedule after each campaign event that produces a return file.

## When Good Sync Runs

Good Sync runs on a scheduled process and is triggered automatically after the following campaign events:

| Campaign Event | Description |
| - | - |
| **Initial campaign email send** | Triggered after the campaign emails are sent to the full list. |
| **Bounce detection** | Triggered when a bounce is recorded for a campaign email address. |
| **Email open event** | Triggered when a recipient opens a campaign email. |
| **Consumer opt-out** | Triggered when a consumer unsubscribes or opts out of the campaign. |

Each of these events causes the ACI Platform to generate a CSV return file, which Good Sync then picks up and delivers on its next scheduled run.

## The ACI Return File

The file Good Sync detects and delivers is labeled the **ACI Return File**. This is the CSV file generated by the platform after each campaign event. Good Sync looks for this file in the ACI Return File folder and transfers it to your FTP destination via FileZilla.

Because Good Sync runs after each individual event, a separate ACI Return File is delivered for each event type — one for the initial send, one per bounce, one per open, and one per opt-out.

> [!TIP]
>
> If a return file is not received at your FTP destination, check that the ACI Return File folder contains the expected file and that Good Sync has run since the campaign event occurred. If the file is present in the folder but has not been delivered, Good Sync may not have run yet or may need to be reviewed for configuration issues.

For details on the structure and contents of the CSV return file that Good Sync delivers, see [Campaign CSV Return Files](https://lyntex.mintlify.site/files-sync/csv-export.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.