Save a community Facebook Pixel ID in 3rd Party Services, optionally allow organizers to set a Meta Pixel on an event Tracking tab, and review which Meta events Bevy can send. Chapter Meta Pixel is a separate, default-off switch.
A Meta Pixel (still labeled Facebook Pixel in some Admin fields) lets your marketing tools record visits and ticket-purchase steps on Bevy pages. Bevy loads the pixel script when an ID is saved. Product labels mix Facebook and Meta Pixel — they refer to the same Meta pixel.
Tip: This article orients technical admins. Field-by-field 3rd Party Services steps stay on Third-party services. Per-event Tracking steps stay on Set Facebook Pixel or Salesforce tracking on an event. Facebook login for members is separate social sign-on setup, not Meta Pixel.
What Bevy can send to Meta
When a pixel ID is active on a page, Bevy can send standard Meta browser events such as:
- PageView — a visitor loads a page where the pixel runs.
- AddToCart — a visitor adds a ticket or RSVP to their order.
- InitiateCheckout — a visitor starts checkout before paying.
- Purchase — a visitor completes a ticket purchase or paid RSVP.
On an event Tracking tab you can also store a Meta Pixel Conversions API access token. When that token and the event Meta Pixel ID are both set, Bevy can send matching InitiateCheckout and Purchase events from the server so Meta can deduplicate browser and server events. Leave the token blank if you only use the browser pixel.
Note: If your community uses a cookie consent banner (OneTrust, Osano, or similar), the pixel script waits until the visitor accepts marketing or advertising cookies. See Cookies on Bevy. For Meta’s own event definitions, see Meta Pixel documentation.
Where pixel IDs live
| Scope | Where you set it | Who configures it |
|---|---|---|
| Community | Facebook Pixel ID on Admin Dashboard → Settings → General → 3rd Party Services | HQ admin — see Third-party services |
| Event | Event Tracking tab: Meta Pixel ID (optional Meta Pixel Conversions API access token) | Organizer or admin, only when Allow users to set a Facebook pixel in event creation is on — see Set Facebook Pixel or Salesforce tracking on an event |
| Chapter | Chapter Settings → Tracking: Meta Pixel ID under Meta | Chapter team, only when Allow Meta Pixel IDs on chapters is on (off until an admin turns it on). HQ switch: Third-party services |
Note: A community Facebook Pixel ID applies across the community. An event Meta Pixel is optional and separate when HQ allows it. A chapter Meta Pixel records page views for that chapter page only, separately from the site-wide pixel, and only after Allow Meta Pixel IDs on chapters is on.
Set a community Facebook Pixel ID
- Open the Admin Dashboard.
- Select Settings → General → 3rd Party Services (some communities still say 3rd Party Settings).
- Enter Facebook Pixel ID (digits only).
- Select Save Settings at the bottom of the page.
Tip: The full 3rd Party Services form — including Google tags, LinkedIn, cookie tools, and the Meta checkboxes — is documented in Third-party services. Do not paste a Meta Pixel ID into Google Tag Manager as a substitute for this field unless your Bevy team has approved that approach.
Allow a Meta Pixel on events
Select Allow users to set a Facebook pixel in event creation on the same 3rd Party Services page so organizers can open an event Tracking tab and enter Meta Pixel ID (and optionally a Conversions API access token).
- When the checkbox is on, the event Tracking tab can show the Facebook section with Meta Pixel fields.
- When the checkbox is off, those per-event Meta Pixel fields stay hidden. The community Facebook Pixel ID is unchanged.
Organizer steps for the Tracking tab: Set Facebook Pixel or Salesforce tracking on an event.
Turn off per-event Meta Pixel fields
- Open Admin Dashboard → Settings → General → 3rd Party Services.
- Clear Allow users to set a Facebook pixel in event creation.
- Select Save Settings.
Note: Clearing that checkbox hides per-event Meta Pixel fields. It does not remove the community Facebook Pixel ID.
Chapter Meta Pixel
Allow Meta Pixel IDs on chapters stays off until an HQ admin turns it on in 3rd Party Services. When it is on, a chapter team can save a Meta Pixel ID under Meta on the chapter Tracking page. That pixel sends page views for the chapter page to that ID, separately from the community pixel.
Tip: Turn on the HQ switch in Third-party services. Chapter teams enter the ID on the chapter Tracking page — not on the event Tracking tab and not in the community Facebook Pixel ID field.