Server-side tracking for PrestaShop
Enable the PrestaShop webservice, give ROASaurus a read key, and paid orders are fetched every 5 minutes and sent to your ad platforms from the server.
| PrestaShop at a glance | |
|---|---|
| Orders arrive by | Webservice polling every 5 minutes |
| Credentials | Webservice key with GET access to orders, customers, addresses, countries and currencies |
| Paid orders | Orders PrestaShop marks as valid |
| Thank-you snippet | order-confirmation.tpl or the displayOrderConfirmation hook |
| Order matching | Thank-you snippet, then an email the visitor gave earlier |
How PrestaShop connects
- Add the ROASaurus script to your theme header (
templates/_partials/head.tpl) or with a custom code module. - Add the thank-you snippet to
order-confirmation.tpl, or a module on thedisplayOrderConfirmationhook, filled with the order id. - Advanced Parameters › Webservice: enable it and add a key with GET access to orders, customers, addresses, countries and currencies. Enter the key in ROASaurus.
How orders are read
PrestaShop has no order webhooks, so ROASaurus asks the webservice for orders updated since its last run, every 5 minutes, with a 30-minute overlap. Only orders PrestaShop marks as valid count as paid. For each order, ROASaurus looks up the customer, invoice address, country and currency, which is why the key needs read access to those resources.
Line items keep the product and its combination, so variants are told apart. ROASaurus reads the total paid including tax, the order reference, the customer email and name, phone, city, zip and country.
Linking orders to ad clicks
The thank-you snippet fires the ROASaurus purchase with the PrestaShop order id and total on the confirmation page, which links the order to the visitor and their ad click. Without it, ROASaurus falls back to an email the visitor gave earlier on your site, such as in a popup.
Limits
- No webhooks: orders reach your ad platforms up to 5 minutes after they become valid. "Fetch orders now" runs a sync on demand.
- PrestaShop orders don't include the shopper's IP address, so the IP fallback isn't available. Add the thank-you snippet.
- 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 does the webservice key need access to customers and addresses?
A PrestaShop order only holds ids for the customer, invoice address, country and currency. ROASaurus reads those records to get the email, name and location it hashes for the ad platforms.
Which orders are sent?
Orders PrestaShop marks as valid, which is how it flags a paid order. Others are left out until they become valid.
How fast do orders arrive?
Within about 5 minutes. PrestaShop has no order webhooks, so ROASaurus polls the webservice. "Fetch orders now" in the Connection tab syncs at once.
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 →