- Home
- Blog
- Meta data sharing restrictions
- Meta data sharing restriction solutions: what to compare
Meta data sharing restriction solutions: what to compare
Six approaches to a confirmed Meta data sharing restriction: what Meta receives from each, what you'd change, and the questions and costs to check before you buy.
Shahzada Ali Hassan, founder of Crisperchecked against 7 sources
Tools
The short answer
A Meta data sharing restriction solution must get Meta a usable Lead or Purchase for the action your website records. Meta marks an ad set learning limited when it's unlikely to get about 50 optimization events in a weekfacebook.com, so an event your campaign can't use costs delivery. This checklist is for owners with a confirmed restriction comparing fixes.
- If you need Lead or Purchase on your current site, ask for standard events on your existing domain; expect DNS and snippet work, not a site move.
- If a fix renames the event or sends a custom one, expect Meta to hold it for review before campaigns can use it.
- If a fix needs a new domain or redirect page, budget for moving your ads, landing pages and pixel.
- Server-side tracking on its own doesn't lift a restriction; it applies to the pixel and CAPI alike.
- Sources checked 26 October 2026.
FREE AUDIT
NO LOGINCheck what Meta and Google can count on your site
- Your site
Crisper- Meta and Google count it
Enter your website to see how good its tracking is, and whether Meta is likely restricting it.
On this page 9 sections
- What does a data sharing restriction solution have to do?
- Which approaches exist, and what does each change?
- Which approach fits your site?
- Which buying mistakes cost the most?
- What should the total price include?
- What should you confirm before changing your setup?
- When isn't Crisper the fix?
- When should you choose Crisper?
- What changed in this guide
We make Crisper, which sells restriction recovery. This guide compares approaches, not vendors. Each approach below is described in at least one provider's public documentation, read on 26 October 2026. We haven't tested other providers' products, and nothing here is scored or ranked.
01What does a data sharing restriction solution have to do?
It has to get Meta a usable event for the action your website actually records, under the restriction your account shows. If your site records enquiries, that's Lead. If it takes payments, that's Purchase. A checkout example in a sales deck doesn't tell you whether a provider handles your clinic's form or booking tool.
A data sharing restriction is Meta's limit on what a domain in a sensitive category can share. Meta's restriction guidancefacebook.com separates limits on event details, on certain standard events, and on all event sharing. It isn't a broken installation, where the event never fires, and it isn't a disabled ad account, which is a policy decision you appeal. If you aren't sure which one you have, start with the restriction diagnostic.
Which conversion will Meta use?
- Answer you need
- The exact standard or custom event, the campaign setup it needs and the completed action it represents
Does this cover my restriction?
- Answer you need
- Your affected event and any full-domain or regional limit, with a check agreed for your account
What changes on my website?
- Answer you need
- Supported platform and form or booking path, plus any domain, landing-page, pixel or campaign change
Who does the installation?
- Answer you need
- Named duties for you, your website manager and the provider, including the senders you already have
What evidence ends the setup?
- Answer you need
- A completed action, the matching event received, duplicates handled and the event available to the intended campaign
If you already installed CAPI, say so in the first call. The blocked-CAPI guide explains why a working connection can still leave a restricted event unusable. The question for a provider is what its service changes for that event.
02Which approaches exist, and what does each change?
Six approaches show up in providers' documentation. They differ in what Meta receives and in what you have to change, and the same label, server-side tracking, covers several of them.
Server-side tracking you configure
- What Meta receives
- The same events, sent from a server. The restriction still applies
- What you change
- A server container and someone to configure and maintain it
- Usual billing unit
- Requests, or a plan per product
- Best for
- Teams with a developer who want control of their tracking
Website event relay
- What Meta receives
- Standard and custom pixel events relayed through CAPI
- What you change
- A snippet on your site
- Usual billing unit
- Per pixel
- Best for
- Owners whose current pixel events already fire on the right action
New domain or route page
- What Meta receives
- Events from a domain Meta hasn't restricted
- What you change
- Ad destinations, a new domain or route page, often the pixel and campaigns
- Usual billing unit
- Events or orders
- Best for
- Stores that can move ad traffic to a new domain
Renamed or custom events
- What Meta receives
- A custom event in place of Lead or Purchase
- What you change
- The event your campaigns optimize for, and Meta's review of it
- Usual billing unit
- Usage units or orders
- Best for
- Accounts where a custom event is allowed and enough
Modeled conversions
- What Meta receives
- Predicted conversions with predicted values, not actual ones
- What you change
- A prerequisite Meta beta for value optimization, per the provider
- Usual billing unit
- Quoted per project
- Best for
- Advertisers comfortable optimizing on predictions
Standard events on your existing domain
- What Meta receives
- Usable standard Lead and Purchase, with your site on the domain you have
- What you change
- A tracking subdomain in DNS, the Meta integration and tracking snippets
- Usual billing unit
- Per tracking subdomain
- Best for
- Owners who need Lead or Purchase back without moving the site
Stape's healthcare guidancestape.io says the restrictions apply to both the pixel and CAPI, which is why the first row isn't a fix on its own. For custom events, Meta's restriction guidancefacebook.com says they can be blocked until you review and confirm them, or unavailable under a full restriction. SegmentStream's FAQsegmentstream.com describes the modeled row: synthetic conversion events with predicted values, with value optimization on custom events needing Meta beta access.
Many guides also tell you to strip health terms from URLs, event names and parameters. That's worth doing, because it limits what Meta trims or flags, but it isn't a seventh fix. Stape's guidance says server-side cleanup does not remove the restrictionsstape.io; it only stops you sending details that cause blocks or stripped parameters.
Health-privacy platforms are a separate kind of provider. Their first job is keeping health data away from the ad platforms, with a signed BAA. Curve Compliancecurvecompliance.com filters health data, can send events under neutral names, and advises moving campaigns to an event or objective Meta still allows. Freshpaint's February 2025 postfreshpaint.io advised replacing Meta's pixel with its tracker and renaming conversions to generic custom labels. Choose one of them when a BAA and governed data are the requirement; ask it directly which event Meta will receive for the conversion you need.
If you're weighing one provider, each has a one-to-one page that compares what you'd build or change to start: Stape, Metamorph, Zappush, Popsixle, Upstack Data, CustomerLabs, Aimerce, Curve Compliance and Freshpaint.
03Which approach fits your site?
Start from what your site records and what you can change. An approach can be right for one job and wrong for your restricted Lead.
A clinic or practice with a lead form or booking tool
Start with the last row: standard Lead on the domain you already advertise. A new domain means rebuilding landing pages and moving every ad, and a renamed event still needs Meta's review. The risk to watch is the success record. Use the booking and form guide to find which tool records the completed booking, because that's what the event has to report.
A Shopify store selling in a restricted category
Shopify-focused services show up in the route and custom-event rows, often priced per order. Ask which event your campaigns will optimize for and whether you'd have to move to a separate root domain. The risk is buying an attribution report when what you needed was tracking.
A team with a developer who wants the infrastructure
Server-side tracking you configure gives that developer control of the container, and Stape is the common choice. Know which product you already have, sGTM hosting, CAPI Gateway or Signals Gateway, before buying another connection. The risk is expecting the server to lift the restriction; Stape's own guidance says it doesn't.
The agency on the account
Use the same five questions for each client domain, and keep the client's domain unless the client agrees to move. The risk is a fix that works for one client's Shopify store and not for the next client's clinic form, so confirm each site's platform before you quote.
04Which buying mistakes cost the most?
- Replacing the pixel or ad account. Meta applies the restriction to the domain, so a new pixel on the same site inherits it and the weeks of setup buy nothing. Fix: change what reaches Meta, not the pixel. The pixel reset guide explains why.
- Buying server-side tracking to lift the restriction. The subscription runs while your ad sets stay short of the events they need. Fix: ask what the service changes for your restricted event, not whether it's server-side.
- Accepting a renamed event as the fix. A custom event can sit blocked until you review it, and campaigns optimizing for Lead can't use it until you switch them. Fix: ask which event the campaign will optimize for and whether Meta must review it first.
05What should the total price include?
Compare the full cost for your site and volume, not the headline monthly fee. Providers bill on different units, so two prices only compare once you've converted both to your traffic.
- The billing unit: requests, relayed events, orders, pixels, usage units or a share of event value.
- What happens above the allowance: overage per order, per event or per unit.
- Onboarding and installation, which some providers charge separately. One published onboarding fee starts at $1,000unrestricted.popsixle.com before the first month.
- Add-ons, such as custom events or a first-party domain, priced on top of the plan.
- Which trial or refund terms apply to the exact service you're buying.
Crisper is done for you: $799 setup + $297 a month per tracking subdomain, one for each website.
06What should you confirm before changing your setup?
Agree a short setup record with the provider and whoever manages your website. It names the expected event, the changes, the bill and the evidence that ends the setup. Keep your privacy or compliance contact involved in reviewing what's shared with Meta.
- Record the website, Meta source ID, exact restriction notice and the completed action you need to measure. Include the actual form, calendar or payment path.
- Ask the provider to name the event Meta will receive and the event or conversion your campaign will use. Record any custom-conversion or campaign changes.
- List domain, DNS, pixel, script and ad changes, and who makes each one. Name the senders you already have so the change doesn't leave two of them sending the same event.
- Get the subscription, billing unit, allowance, overage, add-on, onboarding and installation terms in one written quote.
- Ask for the fields shared with Meta and any data the provider keeps. Have the right person review them for your business; a vendor's compliance headline doesn't replace that review.
- Agree a permitted test action and the completion check using the verification guide. Record receipt, duplicates and campaign availability separately from ad attribution.
A successful server response isn't the whole check. The event has to represent the right action on the right source and be available to the campaign you intend to run. Ad attribution is a separate question, with its own settings and window.
07When isn't Crisper the fix?
- Your form never creates a lead record, or the pixel never fires. That's an installation fault, not a restriction. Repair it first and check it with the verification guide.
- You need offline conversion upload. Crisper doesn't do it today; use the platform's own tools or a general tracking provider.
- Your job is media buying, creative or a Meta appeal. Crisper recovers events. The appeal guide covers what a review can and can't do.
08When should you choose Crisper?
Choose Crisper when a confirmed data sharing restriction leaves Lead or Purchase unusable and you want them back on the website and pixel you already have. Our team does the setup. Tracking is live within 24 hours of full access. You, or whoever manages your website, will need DNS, Meta integration and site access.
For example, Scaled AI, an agency for addiction treatment centers, ran 12 restricted treatment-center domains on Crisper on 9 October 2026, up from 2 at the end of May. What you give up is a container you configure yourself: the recovery layer is run for you, so it suits owners who want the events back more than they want to build tracking.
Two more cases are published. In the wellness coaching case study, without the business's name, Meta restricted a European coaching business's dataset; after Crisper's setup at the end of October 2026, Events Manager showed 61 Purchase events received by Conversions API for 13 October to 9 November, with event match quality of 9.3 out of 10. That is Meta's count of events received, not sales. Before the Crisper app existed, its founder rebuilt purchase tracking on the same domain for Yatra Kundalini Activation in 2025. Ads Manager showed "€20,286.80 spent, 78 purchases, ROAS 0.14" for 1 May to 30 June 2025 and "€2,268.47 spent, 126 purchases, ROAS 2.78" for 27 July to 2 August 2025. Those are attributed purchases over windows of different length, not revenue or profit.
09What changed in this guide
- 16 November 2026: Added health-privacy platforms (Curve Compliance and Freshpaint) to the approaches, with their comparison pages, and two published cases: the anonymised wellness coaching case and Yatra Kundalini Activation.
- 15 November 2026: The page now books a free call; our team does the setup.

