Ad Tracking

Aura tells Meta (and Hyros) which ad clicks turned into booked calls, attended calls, and paying customers — so your campaigns can optimize for revenue, not just clicks. This guide explains, in plain English, how that works and why it's more reliable than the old browser-pixel approach.

The problem with the old browser pixel

The classic way to track ads is a "pixel" — a snippet of JavaScript that runs in the visitor's browser and pings Meta when something happens. It has gotten unreliable:

• Ad blockers stop the pixel from loading at all.
• iOS and Safari (ITP) delete the cookies the pixel relies on within days.
• Later events (like a payment you collect a week afterward in your CRM) never reach a browser pixel, because the browser is long gone.

When the pixel misses an event, Meta can't credit your ad. Your reported ROAS looks worse than reality, and Meta's algorithm ends up optimizing for the wrong thing.

How Aura does it: server-side tracking

Aura sends conversion events from our servers directly to Meta, not from the visitor's browser. Think of it like a restaurant:

The browser pixel is a customer shouting their order across a noisy room — sometimes the kitchen hears it, sometimes not. Server-side tracking is the waiter walking the order straight to the kitchen. Same order, far fewer dropped messages.

Because it runs on our servers, ad blockers and browser restrictions can't stop it — and we can fire events that happen long after the visitor left, like a payment you record days later.

What Aura remembers about each visitor (and why it matters)

When someone lands on your booking page from an ad and fills out the form, Aura quietly captures a snapshot of who they are and where the click came from:

We store this snapshot the moment they book. Later — when they attend the call, or pay — Aura replays that snapshot with the event. So even a payment you record by hand, days later, still carries the original ad-click fingerprint.

The more of these signals present, the higher your "match quality" score in Meta Events Manager — and the more conversions Meta can attribute to your ads.

The events Aura fires for you

Aura automatically reports six moments in your funnel:

Purchase events also carry an order ID, so Meta can de-duplicate and match against offline records — no double-counting.

You stay in control (per booking link)

On each booking link's Tracking tab you choose which of these events get reported. By default everything routes to your connected Meta pixel (and Hyros account, if connected) — you don't need to configure anything per link, it just works. But you can fine-tune which events fire if you want a cleaner, higher-intent signal (for example, only reporting Purchase from a high-ticket link).

Privacy

Personal data (email, phone, name) is hashed before it ever leaves Aura — Meta only receives an irreversible fingerprint, never the raw value. California visitors are automatically sent with Limited Data Use flags per CCPA.

FAQ

Does this slow down my booking page? No. The tracking happens on our servers after the booking is confirmed — your visitor never waits on it.

What if a visitor didn't come from an ad? Aura still reports the event with whatever it knows (email, phone, geo). Meta simply won't attribute it to a campaign — which is correct.

Do I need to install anything? Just connect your Meta pixel (and Hyros, if you use it) under Integrations. Aura handles the rest.

Can I see if it's working? Yes — in Meta Events Manager your events appear with a Match Quality score. Higher is better, and server-side tracking is what pushes that score up.