TradingFellows
Sign in
Pages · landing pages, measured

See what each ad set’s traffic does after the click.

We build your landing page, host it on the edge and watch it every five minutes. The Hub shows every ad set’s visits, taps and joins, the share of its traffic that looks automated, how fast the page loads on real phones, and the pixel events an ad blocker would have cost you.

Start a pageWatch the demo
goldsig.comLive demo · simulated data
1,069real visits
24%tapped the CTA
19%suspicious
110events recovered
Gold UK · broad451 visits · 33% tapped · 3% suspicious
Gold UK · lookalike 3%270 visits · 26% tapped · 5% suspicious
Crypto DE · interests171 visits · 6% tapped · 49% suspicious
Gold UK · Advantage+ placements177 visits · 14% tapped · 27% suspicious
real visits who tappedreal visitssuspicious

What Ads Manager doesn’t show you

Ads Manager counts the click. What happens next is on your page, and most of it never reaches Meta: the visitor who gave up before the page loaded, the data-centre traffic an audience network placement sent, the phone with an ad blocker where your pixel never fired.

Each of those is a paid click that looks like a visit and behaves like nothing. Averaged across a campaign they disappear. Split by ad set they point straight at the one to fix.

One view per page: every ad set, what its visitors did, and how much of it was real.

How it works

  1. Send the briefBrand, offer, where the click should end up and your pixel. We build the page, host it on the edge and point your domain at it.
  2. Tag your ads onceThe Hub gives you one line of URL parameters. Paste it into each ad’s tracking field and Meta fills in the campaign, ad set and ad names by itself.
  3. Read it by ad setVisits, CTA taps, leads or Telegram joins, suspicious share and countries, per ad set, for the last 24 hours, 7 days or 30 days.
  4. Get told when something slipsThe page stops answering, the pixel goes quiet, or one ad set starts sending suspicious traffic: you hear it on Telegram or push first.
In the Hub

What you actually
get to look at.

Real screens from Pages in the Hub, on sample data.

The page at a glance, in the Hub
The page at a glanceReal visits, the share who tapped the CTA, joins or leads, and how much of the traffic was suspicious.
Every ad set, side by side, in the Hub
Every ad set, side by sideVisits, taps, joins and day-7 stay per ad set, with countries and a suspicious flag you can open up.
Speed and uptime, in the Hub
Speed and uptimeLoad times from real phones, visitors who left before it loaded, and 30 days of uptime with every outage.
Pixel health, in the Hub
Pixel healthWhere the pixel loaded, where it was blocked, and each event counted in the browser and from our server.

Suspicious, and why we say it that way

No tool can prove a visit is fake, so the Hub doesn’t pretend to. It flags a visit as suspicious when it shows one of three plain signals, and shows you which one.

Data-centre networkThe visit came from a hosting provider’s network, not a home or mobile connection
Automated browserA headless or scripted browser, or one that says it is being driven by software
Same device againThe same device on the same network, a fourth time or more in one day

Two kinds of traffic are deliberately left alone. iPhone users on iCloud Private Relay arrive through large network providers and are real people, so they’re never counted as data-centre traffic. Meta’s own review and preview visits are counted apart and left out of every number, so they don’t dilute your rates.

Gold UK · broad3% suspicious
Gold UK · Advantage+ placements27% suspicious
Crypto DE · interests49% suspicious
Sample data. Same page, same week: one ad set is clean, one needs its placements trimmed, one is buying data-centre traffic.

Blocked pixels, recovered

On a share of phones the Meta pixel never loads: ad blockers, strict browsers, privacy settings. Those visits still cost you, and Meta never hears about them. The Hub measures that share on every page and, with your Conversions API token saved, sends what was lost from our server.

Pixel blockedPageView and Lead go to Meta from our server instead
Pixel loadedYour page’s events get a matching event ID, and a server copy goes too
DuplicatesBrowser and server share the ID, so Meta counts each event once
Matched withThe click ID from the ad, the browser ID, IP and user agent
Your switchServer copy is one toggle in the Hub, on or off per page

What you see

The funnel per ad setVisits, CTA taps, leads or Telegram joins and, with Channels, how many joiners are still in on day 7.
Suspicious traffic per ad setThe share, the reason, and where it came from by country. Plus an alert when one ad set crosses 40%.
Speed from real phonesHow long the page takes to show something and to finish loading, on mobile and desktop, and the share who left before it loaded.
Uptime history30 days of checks every five minutes, with each outage, how long it lasted and what the page answered.
Pixel health by eventEvery event counted in the browser and from our server, and the share of visits where the pixel was blocked.
Instant exitsVisitors gone in under two seconds without a single touch. A high share usually means the ad and the page don’t match.

What we keep, and for how long

No cookies of ours. No IP addresses stored: only a salted fingerprint of network and browser, used to spot the same device coming back. Visit records are kept for 45 days, then deleted. The only thing sent anywhere is what goes to your own pixel.

The limits, plainly

It reads pages we host, because the tracking is built into them. Ads without the URL parameters still count, filed under “No ad set tag”. Suspicious is a signal, not a verdict: a real person on a work VPN can land in it, and a careful bot on a phone network can miss it. Some phones don’t report every timing, so speed is measured on the visits that do. Recovering blocked events needs your Conversions API token.

Questions

Do I have to change anything in my ads?

Paste one line of URL parameters into each ad’s tracking field. The Hub gives it to you with a copy button. Meta fills in the campaign, ad set and ad names itself.

Is suspicious traffic the same as fake traffic?

No. It means a visit showed a clear signal: a data-centre network, an automated browser, or the same device four or more times in a day. The Hub shows which, so you can judge the ad set yourself.

Will the server copy double count my events?

No. Every event sent from both the browser and our server carries the same event ID, and Meta keeps one. When the pixel is blocked, only the server copy exists.

Does it slow the page down?

No. The script is a few kilobytes, loads after the page and sends tiny beacons in the background. If it fails, the page works exactly the same.

Can I see joins to my Telegram channel per ad set?

Yes, with Channels. Link your channel and each ad set shows its joins and how many are still in after 7 days, next to its visits and taps.

How am I told when something breaks?

On Telegram or push, whichever you switched on in the Hub: the page stops answering, the pixel goes quiet for a day, or an ad set sends 40% or more suspicious traffic.

Who builds the page?

We do. You send the brief from the Hub, we build and host it, and it shows up in Pages the moment it is live.

Find the ad set
that sends real people.

Send the brief. We build it, host it and watch it.

Start a pageAsk on Telegram