This guide walks you through connecting your Sona Audiences to SendGrid for automated syncs. By completing this setup, your SendGrid contact lists will update in real time based on Sona segmentation, helping you reach high-intent, ICP-fit audiences with relevant emails.
Prerequisites
Prerequisites
A SendGrid account must be connected to Sona
Access to Sona Audiences data
Step-by-Step Instructions
Step-by-Step Instructions
Step 1: Connect SendGrid to Sona
Step 1: Connect SendGrid to Sona
Go to Connectors in the Sona sidebar
Locate or add the SendGrid Connector
Enter your SendGrid API key to authenticate the connection
Ensure the connection status reads Active before proceeding
Step 2: Create a New Destination
Step 2: Create a New Destination
Navigate to the Destinations section
Click + Add Destination
Select SendGrid from the list of available destinations
Step 3: SendGrid-Specific Configuration
Step 3: SendGrid-Specific Configuration
Choose your SendGrid List from the dropdown
Enable real-time processing for this destination (located under SendGrid List): 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
If you need to create a new list, do so directly in SendGrid before continuing
Source Selection: Choose your Sona audience
Destination Name: Enter a clear, descriptive name (e.g., “Newsletter Subscribers - SendGrid”)
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)
Best Practices (optional)
Use descriptive destination names like “High Intent Leads - SendGrid”
Segment destinations by audience type or lifecycle stage (e.g., new leads vs. MQLs)
Ensure your Sona data includes an email field—required by SendGrid for contact creation
Adjust sync frequency based on your campaign cadence (e.g., 24-hour intervals for weekly newsletters)
Avoid over-mapping fields—limit to essential attributes to reduce sync errors
Review sync logs regularly to ensure successful data delivery