Skip to main content
The event source URL tells Meta which website an event (a tracked action such as a lead or a purchase) came from. Cometly’s Conversion API sends your events from Cometly’s servers to Meta, and this page shows how to add the Meta Conversion API event source URL to events that reach Cometly through webhooks, Zapier or the API. This matters if your business is in a category Meta restricts, such as health, political or social issues. With the URL on each event, Meta keeps processing your conversions, so your campaigns keep learning from the leads and sales Cometly tracks.
Before you start, the Meta Conversion API needs to be set up in Cometly. See Configure the Meta Conversion API.

Why add an event source URL?

Meta flags or blocks Conversion API events from sites that deal with sensitive topics (health, political or social issues) unless the event includes the Event Source URL parameter. Without it, Meta warns the site that it is “in a category with restrictions” and eventually stops processing its events. If your business is in a restricted category, you need to send the Event Source URL.

Benefits of including the event source URL

  • Continued use of the Meta Conversions API: prevents blocked events.
  • Compliance with Meta’s health, social and political rules.
  • Clear source attribution: Meta knows which domain your events come from.

Set up the event source URL for the Meta Conversion API

1

Identify your root URL

This is your full website root URL, for example:
2

Map the Event Source URL field

How you do this depends on how the event reaches Cometly.
Open the event’s setup from Events Manager and go to the mapping step (the one with the Cometly Fields and Data Fields columns).
  1. Click Add Field and select Event Source URL as the Cometly field.
  2. Open the data field picker next to it. Under Dynamic Data, choose fixed_value and type your root URL (for example https://www.cometly.com).
    Data field picker open on the Event Source URL row with the fixed_value option under Dynamic Data highlighted and https://www.cometly.com entered as its value
  3. Click Save & Continue.
    Mapping row with Event Source URL set to a fixed_value of the site URL, above the Add Field link and the footer buttons, with an arrow pointing at Save and Continue
3

Test and verify

  1. Send a test event that contains the Event Source URL.
  2. Check Meta Events Manager or the debug API and make sure no warnings appear.
  3. Confirm that conversion events are processed normally and nothing is blocked.
If you use one pixel across several funnels or domains, see Send the event source URL when one pixel covers multiple funnels.

Check it worked

Open the event’s mapping step in Events Manager again: Event Source URL is listed with your root URL as its fixed value. After your next test event, Meta Events Manager shows no restricted-category warning for that event.

Best practices and troubleshooting

Frequently asked questions

Does Cometly send the event source URL to Meta automatically?

For events tracked on your website, yes: Cometly sends the URL where the event was tracked as the event source URL. Events that arrive through a webhook, Zapier or the API may not include a page URL, so you add it yourself with the steps on this page.

Do I need a new Meta pixel to send the event source URL?

No. You do not need to reinstall or reconfigure your pixel, and your tracking stays the same. The event source URL is set in the event’s mapping, in your Zapier action or in your API payload.

Is the Event Source URL field required on every event?

No. Event Source URL is an optional field in the event mapping, and url is an optional field in the API. Add it if your business is in one of Meta’s restricted categories, or if Meta warns you that your site is in a category with restrictions.

Next steps

Still have questions or need a hand? We’re happy to help. Reach our team at support@cometly.com.