Server-side tracking for BigCommerce
Give ROASaurus a read-only store-level API account and press Create webhook. Paid BigCommerce orders then go to your ad platforms from the server as they come in.
| BigCommerce at a glance | |
|---|---|
| Orders arrive by | Webhooks (order created, status updated) plus polling every 5 minutes |
| Webhook setup | Automatic, with the Create webhook button |
| Credentials | Store hash and an access token with Orders: read-only |
| Paid orders | Awaiting Fulfillment, Awaiting Shipment, Partially Shipped, Shipped, Completed |
| Thank-you snippet | Script on the Order confirmation page using {{checkout.order.id}} |
How BigCommerce connects
- Storefront › Script Manager › Create a Script: location Footer, pages All pages, type Script, with the ROASaurus script tag.
- Create a second script for the Order confirmation page with the thank-you snippet.
- Settings › API › Store-level API accounts › Create API account with Orders: read-only. Enter the store hash (the part after
/stores/in your API path) and the access token in ROASaurus. - Save, then press Create webhook.
What Create webhook does
ROASaurus registers two BigCommerce webhooks, for order created and order status updated. Every delivery carries a secret header unique to your store, which ROASaurus checks. The webhook only says which order changed, so ROASaurus fetches the order and its products from the API. It also checks for changed orders every 5 minutes, in case a delivery is lost.
Which orders count
Orders in a status that means the payment went through: Awaiting Fulfillment, Awaiting Shipment, Partially Shipped, Shipped and Completed. Pending or declined orders are not sent. ROASaurus reads the total including tax, the billing email, phone, name and address, the customer id, the IP address and each product with its price including tax.
Linking orders to ad clicks
The order confirmation snippet fires the ROASaurus purchase with {{checkout.order.id}}, which links the order to the visitor. Without it, ROASaurus tries an email the visitor gave earlier on your site, such as in a popup, then the order's IP address, but only when exactly one visitor was seen on that IP from 3 hours before to 15 minutes after the order.
Limits
- BigCommerce orders give ROASaurus no user agent, so on shared IPs (offices, mobile networks) the IP fallback often can't decide. The snippet avoids that.
- 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
What API access does ROASaurus need?
A store-level API account with Orders set to read-only. ROASaurus uses it to read orders and to create its two order webhooks.
What if a webhook fails?
ROASaurus also polls BigCommerce every 5 minutes with a 30-minute overlap. Orders it already has are ignored, so nothing is sent twice.
Which BigCommerce statuses count as paid?
Awaiting Fulfillment, Awaiting Shipment, Partially Shipped, Shipped and Completed. Other statuses are left out until the order moves into one of these.
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 →