Server-side tracking for commercetools
ROASaurus reads paid orders from your commercetools project and sends them to your ad platforms from the server.
| commercetools at a glance | |
|---|---|
| Orders arrive by | Orders API polling every 5 minutes |
| Credentials | API client with the view_orders scope |
| Paid orders | Payment state Paid |
| Total | Gross total including tax |
How commercetools connects
- Add the ROASaurus script to your storefront and the thank-you snippet to your order confirmation page.
- In the Merchant Center, create an API client with the
view_ordersscope. Enter the project key, region, client ID and secret in ROASaurus.
Why polling and not webhooks
commercetools subscriptions deliver to message queues such as SQS or Pub/Sub, not to web addresses. ROASaurus fetches orders changed since its last run, every 5 minutes, and ignores duplicates.
What ROASaurus reads from each order
The order number, gross total and currency, the customer email and id, the billing name, phone and address, and each line item's product, SKU, quantity, price and name.
Limits
- Orders count when their payment state is Paid, so your payment integration must set it.
- 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
Which scope does the API client need?
Only view_orders for your project. ROASaurus cannot change anything.
My orders don't show up. Why?
Check that your payment integration sets the payment state to Paid. Orders in other payment states are not sent.
Every sale, traced to the ad that earned it
Server-side tracking, profit and lifetime value in one app. Free plan, no credit card.
Start free →