Server-side tracking for Ecwid stores
ROASaurus reads paid Ecwid orders through a custom app token and sends them to your ad platforms from the server. Ask Ecwid support for webhooks and orders arrive instantly.
| Ecwid at a glance | |
|---|---|
| Orders arrive by | API polling every 5 minutes; webhooks once Ecwid support enables them |
| Credentials | Store ID, the custom app's secret token, and its client secret for webhooks |
| Webhook check | HMAC signature with the client secret |
| Paid orders | Payment status PAID |
| Thank-you snippet | Ecwid.OnOrderPlaced, after the tracking script |
How Ecwid connects
- Add the ROASaurus script to the site that embeds your Ecwid store, or to your Instant Site custom code.
- Add the thank-you snippet after it. It listens for Ecwid's
OnOrderPlacedevent and fires the ROASaurus purchase with the order number, total and email. - At my.ecwid.com/#develop-apps, create a custom app with read access to orders. Enter your store ID (shown in your admin URL and under Account › Summary) and the app's
secret_…token in ROASaurus.
ROASaurus then fetches orders updated since its last run, every 5 minutes, and sends those with payment status PAID.
Instant orders with webhooks
Ecwid sets webhook URLs for custom apps through its API support team. Ask them to set your app's webhook URL to the one in your ROASaurus Connection tab, with the events order.created and order.updated. Paste the app's client secret in ROASaurus: each webhook is checked against its HMAC signature, and the order is then fetched from the API.
What ROASaurus reads from each order
The total, currency, email, billing name, phone and address, customer id and the items with their combination, quantity, price and SKU. Ecwid orders include the shopper's IP address and user agent, so ROASaurus can also match on the same IP and browser, only when exactly one visitor fits.
Limits
- Webhooks need a request to Ecwid support. Until then, orders take up to 5 minutes.
- Ecwid gives one name field, which ROASaurus splits into first and last name.
- The connector is built from the platform's official API documentation. Press Test connection after saving your credentials, then place a test order and check the Event log.
Related
Questions, answered
Why do I have to contact Ecwid for webhooks?
Ecwid configures the webhook URL of a custom app through its API support. Polling every 5 minutes works without them.
What is the client secret for?
It verifies that a webhook really comes from Ecwid. ROASaurus checks each webhook's HMAC signature with it before fetching the order.
Does it work with Ecwid embedded on another site?
Yes. Add the ROASaurus script and the thank-you snippet to the site that embeds your Ecwid store.
Every sale, traced to the ad that earned it
Server-side tracking, profit and lifetime value in one app. 14-day free trial, no credit card.
Start your free trial →