Tracking your ads
If you are paying for ads, the platform needs to know which clicks turned into students. Without that it can send you traffic, but it cannot find you buyers — and you cannot tell which campaign made money.
What Pedagio sends
Once you add your tracking IDs, your public pages report these events to Google Analytics and Meta automatically. You do not add any code.
| Event | Fires when | Why it matters |
|---|---|---|
| PageView | Anyone opens one of your pages | Traffic, and retargeting audiences |
| InitiateCheckout | A batch checkout opens | Shows where people drop out |
| Purchase | They enrol, with the fee as the value | The one campaigns optimise toward |
| Lead | An enquiry form is submitted | For campaigns aimed at enquiries |
Purchase carries the amount paid
Step 1 — Add your tracking IDs
- 1Open Settings → Analytics.
- 2Paste your GA4 Measurement ID (looks like
G-XXXXXXXXXX), from Google Analytics under Admin → Data Streams. - 3Paste your Meta Pixel ID— a long number, found in Meta Business Suite under Events Manager.
- 4Save, then open your public site and check Events Manager shows activity.
Either can be used alone. Add only the pixel if you advertise on Facebook and Instagram and do not use Google Analytics.
This needs a plan with the page builder
Step 2 — Add the Conversions API token
Browser tracking is unreliable in a way that is easy to underestimate. Ad blockers, iOS tracking prevention and privacy browsers stop pixel events from firing at all — commonly a third or more of them. Those conversions simply never reach Meta, so your campaigns look worse than they are and the algorithm optimises on partial data.
The Conversions API fixes this by reporting the same event from Pedagio's server, where no blocker can intervene.
- 1In Events Manager, open your pixel and go to Settings → Conversions API. Generate an access token.
- 2Paste it into Meta Conversions API tokenin Pedagio's Analytics settings. It is encrypted before it is stored and never shown again.
Conversions are not double-counted
Contact details sent this way are hashed before they leave the server — Meta receives a fingerprint it can match against its own records, never a readable email address or phone number.
Step 3 — Check it before you spend
Enrol in one of your own batches, using a free or cheap one, and watch Events Manager → Test Events while you do it. You should see InitiateCheckout, then Purchase with the correct amount.
Do this before running ads, not after. A campaign optimising toward a conversion event that never fires will spend your budget on the wrong people and there is nothing in the reporting to tell you why.
Once it is working
- Optimise for Purchase, not clicks or traffic. Traffic campaigns find people who click. Conversion campaigns find people who enrol, and those are different audiences.
- Retarget the people who visited but did not buy. PageView builds that audience for you, and retargeting is usually the cheapest conversion you will get.
- Give it time before judging. Meta needs a number of conversions before its optimisation is meaningful. Switching campaigns off after two days tells you very little.
- Check the fee against the numbers you know. Pedagio's Payments page is the source of truth. If reported revenue and actual revenue disagree badly, something is misconfigured.
Manual payments do not report a Purchase
Where this fits
Tracking measures what your advertising does; it does not improve it on its own. The pages the traffic lands on, and what happens to people who do not buy immediately, matter at least as much — see Filling your batches.
