Events Manager says "Some Conversions API events will be blocked in 54 days". What does it mean?

What does the Conversions API blocked warning mean?

Meta documents one rule that fits. The server event parameters page describes event_source_url as the browser URL where the event happened, says it should match the verified domain, and says it is required for website events shared using the Conversions API. The same table labels the field optional in general, so the website-event note is the line that matters.

The only place we found the warning text is a HighLevel feature request, opened on 2026-06-15. The reporter quotes "Some Conversions API events will be blocked in 54 days" and says events stop being processed after that window. We searched for a Meta Help Center or developer page containing the warning text on 2026-10-07 and found none. Treat the 54 days as that user's example, not a deadline.

The warning does not tell you the domain has a data sharing restriction. A missing or mismatched URL is one cause and a restriction is another, and each needs its own check.

How do you find which dataset shows the warning?

Open Events Manager, choose Data sources (some Meta pages call this menu Datasets), and select the dataset by name and ID. Meta's Events Manager guide lists its tabs as Overview, Test events, Diagnostics, History and Settings. Settings shows the dataset ID and owner, so you can match it against the ID your CRM sends to.

Start with Diagnostics. Meta says issues sit under Active when detected in the last 24 hours, under Previously detected when nobody acts within 3 days, and under Ignored when someone dismissed them. Each issue is marked critical or a warning. Meta does not say where this particular message appears, so look at Overview as well if Diagnostics is empty.

A clinic can have more than one dataset. Check the one your CRM posts to, not just the first in the list. The audit checklist covers matching the source ID across the installation, Events Manager and the ad set. We have no Events Manager capture of this warning, so none is shown here.

How do you check the event source URL your CRM sends?

Look at what your tool sends, then confirm Meta received it.

1. Find the page URL field in the tool's Conversions API setup. Meta's name for it is event_source_url. The HighLevel reporter found no such field in its native Meta Conversion API action, with or without Custom Mapping. That was in June 2026 and we have not re-tested it, so look in your current version and ask the vendor if it is missing.
2. Confirm the URL is the page where the visitor acted, and that its host matches the clinic's verified domain, as Meta's parameter text asks.
3. Check action_source. Meta marks it required and defines website as a conversion made on your website. Note the value your tool sends for each event, because the URL rule is written for website events.
4. Send a test. Meta's server events test page says to open the dataset, click Test events, find the server events section, choose website or app events, and submit from a terminal or Graph API Explorer. It says the tool checks that the payload is well formed and received, and that results stay for 24 hours or until you clear them.

The page for browser events lets you filter activity by URL and parameters. The server events page does not say the tool shows the URL for a server event, so read the payload your tool sends. That page also describes a separate CRM test for lead ads, which is not the same flow as a website event from a workflow. GoHighLevel users can compare the mapping against the booking tracking guide.

What do you do with what you found?

After any change, repeat the test and follow the verification guide. One accepted test event does not show that live events are usable.

The restriction check is separate. Open the restriction guide and confirm the notice and the affected event. If a data sharing restriction on the clinic's Lead or Schedule events is confirmed, we recommend Crisper to recover usable Lead and Purchase events on the existing clinic domain. Scaled AI, an agency running Meta lead-gen for treatment centers, had 12 restricted domains active on Crisper on 7 October 2026, 10 of them with Lead events in the previous seven days; see the case study. That recommendation covers the restriction only; the checks above are how you handle this warning. Start 7-day trial. 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. After signup, verify DNS, connect the integration, install the tracking snippets, then confirm Lead or Schedule in Events Manager.