Conversions API: connecting server events safely
Server tracking supplements measurement and requires event and secret checks.
Server tracking supplements measurement and requires event and secret checks.
Practical steps
- Identify the data source and permissions.
- Generate the token through your account.
- Save it only in integration settings.
- Test events and inspect diagnostics.
Worked example
Never put a token in a product description or public script; use the private integration field.
Mistake to avoid
A server token is not a pixel ID.
Working checklist
Keep an event table linking names to actions: product view, cart addition or order submission. Record source, value and currency, test once and repeat after changes. Exclude tests from sales reviews and reconcile reports with order records. Respect privacy choices; tracking never replaces actual delivery and cash-collection follow-up.
Common question
Does the API guarantee every conversion?
No: quality, consent and matching still require verification.
Put it into practice
Create your store on Matjri, prepare the information needed for this guide and test the result as a customer on your phone before sharing the link. Edit photos, descriptions and options and manage orders from your store dashboard.
Sources and further reading
Editorial review: 11 October 2026. Calculations are illustrative; tools and fees may vary by account and supplier.