Simple friendly server-side tracking for Meta ads

In partnership with Meta

Get started with Hub

Hassle-free setup

with user friendly interface

1. Create gateway server — connect Meta and set data destination: the Meta dataset that receives the tracked events
2. Own your data — add your domain to capture events as first-party signals: the pipeline with the custom domain active and events tracked over 30 days
3. Maximise tracking — activate the new first-party pixel from Meta: events captured by Birch on top, no data loss

How it works

  1. first-party pixel

    Immune to browser restrictions and ad blockers for reliable event tracking

  2. hub

    Events are collected and processed safely within your own gateway server

  3. meta

    Data is sent via CAPI to Meta, improving attribution and ROAS

With Birch Hub conversion is higher

  • More data events

  • More accurate attribution

  • Better functioning ad algorithms

  • More relevant audience

Cricksy Dog after Switching to Birch Hub

  • 30% decreased in CPA
  • 35% increased in conversions
  • 40% increased in total events tracked
A happy puppy — Cricksy Dog makes dog products
Read case

Accurate Tracking Helped Pawz.rs Scale Campaigns Profitably

  • 9+ ROAS on cold campaigns
  • 22% decrease in CPA
  • 25% increase in total tracked events
A surprised cat — Pawz.rs sells pet products
Read case

Pricing

per gateway

  1. 10,000 events/mo Free
  2. 500,000 events/mo $10
  3. 5,000,000 events/mo $49
  4. 20,000,000 events/mo $149
  5. 50,000,000 events/mo $249
  6. 150,000,000 events/mo $499
Get started with Hub

FAQ

What is 1st party data and 3rd party data?

First-party data is information you gather directly from your audience through channels like your website, app, email subscribers, and CRM.

Third-party data, on the other hand, is collected by another entity or business and then shared with you. As browsers continue to prohibit the collection of third-party data, many advertisers are shifting their focus to first-party data.

Why many marketers are switching to server-side tracking?

Professionals noticed decrease in ad performance due to inaccurate or incomplete data they see in their advertising platforms.

Since third-party cookies are being constantly restricted, they might as well be gone soon. So everyone will have to switch to server-side tracking eventually.

What is the difference between Meta Conversions API Gateway and Signals Gateway?

Both provide ability to use first-party data. But there 2 main advantages to Signals Gateway. First, it allows you to use any sources and distribute data to any destinations, since it is designed to be independent from Meta. Second, Signals Gateway uses the new pixel, so it shows even better results.

What’s the difference between Meta Pixel and Signals Gateway Pixel?

Signals Gateway Pixel collects data from your website and shares it exclusively with your Signals Gateway cloud server, without any use of third-party cookies and is independent from Meta’s servers.

How Signals Gateway helps to make advertising more effective?

More data signals transmitted → more accurate attribution → better functioning Meta ad algorithms → ad is shown to more relevant audience → higher conversion

How do you charge for it?

Event-based pricing charges you based on the number of tracked events per gateway. This scalable model helps you keep initial costs low while expanding your data volume as needed. There are no overage fees — if you exceed your plan, you continue paying the same rate per additional event. This ensures a predictable and dependable solution for marketing teams handling variable traffic.

Is it GDPR compliant?

Signals Gateway and first-party data help with compliance by reducing reliance on third-party cookies, ensuring user consent, and giving businesses full control over their data.

Server-side tracking for Meta ads, set up in minutes

Free up to 10,000 events a month. No credit card required.

Book demo
Freeup to 10,000 events a month
Pay as you grow
No credit card required
Try Birch