G
G. C.
ISSUE
Meta now requires
event_source_url
on Conversions API events for businesses whose dataset falls into a "restricted category" (Health & Wellness, Financial Services, etc.). Without it, Meta shows a warning in Events Manager: "Some Conversions API events will be blocked in 54 days" — and after that window, events stop being processed entirely.
We investigated the native "Meta Conversion API" workflow action thoroughly and found two gaps that, together, make it impossible to fix this without leaving the GHL platform:
GAP 1 — "Meta Conversion API" action has no
event_source_url
field
Checked in both connection types (Integration / Ad Manager) and both event types (Funnel Event / Lead Event), with and without "Custom Mapping" enabled. Custom Mapping only supports FBCLID (Funnel Events), Facebook Lead ID (Lead Events) and IGSID (Instagram DM events) — no field for the landing page / source URL.
Note: GHL DOES store this data per contact (Custom Values > Attribution > First/Latest > URL, e.g. {{contact.lastAttributionSource.url}}) — it's just not exposed as a mappable field in this action.
GAP 2 — "Webhook" action can't build a valid Meta CAPI payload either
As a workaround, we tried building a direct call to graph.facebook.com/{dataset_id}/events via the native "Webhook" action. This requires
event_time
as a Unix timestamp (integer, seconds since epoch) — a REQUIRED field for Meta CAPI.
The "Right now" Custom Values category only offers human-readable date/time components (Second, Minute, Hour, Date in various formats) — there's no
{{now.unix_timestamp}}
or equivalent. Without it, no valid payload can be constructed.
IMPACT
Any GHL sub-account whose dataset gets categorized under a "restricted category" by Meta (very common for health/medical aesthetics, financial services, legal, etc.) will see their Conversions API events blocked, with no native fix available. This likely affects a large number of GHL users in these verticals, not just one account.
REQUESTED FIXES
  1. Add
    event_source_url
    as a configurable field (static or Custom Value) in the "Meta Conversion API" action, for both Funnel Event and Lead Event types.
  2. Add a Custom Value such as
    {{now.unix_timestamp}}
    (current time, Unix epoch seconds), available in Webhook bodies and other workflow steps.
  3. Audit the "Meta Conversion API" action against Meta's full Server Event Parameters schema (action_source, event_source_url, event_time, etc.) to ensure compliance for restricted-category accounts.
RELATED
There's also an existing request for missing
user_data
parameters (em, ph, external_id, client_ip_address, etc.) — see "Facebook Conversion API additional parameters needs to be added". That's a related but separate gap (optimization/match-quality vs. our issue which is a hard compliance block).
REFERENCE
Meta dataset affected: 409806968859794 (category: Health & wellness providers / conditions and treatments)
Confirmed via GHL AI Support that this is not currently documented as supported.