Source connection and heartbeat status

Source Connection is the shared connection signal used across the dashboard. It should be consistent on Signals, Checkout Testing, Performance, Recovery, and store detail pages. A store should not look connected forever just because a plugin was installed once.

What makes a store connected

RocketCheckout looks for recent source activity. Depending on the platform, that can include connector heartbeat, storefront SDK activity, order webhooks, checkout events, or performance samples. The strongest state is when the connector is heartbeating and real events are also arriving.

Why a heartbeat matters

A plugin or app can be removed, disabled, blocked by a firewall, or left on an old URL. Heartbeats prevent the dashboard from showing a false green state. If the heartbeat stops and events stop arriving, the source connection should move away from connected.

What to check when connection is pending

• Confirm the app, plugin, module, or SDK script is installed on the live storefront
• Confirm the store URL in RocketCheckout matches the storefront URL
• Visit the storefront and checkout flow to generate real telemetry
• Place a test order if the platform connector supports order forwarding
• Check that Cloudflare or another firewall is not blocking connector POST requests

What data follows connection

Performance samples should appear after the SDK runs on real pages. Checkout Testing visitors appear after checkout sessions are tracked. Signals and recovery depend on the event contract and destination/provider setup.