Skip to main content

How to Connect SendGrid as a Data Source in Alta (Connectors)

Connect SendGrid through the Connectors library so Alta syncs your email delivery and engagement stats to power deliverability and marketing analytics, metrics, and Luna.

Written by Katie Supporté

SendGrid sends your transactional and marketing email and tracks how it performs — delivered, opens, clicks, bounces, and spam reports. Connecting it as a data source through the Connectors library syncs those stats into your Alta workspace, where they become training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure deliverability and engagement — and ask Luna questions in plain English. SendGrid connects with credentials (an API key).

Who this is for: Marketing, growth, and lifecycle teams who want SendGrid email performance measured in Alta.


Before you start

  • Create a SendGrid API key with read access to stats (Settings → API Keys).

  • Connect a source only once per workspace. If SendGrid already shows Connected, edit the existing connection.

Connect SendGrid

  1. Open Connectors from the sidebar.

  2. Find SendGrid via the Data tab or the Search data sources box.

  3. Click the SendGrid card to open the Create connector screen.

  4. Fill in the connection fields shown (such as your API key), then click Create.

  5. Alta runs a connect test. If it fails you'll see The connect test has failed with SendGrid's error — fix the field and retry.

  6. The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

  1. Open the connection. SendGrid brings in global/category stats, contacts, lists, and campaigns (Marketing Campaigns).

  2. Use the Synced toggle in the SendGrid tables section to control what's pulled in.

  3. Turn off Show only synced tables to see everything available.

Key tables and fields synced

  • stats (global/category) — date, delivered, opens, unique_opens, clicks, bounces, spam_reports, unsubscribes

  • contactsid, email, created_at, custom fields

  • listsid, name, contact_count

  • campaigns / singlesendsid, name, status, send_at

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

  • "What's our delivery rate over time?" — trends delivered vs total from stats.

  • "What's our open and click rate this month?" — uses unique_opens and clicks.

  • "Are bounces or spam reports rising?" — trends bounces and spam_reports by date.

  • "How is our contact list growing?" — trends contacts by created_at.

Build your first metric (worked example)

  1. Confirm stats shows Last sync — Succeeded.

  2. In Metrics, create a metric measuring open rate (unique_opens ÷ delivered) with date as the date field.

  3. Set the period to weekly to watch the trend.

  4. Save, add to a dashboard, then ask Luna "what's our email open rate this month?" to confirm.

Example use cases

  • Deliverability dashboard. Delivered, bounce, and spam rates over time to protect sender reputation.

  • Engagement trends. Open and click rates by category or campaign.

  • List health. Contact growth and unsubscribe trends.

Keep it in sync

  • Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.

  • Click Sync now to refresh immediately; it's disabled while a sync runs.

  • Use the overflow menu () to Disable, Enable, or Delete.

Tips and common pitfalls

  • Watch bounces and spam reports. Rising rates hurt deliverability — set these up as monitored metrics.

  • A failed connect test is usually the key or its scopes. Re-issue with read access to stats.

  • Deleting is permanent. Disable instead to pause.


Related

Did this answer your question?