Privacy and limits settings

Each website has its own Privacy and limits panel. It decides what Meta receives and how many requests one visitor may send.

Privacy and limits controls what leaves the relay for this website.

Rate limit is how many requests one visitor may send per minute. 60 suits almost every site.

Remove health terms replaces blocked words in page addresses and event text.

Hide the site's domain makes Meta see the relay's domain instead of yours.

Send visitor IP and browser improves matching in Meta. Turn it off if your risk analysis treats IP addresses as health information.

Click Save changes when you are done.

Next

Done

That is the whole flow. Try it in your own dashboard.

Watch again

1. Privacy and limits controls what leaves the relay for this website.

2. Rate limit is how many requests one visitor may send per minute. 60 suits almost every site.

3. Remove health terms replaces blocked words in page addresses and event text.

4. Hide the site's domain makes Meta see the relay's domain instead of yours.

5. Send visitor IP and browser improves matching in Meta. Turn it off if your risk analysis treats IP addresses as health information.

6. Click Save changes when you are done.

1. Step 1: Privacy and limits controls what leaves the relay for this website.
2. Step 2: Rate limit is how many requests one visitor may send per minute. 60 suits almost every site.
3. Step 3: Remove health terms replaces blocked words in page addresses and event text.
4. Step 4: Hide the site's domain makes Meta see the relay's domain instead of yours.
5. Step 5: Send visitor IP and browser improves matching in Meta. Turn it off if your risk analysis treats IP addresses as health information.
6. Step 6: Click Save changes when you are done.

Remove health terms from page addresses#

On by default. Words on the website's blocked terms list are replaced with page in page addresses and in the content name, type and category of events, before anything is sent to Meta. /ivf-consultation reaches Meta as /page-consultation.

Leave it on for any site in a sensitive field. Change the words themselves on the Blocked terms page.

Hide the site's domain from Meta#

Off by default. When on, Meta sees the relay's domain in page addresses instead of your site's. Turn it on when the domain itself says what the business does, like ivf-clinic-london.com, so Meta does not file the business under health.

Your own analytics still show the real domain.

Send visitor IP and browser to Meta#

On by default. When on, the visitor's IP address and browser are added to each event. Meta uses them to match events to people, which improves attribution.

An IP address identifies a person. Turn this off for sites, like booking pages, where your risk analysis treats it as health information. The relay never stores the raw IP either way. With this off, Meta still receives the browser's user agent string and Meta's own _fbp and _fbc cookie values when the visitor has them.

Rate limit#

How many requests one visitor may send per minute for this website, 60 by default. The tracker batches events, so one request often carries several. 60 is plenty for normal browsing. Raise it only if a page legitimately fires many events, like a long single-page booking flow.

Your account may have a ceiling on this number, shown as the field's maximum.

Read-only settings#

Your account team decides which of these you may change. Settings you cannot change are greyed out, with a note at the top of the page. Ask your account team to change them.