Overview

Connecting a source, platform, or destination doesn't guarantee it's sending data. The connect flow can succeed while the snippet is missing from your site, or an OAuth-based connector's access has been revoked or expired. This guide walks through confirming a connection is really working: checking its status and last sync time on the Connections table, then watching the actual event stream in Live data feed.

Before you begin

You need:

1. A source, platform, or destination already connected. See Basic Intempt installation or Creating a Source if you haven't connected one yet.
2. Some real activity to generate data: a page load or app open for a source, or a completed sync for a platform.

Checking connection status

1. Go to Integrations in the left navigation. The Connections tab opens by default.
2. Use the Search integrations... box to find the connector by name, or the Filter button to narrow the table by Status or Type.
3. Read the Status column for your connector's row.

📘 Media pending

Screenshot of the Connections table hasn't been captured yet.

The Status column shows one of four values:

📘 Good to know

If a connector stays on Syncing for more than a few minutes, or shows Error, treat it as not yet validated.

Confirming events are arriving

Status alone tells you the connection is configured; it doesn't confirm data is flowing right now. Check the Last Sync column too:

• just now or X minutes ago means recent data has arrived.
• X hours ago or X days ago means no data has arrived recently. Generate some activity and check again.
• A dash in that column means the connector has never synced.

Generate real activity, then recheck the row:

1. For a source, load a page (JavaScript) or open the app once (iOS, Android) on the property where you installed the snippet or SDK, or send a test call from your server (Node.js).
2. Refresh the Connections tab.
3. Confirm Last Sync now reads just now or a small number of minutes.

For event-level confirmation instead of a table timestamp, open Live data feed (under Events in the main nav) and watch for your event in the real-time stream. See Live data feed for filtering and labeling raw events from there.

Fixing a connector that won't validate

If a connector sits in Error or Disabled, or Last Sync never updates after real activity:

• For OAuth-based connectors (HubSpot, Stripe, Shopify, Slack, and Gmail), open the row's action menu and click Reconnect OAuth to re-authorize it.
• For other connectors, there's no reconnect action. Use Delete on the row, then reconnect it following Basic Intempt installation or Creating a Source.

Use cases

• Pre-launch check. Before you rely on a new JavaScript source for reporting, confirm it shows Active with a recent Last Sync after loading the tracked page.

• Verifying a mobile install. After connecting an iOS or Android source, open the app once and confirm the row moves to Active.

• Auditing all connectors at once. Filter the Connections table by Status to spot anything that isn't Active.

• Triaging failures. Filter to Error to see exactly which connectors need attention.

• Confirming a platform sync. After connecting HubSpot, Stripe, or Shopify, watch the row move from Syncing to Active.

• Checking a destination before go-live. Confirm SendGrid, Slack, or another destination shows Active before a journey step depends on it.

• Investigating a "missing events" report. Check the source's Last Sync time to see when data last arrived from it.

• Verifying a reconnect worked. After using Reconnect OAuth on an expired connection, confirm the row returns to Active.

Where to go next

• Integrations Overview for the full connectors table, platforms, destinations, and the Domains tab.

• Basic Intempt installation for installing the JavaScript SDK end to end.

• Creating a Source for connecting JavaScript, Node.js, iOS, or Android as a source.

• Live data feed for watching individual events arrive in real time.

• JavaScript SDK for the full method reference if events still aren't showing up.