Your own tracking: GA4, Meta Pixel and Tag Manager

This is not Velobook's own reporting; for bookings, revenue and conversion figures see analytics and CSV exports. This is where your booking pages report into the analytics tools you run yourself. Open Integrations → Analytics integrations.

Where the ids go

The Your analytics card holds three fields. Fill in the ones you use; a blank field means that tag never loads. Velobook checks the shape of each id as you type.

• Google Analytics 4, Measurement ID, in the form G-XXXXXXXXXX. In Google Analytics under Admin, Data streams, your stream.
• Meta (Facebook) Pixel ID, a number of 6 to 32 digits. In Events Manager, your pixel, Settings.
• Google Tag Manager, Container ID, in the form GTM-XXXXXXX. Next to your container name in Tag Manager.

No sign-in and no approval screen. These ids are not secrets; paste them in and press Save.

Which pages the tags load on

• Your public booking pages only: your booking page and booking flow, plus your workshops, hire, tours, fittings and community day pages
• Never the admin, so your own staff never show up as traffic

Nothing loads without consent

• Every visitor to your booking page sees the Cookies & storage banner. Until they choose, no tag script is fetched and no request goes out
• Accept all, or turning Analytics on under Customize, switches your tags on. Essential only leaves them off
• A visitor can come back to the banner and change their mind

What the tags actually see

• GA4 receives page views and funnel events named with a vb_ prefix, carrying the step and the flow as parameters, addressed to your property only.
• Meta Pixel receives a PageView plus a custom BookingFunnel event carrying the step and flow.
• Tag Manager receives a velobook_funnel data layer event with the same details.