Background:
Meta recently flagged our Pixel with the “Core Setup” data restriction, which I understand limits the ability to track important parameters — particularly URL parameters like fbclid, utm_source, and other identifiers. This seems to impact attribution, event match quality, and how well the Meta algorithm can optimize our ads. From what I’ve read, the restriction essentially means browser-side tracking is degraded.
Question:
Can someone please confirm if I understand this correctly?
My current understanding is that setting up GTM + Stape + Facebook CAPI can fill in the gaps left by the Core Setup restriction — by passing those missing parameters (like fbclid, user IP, user agent, and even hashed email/phone) server-side.
Is that correct? And does this approach reliably restore attribution accuracy and improve signal quality for Meta’s ad delivery and algorithm?
There isn’t much information about the Core Setup on Meta’s documentation.
When it’s on, the browser-side tracking is heavily degraded. The restrictions apply to the JS Pixel level, meaning that the information is capped automatically by it before it leaves the browser (such as: custom parameters and the full URL and referrer). fbclid, user agent, IP address and hashed email/phone are still collected.
Now, the CAPI might be a way to send the data, because you are in control of the data sent and the Core Setup rescritions are not applied at collection time.
However, Meta may enforce it when the data is received.
This is just a deduction of what might happen, because the Core Setup is enforced on a Dataset, and the Dataset receives data from both the JS Pixel and CAPI.
Therefore, one option is to run the CAPI in parallel is see how the account performance behaves.