Integrations Overview
Synaptyx sits in the middle of your marketing stack. It ingests conversions from your store or your networks, pushes data back to ad platforms for optimization, imports ad spend for true ROI, and notifies your other systems.
The integration map
| Integration | Direction | Purpose | Page |
|---|---|---|---|
| Revenue Sources | In | Attribute your own Stripe/Polar sales to clicks | Revenue Sources |
| CPA postbacks | In | Receive conversions from affiliate networks | Postbacks |
| Conversion APIs | Out | Send conversions to Meta / TikTok / Google for ad optimization | Conversion APIs |
| Ad Accounts | In | Import ad spend so ROI/ROAS is accurate | Conversion APIs & Ad Accounts |
| Audiences | Out | Build segments and export to ad platforms | Conversion APIs & Ad Accounts |
| Traffic-source postbacks | Out | Tell your traffic source a conversion happened | Postbacks |
| Webhooks | Out | POST events to your own systems | Alerts, Reports & Webhooks |
| Telegram | Out | Notifications and reports | Notifications |
Two kinds of conversion ingestion
It’s worth restating the key distinction:
- CPA postbacks — for affiliate offers. The network calls your conversion URL
server-to-server. You earn a payout. Carries an
offerId. - Revenue webhooks — for your own product sales. Stripe/Polar fire a webhook;
Synaptyx reads the click ID and records the real order value. Carries a
revenueSourceId.
Both land in the same Conversion table and appear together in analytics and the API.