All case studiesRestricted domain, on Crisper

Meta put a coaching business in a health and wellness category. Its Purchase events now reach Meta through Crisper's server.

A European online coaching business · Wellness coaching, Europe · 2026

Timeline

61

Purchase events the dataset received by Conversions API, 13 October to 9 November 2026

  1. 27 Oct 2026The funnel went onto Crisper
  2. 28 OctLead and Purchase set on the funnel pages
  3. 30 OctCrisper asked to stop parallel sends
  4. 10 NovEvents Manager: match quality 9.3/10

A European coaching business runs Meta ads to a sign-up funnel. Meta placed its dataset in a category with data-sharing restrictions, and some of its data was blocked in the European region.

A restricted dataset

Meta wrote that the business's dataset was "in a category that has data-sharing restrictions", because it "is associated with one or more medical conditions or health statuses". Some of its data was "now blocked in the European region", with restrictions "such as core setup and/or blocking of some standard events".

In Events Manager, Meta listed three of the dataset's websites in a "Health & wellness" category. On two of them, a review of that category had been rejected.

Setting up the funnel

The business came to Crisper in late October 2026 with a funnel built for Meta ads: an opt-in page, a sign-up page and a confirmation page. The site went onto Crisper on 27 October.

On 28 October the events were set: PageView on the opt-in page, a Lead when a visitor reaches the sign-up page, and a Purchase when they reach the confirmation page. Crisper sends them to Meta from its server by the Conversions API.

Another tool was also sending events to the same dataset. On 30 October Crisper asked the business to stop those parallel sends, so Meta would not count one conversion twice. The click IDs, UTM tags and events in Events Manager looked right that day.

What Meta received

On 10 November, Events Manager showed 61 Purchase events for the window 13 October to 9 November, all from the Conversions API through Google Tag Manager, with event match quality of 9.3 out of 10. Purchases begin in the chart at the end of October, after the setup. The count covers the whole dataset, which takes events from more than this funnel.

That is Meta's count of events received. It is not a count of sales, and not what Ads Manager attributed to the ads.

In the seven days from 9 to 15 November 2026, Crisper recorded 50 fired Purchase events and 1,839 fired Lead events for the funnel.

Meta Events Manager, read 10 Nov 2026

9.3/10

event match quality Meta gave those Purchase events

The first two figures are Meta's Events Manager, read 10 November 2026: events received, not sales or attributed conversions. The third is Crisper's count of fired events, not Meta's. The story comes from Meta's restriction email and Crisper's messages with the business, October and November 2026. The business is not named. This client runs on the Crisper app.

Check your restriction.

Bring your website URL or an Events Manager screenshot. We'll check the restriction and explain whether Crisper can help.

Choose a time for your free consultation
  • Restricted domain

    Behavioral health marketing, US · 2025–2026

    Scaled AI

    212

    Restricted treatment-center domains live on Crisper, end of May to 9 Oct 2026

    Read the case study
  • Addiction treatment, US · 2025

    Northridge Addiction Treatment Center

    037

    Website submit applications in Ads Manager, by ad set

    An addiction treatment center's ads reported no applications. The first week after setup reported 37.

    Read the case study
    BeforeAds Manager by ad set, undated
    AfterAds Manager by ad set, 14–20 Jun 2025