Lead is blocked: should the clinic switch to Instant Forms, Traffic or Landing Page View?

Which campaign setups still work while Lead is blocked?

For restrictions on certain standard events, Meta's restriction page suggests "more upper-funnel events". For full restrictions it names the Awareness, Engagement and Traffic objectives. It does not mention Instant Forms, Landing Page View or CRM conversions. The Instant Forms and Landing Page View rows come from Meta's own lead ad and landing page pages, and the CRM row is covered below. Weighing them is your call.

None of these needs the category review to finish first. The review guide covers whether to keep spending during one. If you would rather fix the website event than work around it, skip to the main fix.

Are Instant Forms better or worse than website leads?

No source opened for this post compares the quality of Instant Form leads with website leads, so this post makes no claim either way. What changes is where the lead is captured and what the ad set aims at. With Instant Forms, people fill out a form without leaving Facebook or Instagram, and name, email and phone number may be prefilled. A website lead runs through the clinic's own form, booking tool and thank-you page.

• Meta records the submission, so the lead does not depend on the website event that is blocked.
• The goal in Meta's lead ad setup is "Maximize number of leads". The qualified leads goal for instant forms needs a CRM connection.
• The Instant Forms page lists custom questions, conditional logic, phone number verification and work email validation as quality filters. No source opened here tests whether they raise lead quality for a clinic.
• Meta's Advertising Standards say lead ad questions must not request health information, including medical treatments and conditions, without Meta's prior written permission. Check every custom question with the clinic's counsel.
• Meta's Website and instant forms setup supports only the Lead event. That is the blocked event, so choose Instant forms alone. This is an inference from Meta's page, so test it in Ads Manager.

Meta's restriction page covers event data shared through Business Tools and never mentions Instant Forms, and no page opened here says how a restricted domain affects an Instant Form campaign. Check the campaign in the account. To judge the two sources for one clinic, compare booked appointments by lead source over the same period in the clinic's own records, as in the CRM reconciliation worksheet.

What do Traffic and Landing Page View campaigns optimize for?

Both aim at visits. In Meta's objective table, Traffic is to "increase traffic to an online destination". With landing page view optimization, Meta tries to show the ad to people it thinks are most likely to click and fully load your website. Meta says that since July 2025 the goal is available to advertisers with pixel sharing challenges, and its only eligibility requirement is a functional webpage.

Meta recommends landing page views over link clicks when you want more traffic to specific pages, because it can improve traffic quality. It adds that an ad set optimized for conversions needs about 50 or more per week, and that landing page view optimization could be an effective alternative when it does not get that many. Meta also says it suits advertisers without lower-funnel events set up.

Landing page views are counted through Meta's in-app browser or a Meta Pixel on the page, and some are modeled. No page opened here says how that count behaves at each restriction depth. After you switch, confirm that landing page views show in the results column.

Switching has a cost. Meta lists a change to the optimization event as a significant edit, and an ad set is learning limited when it is unlikely to get about 50 optimization events in the week after the last significant edit. Meta calls that "isn't a penalty" and lists choosing a more frequent optimization event as one fix. A page load happens more often than a lead, so that bar should be easier to reach. After the switch, though, the ad set learns from page loads, which say nothing about who enquires.

Can the CRM send conversions while the website event is blocked?

Crisper takes conversions from any CRM that can send an outbound webhook, including GoHighLevel and Salesforce. You connect your CRM by webhook, and the clinic's own conversions come through Crisper. That is a separate path from Instant Forms. If the CRM cannot send a webhook, this option is not available.

What the CRM sends is only as good as what it records. Agree with the clinic whether the conversion is a submitted enquiry or a booked appointment before you connect it, and keep that definition when you compare sources in the CRM reconciliation worksheet.

Meta has its own CRM route for lead ads. Its Conversions API for CRM page says a connected CRM can send lead data to Meta to help optimize lead ads for higher quality instead of volume. That is Meta's route, not this one. No Meta page opened for this post says how a restricted data source treats events from either route, so check them in Events Manager before you rely on them.

What fixes the blocked Lead event itself?

A stopgap changes the campaign, not the data source restriction. On its restriction page Meta says you can ask for a review of a category Meta assigned and will email its decision, and it gives no deadline. Ask in parallel with the review guide, and check what the restriction covers in the restrictions explainer. A fix has to make the website Lead and Purchase events usable on the clinic's existing domain, so the campaign can learn from the result the clinic cares about again. That is what Crisper's recovery setup does.

Scaled AI runs Meta lead-gen for treatment centers from one agency org. Its clients' domains were restricted, and Crisper recovered usable Lead events on the existing domains. As of 7 October 2026, 12 of its restricted treatment-center domains are active on Crisper, and 10 of them recorded 207 Lead events through Crisper in the previous seven days. That is Crisper's own count of Lead events sent from the clinics' existing domains, so confirm your own in Events Manager. Its founder, Mitchell Price, says in the case-study video that cost per lead went down after the tracking changed. That is his account, not a measured result for your clinic. The Scaled AI case study has the video.

One restricted site shows both event types at once: an ear-care clinic in Ireland recorded 17 Lead events and 99 Purchase events through Crisper in the seven days to 7 October 2026, on the domain it already had. The counts are Crisper's own, not Meta's, so check your own in Events Manager.

If you need spend this week, run a stopgap. Moving back to a lead event later is another significant edit, so plan that change once instead of testing weekly. After any change, use the verification guide to check event receipt separately from ad attribution.

If the clinic's website Lead or Schedule events stay unusable under a confirmed restriction, we recommend Crisper. It recovers the standard event server-side on the clinic's existing domain, including when PageView has stopped, to make Lead and Purchase usable again. Setup takes about 5 minutes when you have DNS access, access to the Meta integration and the ability to add the tracking snippets, and the founder sets up the first client domain with you. Start 7-day trial and run it alongside the setup you picked. A payment method is required, with one trial per domain and 7 days to cancel. 30-day money-back guarantee. We keep working with you until it is fixed. Once tracking is installed and events fire, they can appear in Events Manager within about 30 minutes. Verify DNS, connect the Meta integration and install the tracking snippets on the existing site. Then submit one test enquiry and check in Events Manager that a Lead arrives and no restricted-event warning appears for it.