Skip to main content
Test connection is the one-button health check for a store in Referly Atlas. It looks at whether your site has loaded the tracker recently, whether events and orders have arrived, and whether every pixel you added answers a test event. Run it after setup, after changing a pixel’s credentials, and whenever a report looks emptier than it should. This page shows where the button lives, what each of its four checks means, and what to do when one fails.

​
Where to find it

In the left sidebar, open Store settings and pick the store (the stores are listed on the left of the settings page). Scroll to Tracking and connection. The section opens with status tiles that describe the connection as it stands, followed by the Test connection button. Connection status tiles for a Shopify store: App embed seen, Web pixel registered, last pixel event, last order webhook and destinations, with the Test connection button The tiles are: Connection status tiles of a store that has not reported yet: Tracking script not seen yet, Last pixel event none yet, Last order webhook waiting for the first order, 1 destination connected The store wizard runs part of the same test: the Verify button on its tracking step checks the script and adds an events line under the address field. The settings page is where you get all four checks and the per-pixel answers.

​
The four checks

Select Test connection. Atlas runs these four checks and lists them with a pass, a wait or a fail: The destination check sends a real test event to each pixel, the same as Send test event on a pixel row. Each platform has 10 seconds to answer; a pixel that is switched off is not tested.

​
Reading the results

Test connection results showing the Destinations check with each pixel's answer, one of them failing with a Klaviyo key mismatch
  • All four pass: the store is healthy. If reports still look thin, the gap is usually consent, filters or dedupe rather than the connection. Live activity shows which.
  • Order webhook is waiting on a store with no orders yet: normal. The store sits in Awaiting data until the first order and switches to Running on its own.
  • Destinations lists a failure: the pixel’s answer names the problem, for example a key that does not match the pixel id. Open Pixels and destinations, select Edit on that pixel, fix the credential and run the test again. Each platform’s guide under Pixels says where to find the right values.
  • Tracking script fails but events pass (or the other way round): one of the two sources has gone quiet. A script that is no longer seen after a site redesign, or a Shopify embed switched off, are the usual causes.
The test events also appear in Live activity with the Test status (Test passed or Test failed), so you can open the platform’s response there.

​
How long the first events take

Right after setup, Atlas is honest about the timing: first events usually show within 15 to 30 minutes, and full coverage within 24 to 48 hours. In practice:
  • Page loads count as soon as someone (including you) opens your site with the tracker on it. Open your store in a normal browser window, browse a product, and run the test again.
  • Events (product views, adds to cart, checkouts) follow the first visits. Browser events are forwarded only to pixels that want them, and consent rules may skip them; the incoming row still counts for the check.
  • Orders arrive with the first paid order (or created order, for an external checkout). A purchase sent from the browser waits 60 seconds for the matching order from your platform before it is sent on.
  • Pixels answer within seconds. What you see on the platform’s side (Events Manager, Events API diagnostics) can take longer to update.
A store that has finished its wizard but has no active plan waits instead: nothing is sent until you choose a plan. See Store statuses.

​
The setup checklist

While a store is not fully live, the top bar shows a Complete your setup pill. Open it for the Let’s set up Atlas checklist, five steps that tick themselves as you go: The setup checklist with its five steps Clicking a step takes you where it is done: Billing, the store wizard, Pixels and destinations, Ad accounts or Live activity. The checklist follows the store the page shows; on All stores it follows the business’s most set-up store, so the list always describes one store going live. Choose Hide checklist to put it away for good.

​
If a check fails

Nothing from your site has reached Atlas in 7 days. Open your site in a browser and reload a page, then test again. If the check still fails, the tag is missing or carries another store’s ID: rerun Verify in the wizard’s tracking step (see Add the tracking script). On WooCommerce, clear your caching plugin; on a site that runs the tracker through Google Tag Manager, confirm the container is published.
The Referly Affiliate Tracker embed is off in your live theme, or your storefront is password protected. Open the theme editor, switch the embed on under App embeds, save, then open your storefront and test again. See Connect a Shopify store.
The tracker loads but has not reported an event. Browse a product page and add something to the cart, then test again. On Shopify, check that Turn on Atlas pixel was run in the wizard; the Web pixel tile should read registered. A store still in Draft starts tracking only after the setup is finished.
On Shopify with a third-party checkout, set Type of checkout to External checkout (3rd party) so orders are recorded when they are created. On WooCommerce, confirm the token was saved with Verify and Save and that the plugin is 2.1.0 or later. On a custom site, orders come from your data connection or your own purchase events. Orders placed while Test mode is on are recorded as tests and do not satisfy this check.
Read the error on the pixel’s line: it comes from the platform. A wrong access token, a pixel id that does not match the key, or a conversion label that does not exist are the usual answers. Edit the pixel under Pixels and destinations and test again. If the line says the test timed out, the platform did not answer within 10 seconds; try once more before changing anything.
The connection is fine, so look at what happens after an event arrives. In Live activity, rows marked Skipped, Filtered or Deduped explain themselves; Test rows never reach reporting; and a Paused store records but does not send. The Troubleshooting page walks through each case.

Live activity

Watch events and test deliveries arrive in real time.

Store settings

Tracking and connection, test mode and the API token.

Pixels and destinations

Add, edit and test the pixels that failed.

Troubleshooting

No events, failing tests, pixels in error and more.
Last modified on October 23, 2026