> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set the Meta Event Source URL for multiple funnels

> Set the Meta Event Source URL for multiple funnels in Cometly, so Meta knows which domain each event came from when one pixel covers them all.

The Event Source URL tells Meta which website an event (a tracked action such as a lead or a purchase) came from. If you use the same Cometly pixel (the tracking script on your site) across multiple funnels or domains, and your integration doesn't send a page URL by default, you need to set the Meta Event Source URL for multiple funnels manually, once for each event.

This matters most if you run Meta ads in a **Special Ad Category** such as health, social issues or politics, where Meta requires a valid Event Source URL for optimization and attribution. With a fixed URL on each funnel's event, Meta knows which domain every lead or sale came from, so it can keep optimizing your campaigns.

> [!NOTE]
>
> Before you start, the Meta Conversion API needs to be set up in Cometly (see [Configure the Meta Conversion API](https://docs.cometly.com/guides/conversion-api/meta.md)), and each funnel needs an event that reaches Cometly through an integration such as a [webhook](https://docs.cometly.com/integrations/webhooks.md).

## Why the Meta Event Source URL matters for multiple funnels

Meta's Conversion API (the server-side connection Cometly uses to send your events to Meta) uses the Event Source URL to understand **where an event occurred**. When this value is missing:

* Meta may restrict optimization.
* Your ad performance can suffer.
* You may become **non-compliant** with Meta's policies for regulated business categories.

To solve this, you can set the Event Source URL in Cometly yourself, even if your platform (for example ClickFunnels) doesn't send it automatically.

## The solution: set a fixed value for each funnel

To make sure Meta receives the correct Event Source URL:

1. Create a separate event integration for each funnel or domain.
2. In the mapping of each one, map the **Event Source URL** field to a fixed value.

Cometly then sends the correct source URL to Meta, which improves attribution accuracy and keeps you compliant.

### Example setup in Cometly

Say you track the `Lead` event for two different domains with the same pixel. You would configure it like this:

| Setting | Event integration 1 | Event integration 2 |
| - | - | - |
| **Event name** | Lead | Lead |
| **Mapped fields** | Email, Name and so on | Email, Name and so on |
| **Event Source URL** (fixed value) | `https://www.cometly.com` | `https://www.cometlymarketing.com` |

### Set the fixed value

1. In Cometly, go to **Events Manager** and click **Edit** on the event (or **Configure** if it is still a draft).
2. On the **Configure Mapping** step, click **Add Field** and choose **Event Source URL** under **Cometly Fields**.
3. Open the selector under **Data Fields**. Under **Dynamic Data**, choose the `fixed_value` option. The selector closes, and you type the URL of the funnel in the row itself.
4. Click **Save & Continue**.

![Event Source URL mapping row with the Data Fields picker open, marker 1 on the fixed\_value option and marker 2 on the typed value https://www.cometly.com](https://mintcdn.com/cometly/4NU5YV9iL1PADmGE/images/integrations/guides/meta-event-source-url-multiple-domains/01.webp?fit=max\&auto=format\&n=4NU5YV9iL1PADmGE\&q=85\&s=591e5b4a715a94e6f6664b39ecdd7a51)

## Use filters to target the correct funnel

Apply **filters** to each event integration so that only the correct one processes an event. You add them on the **Filtering** step, which follows the mapping step.

For example, use a webhook field such as `funnelId`, `pageId` or a custom tag to:

* Match the correct integration to the correct funnel.
* Prevent duplicate or incorrect events from being sent.

This keeps your setup clean and makes sure Cometly sends the correct URL every time.

## Check it worked

Open each event from **Events Manager** again. On the mapping step, **Event Source URL** is listed with that funnel's URL as its fixed value. On the **Filtering** step, a sample record from the matching funnel shows a green box confirming that the webhook would have continued, with **PASS** next to each condition.

## Recap

* Platforms like ClickFunnels don't send Event Source URLs by default.
* If you use one pixel across multiple funnels, set a fixed value per domain.
* Create a separate integration per funnel.
* Use filters to match data to the correct funnel.
* No changes are needed to your pixel code.

## Frequently asked questions

### Do I need a new pixel?

No. You do not need to reinstall or reconfigure your pixel. Your tracking stays the same. This is strictly an integration-level change that gives each funnel its own Event Source URL value.

### 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 an integration such as a webhook may not include a page URL, so you set it yourself with the steps on this page.

### Is the Event Source URL field required on every event?

No. **Event Source URL** is an optional field in the event mapping. Add it if your business is in one of Meta's restricted categories and your integration doesn't send a page URL.

## Next steps

* [Event source URL for the Meta Conversion API](https://docs.cometly.com/guides/conversion-api/meta-event-source-url.md)
* [Send event data to Cometly with webhooks](https://docs.cometly.com/integrations/webhooks.md)
* [Configure the Meta Conversion API](https://docs.cometly.com/guides/conversion-api/meta.md)
* [Fix Meta Conversion API events that are not sending](https://docs.cometly.com/support/troubleshooting/conversion-api/meta-capi-not-sending-events.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.