Simplefriendly server-side tracking

for

Meta ads

in partnership with Meta

Get started

for other platforms

coming soon

Hassle-free setup

with user friendly interface

How it works

first-party

pixel

Immune to browser restrictions and ad blockers for reliable event tracking

hub

Events are collected and processed safely within your own gateway server

meta

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

With Bïrch Hub

conversion is higher

More data 
events

More accurate attribution

Better functioning ad algorithms

More relevant audience

Cricksy Dog after Switching to Bïrch Hub

30%

decreased
in CPA

35%

increased in conversions

40%

increased in total events tracked

Accurate Tracking Helped 
Pawz.rs Scale Campaigns Profitably

9+

ROAS on cold campaigns

22%

decrease 

in CPA

25%

increase in total tracked events

Pricing

per gateway
10,000 events/mo
Free
500,000
events/mo
$10
5,000,000
events/mo
$49
20,000,000
events/mo
$149
50,000,000
events/mo
$249
150,000,000
events/mo
$499
Create your Bïrch 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.

It reduces ad blocker impact and supports custom audiences (Beta). Using it alongside the Meta Pixel and Conversions API enhances performance. Meta reports a 23% lower Cost per Action for advertisers who integrate all three.

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.

It was initially designed by Meta to allow secure data transfers, and aligns with GDPR principles like transparency, data minimization, and purpose limitation. However, businesses must still ensure proper consent management and legal compliance. For instance, Europe-based businesses must use European gateway servers.

Bïrch Hub supports 3 domain zones for storing your data: US, EU and Asia.