Enter your admin secret to view click data
Incorrect secret β try again.
familymilesguide.com Β· external link events
Loadingβ¦
| Link / Destination | Vendor | π± | π» | π₯ | Total | Last click |
|---|---|---|---|---|---|---|
| Loading⦠| ||||||
| Time | Device | Hash | Link text | Page | URL |
|---|---|---|---|---|---|
| Loading⦠| |||||
Paste the click total from each network's dashboard for the same period. The difference reveals bot / pre-fetch traffic that their system filtered out but our beacon still recorded.
| Network | Our clicks | Network reported (auto / paste) | Difference | Where to find |
|---|---|---|---|---|
| Amazon Associates amazon.com links | β | β | Associates Central β Reports β Link Performance | |
| TravelPayouts EKTA Β· AirHelp Β· Aviasales Β· Kiwi Β· Klook | β | β³ Fetchingβ¦ | β | Open TP Statistics β |
| Viator / GetYourGuide viator.com Β· getyourguide.com | β | β | Viator Partners Hub / GYG Partner Portal β Clicks report | |
| Other (CJ / Booking / Expedia) Remaining tracked links | β | β | CJ Publisher Dashboard / Booking Partner Hub |
Difference = gap between what our JS beacon recorded and what the network counted. We > Network: our beacon fired but the affiliate redirect didn't complete β caused by ad-blockers, user navigation, or session deduplication. A 10β30% loss is normal; >40% warrants investigation. Network > Us: the network's server counted hits our JS never saw β bots, search-engine crawlers, link-checkers, and browser pre-fetch all hit affiliate redirect URLs without running JavaScript. This is expected for TravelPayouts because their tpm.li links are crawled frequently.
| Page | Views | New | Returning | Last seen |
|---|---|---|---|---|
| Loading⦠| ||||
Data auto-refreshes on page load Β· all times UTC