Page loads
Which visitor opened the ad
One script on the page the ad opens. It runs only while fbclid or utm_account is still on the URL, and it records that visitor’s addresses so a later registration can be tied back to the click.
Paste on the landing page
<script src="https://tracker.sabtrack.com/t.js" data-website="WEBSITE_ID" async></script>
WEBSITE_ID is the id in the dashboard website URL. The tag does not contain the API key.
An empty query string does nothing. So does /?source=pwa, and so does a later page such as /register. The hit is the ad open, once.
The two hosts answer for that visitor
The page cannot see its own public addresses. The browser calls two hosts, and each host records the address of the phone that just called it.
| Host | What reaches it | Stored on the page load |
|---|---|---|
| v4.tracker.sabtrack.com | IPv4 only. An A record, no IPv6. | 49.36.208.137 |
| v6.tracker.sabtrack.com | IPv6 only. An AAAA record, no IPv4. | 2409:40c1:2a::1 |
Both calls use one page-load id, so the two addresses sit on the same visit, with the full ad URL and the user agent. A phone that can only reach one family leaves the other field empty. That one address is still enough to match.
One visit, then the registration
The ad opens on the account domain. The script stores this row. Nothing is sent to Meta yet.
- Page
- https://reddyfashion.in/?utm_source=ig&utm_medium=paid_social&utm_campaign=summer&campaign_id=120000000000000001&adset_id=120000000000000002&ad_id=120000000000000003&utm_account=reddyfashion&fbclid=PAQk9Dexample
- IPv4
- 49.36.208.137
- IPv6
- 2409:40c1:2a::1
- User agent
- Mozilla/5.0 (iPhone; CPU iPhone OS 18_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Instagram 454.1.0.41.71
The person registers later. Your server sends CompleteRegistration as usual. If that call’s URL still has fbclid or utm_account, we use the URL as sent.
If the registration URL is clean, we look for one page load from the last 24 hours with the same user agent and either of those addresses. One match: fbclid, utm_account, and the ad ids are copied from the stored URL onto the registration. Zero matches, or more than one: the registration stays as it arrived.
When the address changes
Switching from IPv4 to IPv6 on the same visit is already covered. The registration can arrive on 2409:40c1:2a::1 and still find the row that also holds 49.36.208.137.
A new network is a new address. fbclid and the ad ids stay on the page-load row, and they still describe that visit. They are not a second way to find the person. The matcher joins on the address and the user agent.
The join survives a new address when the site saved the first URL and sends that saved URL on the registration. The ad parameters are already on the call, so the address is not required.
Before both addresses work
v4.tracker.sabtrack.com needs an A record only. v6.tracker.sabtrack.com needs an AAAA record only. Both names belong on the TLS certificate and in DJANGO_ALLOWED_HOSTS.
Until those names exist, add data-both="off" to the tag. The script then reports only the address family that reached tracker.sabtrack.com.
The landing host has to be a Meta account domain for the website. A host such as reddybooks.win is stored and marked rejected, and a later registration does not use it.