Last updated September 6, 2026
If you run Facebook or Instagram ads that send people to your JourneyFuse booking pages, Meta needs a way to tell you which of those clicks turned into a booking. That is what a pixel does. Add yours once and JourneyFuse reports three things into it automatically: who visited, who started a booking, and who finished one, along with the dollar value of the booking.
Without a pixel, Meta can count the clicks you paid for and nothing after that. You cannot see which ad produced a sale, and Meta's own optimization has nothing to aim at.
That is the whole setup. To remove it later, clear the box and save again.
| Event | Fires when | Includes |
|---|---|---|
| PageView | Someone opens your landing page or a booking link | — |
| InitiateCheckout | A traveler picks their package and continues | Booking total, currency, number of travelers |
| Purchase | A traveler completes their booking | Booking total, currency, number of travelers |
Purchase carries the real booking value, in the currency the proposal was priced in. That is the number Meta needs for a return-on-ad-spend column, and it is what lets you optimize a campaign for revenue rather than for clicks.
Purchase fires when the booking is placed, not when the money clears. A traveler who books and then authorizes a card counts once, at the moment they book. Cancellations and refunds are not sent back to Meta, so reconcile against your own reports before making a spend decision on a campaign with a lot of churn.
Your pixel loads on the pages your ads should point at:
book.youragency.combook.youragency.com/go/your-trip-slug and book.youragency.com/group/YOURCODEAdvertise the branded link, not the long token link. Your proposal has two URLs: a short readable one and a long one ending in a 48-character code. Only the short one carries your pixel.
That is deliberate, and it is worth understanding before you paste a link into an ad. The long code in a proposal URL is what grants access to that proposal — anyone holding it can open the booking page. Ad platforms record the full page address of every event they receive, so firing a pixel on that URL would hand your travelers' booking link to Meta. JourneyFuse will not do it. Your branded link has no code in it, so there is nothing to leak.
To find your branded link, open the proposal and use Share — the short link is the one shown first. If your proposal has no slug yet, set one in the proposal settings and the branded link appears.
JourneyFuse runs no analytics or advertising tags of its own on your custom domain. Your landing page and your booking links carry your pixel and nothing else, and visitors to your domain are not shown a JourneyFuse cookie banner.
JourneyFuse supports one pixel per agency. If you need to feed several ad accounts, point the ID here at a pixel you own and share that pixel with the other accounts from Meta's Business Manager — that is Meta's supported path and it avoids loading several trackers on your travelers' phones.
Meta says my pixel is not receiving events. Install the Meta Pixel Helper Chrome extension and open your landing page. It should show your pixel ID and one PageView. If it shows nothing, re-check the ID in Settings → Domain — it must be digits only, with no spaces.
PageView works but Purchase never fires. You are almost certainly testing on the long token URL. Open your branded /go/ link instead and walk the booking through.
Events show up hours later. Meta's Events Manager has its own reporting delay. Use the Test Events tab there for anything you want to confirm immediately.
Set monthly, quarterly and annual sales and commission targets for the agency and per advisor. Track MTD/YTD progress on the dashboard and Scoreboard.
Bring your TravelJoy clients, trips, bookings, payments and commission history into JourneyFuse. Two self-serve exports carry it, and we migrate it free.
Bring your TESS export into JourneyFuse. Drag-drop the .xlsx, preview what comes over per sheet, then confirm — nothing imports until you say so.