How to connect your sales to RastroAff: choosing the right integration
Postback, pixel, API, Shopify, WooCommerce, coupons or a CRM report: which one to use for your business, with the step by step for each.
Updated on 9 Nov 2026
To pay affiliates, RastroAff has to know about each sale and which click it came from. There are several ways to tell it; choose based on what you have.
Choose
| You have… | Use | Coding |
|---|---|---|
| A Shopify store | Order webhooks | None |
| A WooCommerce store | Order webhooks | None |
| A system that calls URLs (casino, CRM, affiliate platform, your own backend) | Postback | A little |
| Only a "thank you" page | Pixel | Paste a snippet |
| An app or backend that speaks JSON | API | Yes |
| Creators sharing discount codes | Coupons | None |
| Only a monthly report (iGaming) | CRM import | None |
You can use more than one: for example, the Shopify store for sales and coupons for creators.
What they all need
- The click ID at the destination. The offer's destination URL carries
{click_id}in a parameter your site stores, for example?click_id={click_id}. - The sale notification with that click ID (or a coupon), by one of the ways above.
- A sale ID (
txn_id), so the same sale isn't counted twice and you can cancel it later.
Postback or pixel?
The postback goes from your server to RastroAff and doesn't depend on the browser: ad blockers don't affect it. The pixel is simpler, but loses sales when blocked, and has to be turned on in the offer: pixel sales come in as pending until you approve them. See postback or pixel.
Test
Whatever the integration, make a test click on an affiliate link, make a purchase (or fire the notification) and check Conversions. If something fails, search for the click ID in Clicks: you see the postbacks received and the reason for each rejection. For a full example with a casino brand, see set up a casino offer.