Connect your data

The tracking script sees what happens on your pages. It does not see a subscription renew in Stripe, a trial start in Paddle or an order placed in Ecwid. Connect your data, step 3 of the store wizard, closes that gap: pick the tool that records your sign ups, trials, subscriptions or sales, and Referly Atlas turns them into conversion events for your ad platforms, recorded from the server. The step is optional. Skip it if the tracking script already sends everything, which is often the case for a simple shop. It appears only for stores set up with the tracking script: Shopify and WooCommerce stores get their orders from their own platform and do not see it.

​

What a data connection adds

A data connection gives Atlas a second, server-side source of conversions next to the script:

• Events the page never sees. A renewal, a trial that converts, a refund or an order placed by phone all happen in your billing tool, not in the visitor’s browser.
• Events that survive blockers. Server-side records arrive even when the visitor’s browser blocks the script.
• Values and ids you can trust. Amounts and currencies come straight from the payment, and each conversion carries the tool’s own id, so it is never counted twice.

When the script and the connection both report the same conversion (the same person and type within 24 hours), Atlas merges them and the server copy wins the value and the time. Browser rows wait 60 seconds for the server copy before they are sent. See How duplicates are merged. Atlas matches a payment to the ad click behind it by the customer’s email. For an exact match, several tools let you pass the Atlas visitor id along with the checkout; the wizard shows how under Match payments to ad clicks.

​

One connection per store

Each store has one integration. The step shows a card per tool with the events it records; choose one and the step turns into that tool’s instructions. Once a tool is connected or chosen, the step shows it with a Connected or chosen badge, a Manage (or View setup) button, and the rule spelled out: to use another one, disconnect this one first (Manage, then Disconnect), or click Change for a tool that was only chosen. If you open another tool while one is in use, Atlas tells you the store already uses it and how to switch. Use the Search integrations box when the list is long, and All integrations to go back to the cards. Select Continue at the bottom when you are done, or to skip.

​

What each integration sends

Two more tools, Zylvie (leads and purchases) and Skillplate (subscriptions and purchases), appear only for accounts that were granted access to them. Every card for a payment tool starts with a Connect block whose subtitle reads “Authorize Referly to access your … account”. The connection is the same one your affiliate program uses, so if you already connected the tool there, the block shows Connected with the account name and a Reconnect button. If the wizard asks you to open the store first, select Open store and come back to the step from there.

​

Stripe

Select Connect Stripe and approve the connection on Stripe’s site, as described in the Stripe integration. Atlas then records trials, subscriptions and payments as they happen. Test mode and live mode are separate connections, so connect the one you want to track. The optional Match payments to ad clicks block shows how to put the Atlas visitor id in the checkout session metadata: read it in the browser and add it as referly_vid when your server creates the Checkout Session. Atlas matches payments to visits by email; passing referly_vid makes the match exact. If you use Stripe Buy Buttons, Pricing Tables or payment links, the tracking script sets the client reference id for you, so there is nothing to add.

​

Paddle

Select Connect Paddle and follow the Paddle integration. The Match payments to ad clicks block passes referly_vid in the checkout’s custom data. A Paddle connection made before Atlas needs the subscription.activated event added to its webhook so trials and subscriptions arrive.

​

Chargebee

Select Connect Chargebee and follow the Chargebee integration. Chargebee has no visitor id step: payments are matched by email.

​

Creem

Select Connect Creem and follow the Creem integration. The optional block adds referly_vid to the checkout metadata when you create the checkout.

​

Polar

Select Connect Polar and follow the Polar integration. The optional block adds referly_vid to the checkout metadata. Polar’s webhook needs the subscription.created, subscription.active and subscription.updated events enabled for trials and subscriptions to reach Atlas.

​

Ecwid

Select Install the Referly app on Ecwid: the app comes from the Ecwid App Market and there is nothing to paste. Approve it in your Ecwid admin and you come back with the store connected. Orders and refunds then come in from Ecwid automatically. The Ecwid integration covers the app in detail. If you picked the Ecwid tile in step 1 of the wizard, the same block already appeared in the tracking script step.

​

Sharetribe

Select Connect Sharetribe and follow the Sharetribe integration. Atlas records sign ups and purchases from your marketplace.

​

Zylvie and Skillplate

Zylvie connects like the payment tools above and records leads and purchases. Skillplate asks you to add a webhook: in Skillplate, go to Settings, Webhooks, Create Webhook, paste the endpoint shown in the wizard, pick the event Payment Succeeded and save, then repeat for Subscription Started. Both tools are listed only for accounts that have been granted access.

​

Zapier, Make and the REST API

These three do not connect to a platform. They let anything that can make a web request send conversions to Atlas, which makes them the way in for a CRM, a booking tool, a course platform or your own backend. Each has the same two blocks: The body carries the event name (Lead, CompleteRegistration, StartTrial, Subscribe or Purchase), an id, and the person’s email. A purchase needs an id and a value. You can send up to 50 events in one request. Send one from your tool, check that it shows in Live activity, then select Mark as completed on the Send your events block: the tool becomes this store’s integration and the step shows it as chosen. Field by field, with limits, errors and examples in several languages, see the Events API. The affiliate guides for Zapier, Make and API keys show where those tools keep their settings.

​

Disconnect a data source

Open the store’s wizard (Setup wizard from the store’s row on the All stores page) and go to Connect your data.

• For a connected tool (Stripe, Paddle, Chargebee, Creem, Polar, Ecwid, Sharetribe, Zylvie): select Manage, then Disconnect. New payments stop arriving in Atlas at once.
• For Zapier, Make, the REST API or Skillplate: select Change on the card. The API key keeps working, so requests from your Zap, scenario or backend are still recorded; Regenerate the key under Tracking and connection in Store settings to stop them.

Conversions already recorded stay in your reports. If the store reuses a site from your affiliate program, the payment connection is the same one your affiliate program uses, so disconnecting it here disconnects it there too; reconnect it from either place.

​

Related