Conversion tracking is how DiscoAds measures the orders it drives, and how the system learns what converts for you. This guide helps you pick the right method and know what to expect.
Choose your method
Pick the one that fits how you're set up:
- Postback — the most common choice. Your system sends Disco a server-side signal when a conversion happens. Reliable and not affected by browser restrictions. See the Postback integration guide.
- Event API / Web SDK — fire conversion events from your site or app. A good fit if you're already managing events client-side. See the Event API / Web SDK docs.
- Shopify app — if you're a Shopify brand, the Disco app handles tracking for you with the least setup.
- Impact / AppsFlyer — supported if you already track conversions through one of these partners.
What you'll need
DiscoAds does not require you to send personal information (PII) to track conversions. You can pass an anonymized identifier — your own internal user ID, or any unique value — instead of an email. Email is optional and can improve matching, but it's never a prerequisite.
Run an end-to-end test
Before you go live, run a test conversion to confirm the signal is firing:
- Grab your account ID — it's shown under your brand name in the bottom-left of your Disco dashboard.
- Complete a test conversion using the method you chose.
- Check that the conversion appears in your reporting. It can take up to ~30 minutes to show up — a delay here doesn't mean the test failed.
- If you change anything about your tracking setup afterward, run the test again.
What happens next
Once your test passes, your Disco team confirms setup and your campaign moves to launch. From there, conversions flow in near real time, which is what lets the system optimize and attribute correctly.