Skip to main content
Meta Ads is the advertising platform of Facebook and Instagram. The Meta Pixel is a small script that measures what visitors do on your booking page. With the integration, anny automatically embeds your Meta Pixel on your public anny booking and shop pages and reports bookings as conversions to Meta. With Meta Ads in anny, you can:
  • Report page views and bookings of your anny booking page directly to Meta
  • Pass completed bookings to Meta as a Purchase conversion with the order value
  • Optimize your Meta campaigns for actual bookings and measure your advertising success
The integration is especially useful when you bring visitors to your anny booking page via Facebook or Instagram ads and want to know which ads lead to real bookings.
The Meta Ads integration is part of the marketing integrations and requires a suitable plan. Check your plan or ask the anny team if the integration is not selectable for you.

​
Typical use cases

​
How the Meta Ads connection works

The connection consists of two building blocks that you can use independently of each other. Meta Pixel in the browser. You enter your Pixel ID and activate the integration. After that, anny loads the Meta pixel script on your public anny booking and shop pages and reports events directly from your visitors’ browsers to Meta. For this building block, the Pixel ID is enough. Offline Conversion API. In addition, you can store an Access token and click Authorize. With it, anny additionally sends purchase conversions directly from the anny server to Meta, independently of the browser. This improves attribution. This building block reports only the Purchase and only fires for visitors who came to your booking page via a Meta ad. What anny accesses: anny sends events to your Meta account, which is defined by the Pixel ID and access token. What anny does not access: anny reads no data from your Meta ad account and changes nothing there. Only events are sent. Which data anny passes to Meta on a purchase: For the conversion, anny passes no names and no email addresses to Meta. Cookie consent: The Meta Pixel only loads in the browser when visitors accept Marketing in the cookie banner. Without this consent, anny sends no browser events. If visitors withdraw consent during the session, anny stops tracking immediately.

​
Connect Meta Ads

​
Requirements

Before you connect Meta Ads, make sure you have the following:
  • A Meta business account with a set-up Meta Pixel and access to the Pixel ID (Meta: Events Manager → Data sets → select pixel → Pixel ID)
  • For the Offline Conversion API additionally an Access token (Meta: Events Manager → select tag → Settings → Conversion API → generate access token)
  • An active cookie banner on your anny booking page so that visitors can consent to marketing tracking
  • Admin rights in your anny account

​
Set up the connection

1

Enter the Pixel ID

From the menu bar, open Integrations and go to Meta Ads. In the Meta Pixel panel, enter your Pixel ID.
2

Set up the Offline Conversion API (optional)

If you also want to report purchases server-side, enter your Access token in the Offline Conversion API panel and click Authorize. Without this step, only the Meta Pixel runs in the browser.
3

Activate the integration

Activate the integration via the toggle in the top right. anny then embeds the pixel on your public booking and shop pages.
As soon as the integration is active and visitors accept marketing cookies, anny reports page views and bookings to Meta automatically.
Check the connection in the Meta Events Manager: open your anny booking page, accept the marketing cookies and create a test booking. Shortly afterwards, the events PageView and Purchase should appear in Meta.

​
Settings & options

anny reports these events to Meta: Page view, Add to cart and Checkout started run exclusively via the Meta Pixel in the browser. The purchase is additionally reported via the Offline Conversion API if you have stored an access token.

​
Limitations

The Meta Ads integration does not support:
  • Tracking on external pages: anny embeds the pixel only on your anny booking and shop pages, not on your own website or other pages.
  • Reading Meta data: anny only sends events to Meta. Campaigns, audiences or statistics from your ad account are not shown in anny.
  • Custom event definitions: The fixed events Page view, Add to cart, Checkout started and Purchase are sent. Additional or renamed events are not possible.
  • Tracking without cookie consent: Without accepted marketing cookies, the Meta Pixel does not load in the browser.

​
Disconnect

If you deactivate the integration, anny no longer embeds the Meta Pixel on your booking pages and sends no new conversions to Meta. Events already transmitted to Meta remain in your Meta account. When you delete, anny removes your stored Pixel ID and the access token; no further steps are required.
You can do both under Integrations: deactivate via the toggle in the top right, delete via the three dots → Delete.

​
FAQ

No. For the Meta Pixel in the browser, the Pixel ID is enough. The Access token is only needed if you additionally want to use the Offline Conversion API, which reports purchases server-side to Meta.
On your public anny booking and shop pages, for example resource, service, package and checkout pages. anny does not embed the pixel on your own website.
anny passes the net amount of the booking, the currency and the order number. Names or email addresses are not sent to Meta for the conversion.
You find the Pixel ID in the Meta Events Manager under Data sets in the selected pixel. You generate the Access token in the Events Manager under the settings of your tag in the Conversion API area.

​
Troubleshooting

Usually the integration is not active or visitors did not accept marketing cookies. Check whether the toggle is active, whether the Pixel ID is entered correctly and whether the marketing cookies were accepted on your booking page.
The access token can only be set while the integration is deactivated. Deactivate the integration first via the toggle, then enter the access token and click Authorize. Reactivate the integration afterwards.
The Offline Conversion API reports only the Purchase and only for visitors who came to your booking page via a Meta ad. Check whether the access token is valid and not expired and whether the booking actually originates from an ad click.