Skip to main content

Destination Setup: Customer.io

Updated over a week ago

This guide walks you through connecting your Sona Audiences to Customer.io for automated syncs. By completing this setup, your Customer.io audiences will stay updated in real time based on Sona segmentation, enabling behavior-driven campaigns triggered by real-time customer signals.

Prerequisites

  • A Customer.io account must be connected to Sona

  • Access to Sona Audiences data

Step-by-Step Instructions

Step 1: Connect Customer.io to Sona

  1. Go to Connectors in the Sona sidebar

  2. Locate or add the Customer.io Connector

  3. Authenticate and confirm the status reads Active

Step 2: Create a New Destination

  1. Navigate to the Destinations section

  2. Click + Add Destination

  3. Select Customer.io from the list

Step 3: Customer.io-Specific Configuration

  • Record Matching: Choose the identifier used to match records (e.g., email).

    • Source: Select the matching field in your Sona data

    • Target: Typically, this will be “Email” in Customer.io

  • Field Mapping: Define which data points to sync

    • Source: Select additional fields from Sona (e.g., lifecycle stage, industry)

    • Target: Enter the corresponding field names in Customer.io

    • Click + Add to map more fields

  • Enable real-time processing for this destination (located under Field Mapping): Check this box if you want immediate data updates

    • When enabled, real-time processing will override the scheduled sync frequency

    • Ideal for time-sensitive workflows and immediate lead follow-up

  • Sync Frequency: Schedule how often data should sync

    • Use the interval settings to configure updates every n minutes, hours, days, or weeks

    • Set effective start and end times, if needed

    For general destination configuration steps—such as selecting a Sona audience, setting sync frequency, record matching, field mapping, sync settings, and saving—follow the instructions in the Destination Setup guide.

Best Practices (optional)

  • Use descriptive destination names like “Trial Users – Customer.io Retargeting”

  • Match on email for highest consistency across systems

  • Include fields that support segmentation and campaign triggers in Customer.io

  • Schedule syncs hourly for dynamic campaign use cases

  • Create separate destinations for distinct cohorts or lifecycle stages

  • Monitor sync activity regularly to ensure data integrity

Did this answer your question?