Why can't I just do this myself?

You can — if you have 80–120 hours to learn server-side GTM, debug iOS dedup edge cases, and stress-test EMQ across every conversion event. We do it in 7–10 days because we've done it 300+ times.

What if it doesn't work?

Two protections: (1) 95% tracking accuracy guarantee — we keep working free until your Meta Match Quality hits 8+. (2) You own the entire stack — server, container, runbook — on your accounts from day one.

Will Apple / Google break this in the future?

1st-party server-side tracking is what survives Apple, Mozilla, and Chrome cookie deprecation. The CAPI / Events API endpoints we use are how Meta, Google, and TikTok publicly committed to keeping the channel open.

Does PROSPECT_DISQUALIFIED help optimization?

Indirectly. It should never be sent as a conversion, but recording it lets you see disqualification rate by campaign, which is often the fastest way to cut wasted B2B spend.

Is the dataLayer and fbq example in RevenueHero's docs enough?

It shows the shape but not a production setup. It does not filter reschedules, does not set an event ID for deduplication, and sends a custom Meta event most campaigns are not optimizing for.

Can we send pipeline value to LinkedIn and Google?

Yes, from the CRM rather than the browser. The meeting id ties the RevenueHero booking to the opportunity, and the opportunity value goes back as an offline conversion.

What happens when a prospect books on a different device later?

The browser event is lost, which is why the server-side loop keys on the booker's email and meeting id instead of a cookie.

RevenueHeroBooking-funnel builders & lead routing

Conversion tracking for RevenueHero demo routing

RevenueHero sits between your demo form and your reps' calendars: the prospect submits, the router decides, and a scheduler opens in a popup or embedded iframe on your own page. Most B2B teams count the form submit as the conversion, which means LinkedIn and Google are rewarded for prospects the router turned away. The router announces what happened through postMessage events on your page, and almost nobody listens to them properly.

Get my free conversion tracking audit See what we check

Free30 minutesNo obligation

By Ariful IslamHow RevenueHero works ↓

RevenueHero · what breaks

What goes wrong with RevenueHero

01
The form submit treated as the win
Routed and rejected prospects look identical to the bidding algorithm.
02
Events trapped inside the iframe
Without a message listener on the parent page, GTM never hears MEETING_BOOKED.
03
Reschedules counted as fresh demos
MEETING_RESCHEDULED is a separate message, and a loose listener fires on both.
04
Demo booked, never held
The AE no-show rate on cold paid traffic is invisible until it is joined back from the CRM.

RevenueHero · the fix

What changes — RevenueHero

Qualified, booked demos as the browser conversion
Fired only on MEETING_BOOKED, never on the form.
Disqualified prospects removed from optimization
PROSPECT_DISQUALIFIED recorded, and nothing sent as a conversion.
Held demos and opportunities fed back offline
From the CRM record, at a pipeline value you choose.

RevenueHero · architecture

What RevenueHero actually lets you do

What the documented JavaScript events give you, and what still has to be confirmed on your account.

1
postMessage events to your page
MEETING_BOOKED, MEETING_RESCHEDULED, PROSPECT_DISQUALIFIED, PAGE_LOADED, CLOSE_DIALOG, INIT_REDIRECT and others, read from ev.data.type.
2
A meeting object on booked and rescheduled
Includes the meeting id, meeting time, booker email and the routing rule that matched.
3
A dataLayer and fbq example
Documented as a starting point. It fires a custom Meta event, not a standard one, so it needs rewriting before it feeds bidding.
4
Webhooks and UTM capture
Listed for RevenueHero but not on the events page. Check which webhook triggers and UTM fields your plan exposes before relying on them server-side.

RevenueHero · diagnose

Where RevenueHero tracking breaks, in diagnostic order

Start at the parent page and work outward to the CRM; the first check that fails is usually the answer.

01
Confirm a listener exists for MEETING_BOOKED
Open the console, book a test demo, watch for the message. No listener, no conversion.
02
Check what fires on form submit
If a conversion fires before the router decides, every disqualified prospect is being counted.
03
Book, then reschedule, the same test demo
Two conversions for one meeting means the listener is not filtering on type.
04
Match booked meetings to CRM held demos
The gap is the AE no-show rate, and it differs by campaign.
05
Check the Meta event name
The documented example sends a custom event; campaigns optimized for Lead or Schedule never see it.

RevenueHero · prove

The QA evidence — RevenueHero

Run against your live router and a real rep calendar, not RevenueHero's test mode.

Source of truth

RevenueHero's meeting list, joined to held demos and opportunities in your CRM

A real demo booked through the router, with MEETING_BOOKED captured and the meeting id used as event ID.
A disqualified test prospect confirmed to send nothing to any ad platform.
A reschedule confirmed to update the original meeting rather than fire a second conversion.
Booked meetings reconciled per meeting against each platform over a closed window.
Held demos joined from the CRM and the AE no-show rate stated by campaign.
Opportunity values confirmed arriving as offline conversions.
Re-checked 30 days later, and after any change to routing rules.

RevenueHero · free audit

What we check in the free audit

Confirm a listener exists for MEETING_BOOKED
Check what fires on form submit
Book, then reschedule, the same test demo
Match booked meetings to CRM held demos
Check the Meta event name

Checked against

RevenueHero's meeting list, joined to held demos and opportunities in your CRM

Get my free conversion tracking audit

Free30 minutesNo obligation

RevenueHero · when not to buy

When you don't need this on RevenueHero

Some demo funnels are simple enough that this is overkill.

If you book a handful of demos a month from organic and outbound, ad-platform feedback has nothing to learn from yet.
If your router rarely disqualifies anyone, the form submit and the booking are close to the same number.
If your sales cycle closes in the CRM months later and you only judge campaigns on pipeline, an offline import from the CRM may be the whole job.
A developer comfortable with postMessage can wire the listener in an afternoon. The value we add is the CRM loop and the proof.

RevenueHero · what we deliver

The event map for a RevenueHero demo funnel

Demo form submitted
Volume only. Never an optimization target.
Prospect disqualified
Logged for reporting, excluded from every ad platform.
Demo meeting booked
The browser conversion, with the routing rule that matched.
Demo rescheduled
Recorded against the original booking, not counted again.
Demo held
From the CRM after the call, sent server-side.
Opportunity created
The pipeline conversion, at the stage value you agree with sales.

Written guarantee

95%+ tracking accuracy

Measured against RevenueHero's meeting list, joined to held demos and opportunities in your CRM. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

RevenueHero questions, answered

Because RevenueHero's router decides after the submit. Counting the form rewards campaigns for prospects your own rules rejected, and the algorithm then finds you more of them.

RELATED GUIDES

Free · 30 min

Get RevenueHero demo tracking done properly

Book the free call

Free30 minutesNo obligation

Conversion tracking for RevenueHero demo routing

What goes wrong with RevenueHero

The form submit treated as the win

Events trapped inside the iframe

Reschedules counted as fresh demos

Demo booked, never held

What changes — RevenueHero

Qualified, booked demos as the browser conversion

Disqualified prospects removed from optimization

Held demos and opportunities fed back offline

What RevenueHero actually lets you do

postMessage events to your page

A meeting object on booked and rescheduled

A dataLayer and fbq example

Webhooks and UTM capture

Where RevenueHero tracking breaks, in diagnostic order

Confirm a listener exists for MEETING_BOOKED

Check what fires on form submit

Book, then reschedule, the same test demo

Match booked meetings to CRM held demos

Check the Meta event name

The QA evidence — RevenueHero

What we check in the free audit

When you don't need this on RevenueHero

The event map for a RevenueHero demo funnel

Demo form submitted

Prospect disqualified

Demo meeting booked

Demo rescheduled

Demo held

Opportunity created

RevenueHero questions, answered

Why not just count the demo form submission?−

Does PROSPECT_DISQUALIFIED help optimization?+

Is the dataLayer and fbq example in RevenueHero's docs enough?+

Can we send pipeline value to LinkedIn and Google?+

What happens when a prospect books on a different device later?+

More on RevenueHero

Booking tools beside RevenueHero, and what their bookings feed

Get RevenueHero demo tracking done properly