Alba uses built-in tracking integrations rather than custom JavaScript. You can connect:
- Google Ads
- Google Tag Manager
- Meta Pixel
Go to Settings, then Tracking to set it up for your venue. Enter your Google Ads ID (it starts with AW-), your Google Tag Manager container ID (it starts with GTM-), and your Meta Pixel ID (numbers only). Alba won’t save an ID in the wrong format.
Once it is configured, Alba fires events your campaigns can use for conversion tracking:
- A page view when someone lands on your venue page.
- A begin checkout event when they enter checkout, including value and currency.
- A purchase event when payment is verified, including value, currency, and transaction ID. Free bookings (total 0) also send a purchase event, with value 0.
These events run for bay bookings and for standalone product checkouts, including memberships, vouchers (value cards), gift cards, and eligible event products. Each purchase includes a checkout_type field so you can separate bookings from memberships, vouchers, gift cards, and similar sales in Google Tag Manager or your ad platform.
The same events are pushed to the GTM dataLayer, so you can control which tags fire from your own GTM container. You provide the relevant IDs and Alba loads the vetted SDKs for these integrations. Adding your own custom JS snippets to the booking pages is not supported.
Alba loads the tracking scripts for the IDs you save and sends the events listed above. What happens after that, such as your campaigns, tags and reports in Google Ads, Google Tag Manager and Meta, is set up and managed by you.
Meta Pixel: Meta receives InitiateCheckout when checkout starts and Purchase when the purchase is completed. Alba does not send Meta a transaction ID and does not use the Conversions API.
Cookie consent
Alba shows one cookie banner across the marketing site, admin back office, and your venue booking pages. Visitors choose once for the whole Alba product.
On your venue booking pages, accepting also turns on your configured Google Ads, Google Tag Manager, and Meta Pixel tags. Rejecting keeps them off. Nothing loads before they make a choice.
A cookie choice is applied when a page loads. If a visitor changes it in another tab, tabs that are already open keep the old choice until they are reloaded.
If a visitor completes a purchase before choosing, Alba holds the purchase event. If they then accept, it is sent. If they reject, it is discarded.
Visitors can change their mind anytime from the Cookie settings link in the footer.