Meta can receive your GA4 key events through a partner integration in Events Manager. Useful without a pixel, risky next to one, and it does nothing for how Meta looks in GA4.
In Meta Events Manager, under Partner integrations, you can connect a GA4 property. You then map GA4 key events to events in your Meta dataset, the thing that used to be called the pixel. Meta suggests the mappings, you check them. A few screens, no tag work.
Data flows one way only: from GA4 to Meta. It doesn't change how Meta traffic shows up in GA4. If that's your problem, the causes are elsewhere, see Meta Ads against Google Analytics.
Use it if there's no Meta pixel or Conversions API yet and you want Meta to optimise on conversions without waiting for a tag project. It beats running campaigns blind.
Don't stack it on top of a working pixel and CAPI setup. Mapping a GA4 purchase onto a Meta purchase you already send risks counting it twice. Check for duplicates before you map anything.
Don't treat it as the end state. Meta only lets you map web events, and it only gets what GA4 collected. It isn't a replacement for a proper pixel and CAPI setup.
Privacy: you choose whether Meta gets events from all traffic or only from visitors who came through Meta ads. The second option filters on the utm_source values of your Meta ads and isn't available if you use more than 50 of them. With all traffic, Meta also receives events from people who never clicked an ad. Run that past whoever handles privacy, and mention it in your privacy statement.
Ownership: you need at least Viewer access to the GA4 property. If the person who connected it loses access to GA4 or Meta, the connection can break, so connect it with a shared account, not a personal one. Meta usually takes 2 to 7 days to validate the setup, in rare cases up to 14. After that, check the connection quality on the integration page.
The click-by-click setup is on newmetrics.io.
Want to talk about this?