Event Blocking Rules

Event Blocking Rules stop certain browser events from being sent to an Ad Platform. You have one rule per Site. PixelFlow evaluates that rule once for Meta and once for TikTok. A match can skip Meta and still send TikTok, or the reverse.

A rule that blocks too much can also stop real conversions from counting.

If every Ad Platform is blocked, the event does not appear in PixelFlow Event Logs. If at least one Ad Platform is allowed, the event appears once and Sent to shows who received it.

What's already set up for you

Every new Site comes with the most common protections already turned on. In most cases you do not need to add or change anything:

• Bots and automated traffic: PixelFlow automatically stops recognized bots, crawlers, scrapers, and automated browsers from sending events. They can still load your Site. This is built in and does not show up in the rule builder.

• Duplicate events from other tracking tools: The default All Events rule stops other tools on your Site from sending the same event again to that Ad Platform (Meta fbq or TikTok ttq).

• Immediate repeat events: The default All Events rule stops the same event from counting twice for the same visitor within 2 seconds. This catches clear double fires, including a very quick page refresh. A repeat match blocks every Ad Platform.

• Duplicate Squarespace orders: New Squarespace Sites stop a repeated Purchase with the same order page address for 90 days, even if the duplicate comes from a different browser. This match also blocks every Ad Platform.

The editable All Events rule added to every new Site is:

Block when the call is not from PixelFlow OR the same event happens for the same visitor within 2 seconds.

The specific Purchase rule added to a new Squarespace Site keeps both All Events protections and adds 90-day duplicate Purchase protection.

What each blocking rule does

You combine these conditions to build the rule you want. There is no Ad Platform picker. Each condition already says whether it applies to Meta only or to every Ad Platform.

Common simple cases

For most custom needs, one simple rule for a single event is enough. Use the narrowest rule that solves your problem, then test one case that should be blocked and one that should be allowed.

1. Open Blocking Rules for your Site and select Add Rule.

2. Choose the specific event you want to control unless the recipe says to use All Events.

When you choose a specific event, PixelFlow may fill in the form with a copy of the current All Events conditions. Those copied conditions will also apply if you save them. Review each copied condition and keep any protection you still need.

Block duplicate events caused by a page refresh

Use this for a page-load event, such as a Lead event on a thank-you page:

1. Choose the specific event, for example Lead.

2. Select It is the same event from the same visitor and set the interval to 1 minute.

3. Add another condition, keep AND selected, then choose It is the same page URL from the same visitor and set its interval to 1 minute.

4. Save the rule and wait up to one minute for it to take effect.

The first event is sent to every connected Ad Platform. If the same visitor triggers the same event on the same page again within one minute, the repeat is blocked for every Ad Platform.

Page addresses with different information after ? count as different pages. For example, /thank-you?order=1 and /thank-you?order=2 do not match. For Squarespace Purchase events, use the Squarespace duplicate Purchase protection instead.

New Sites already stop repeats within 2 seconds. Use this custom rule only when a page-refresh duplicate may happen later or when the page must also match.

Block sending to Meta when the Click ID (fbc) is missing

In most cases you should keep sending all eligible traffic to Meta so it can learn from the full set of conversion signals. If you specifically need Meta to receive only events that have a Meta Click ID:

1. Choose the specific event, for example Lead.

2. Select Block sending to Meta if the Click ID (fbc) is missing.

3. Save the rule and wait up to one minute for it to take effect.

Meta is allowed when an fbc value is available and skipped when it is missing. TikTok is not affected. A TikTok ad click without fbc still sends to TikTok.

This is not a perfect Facebook or Meta traffic-source test. A visitor from a Meta ad can lack fbc because of browser privacy settings or cleared cookies, and an fbc value can remain after an earlier Meta ad click.

Block an event on a known page

Use this when an event should stay active across most of your Site but must never be sent from a known page or section, such as a preview, staging, test, or internal-only page.

1. Choose the specific event.

2. Select The page URL matches a pattern.

3. Choose Equal to for one page or Starts with for a section and all pages below it.

4. Enter the domain and page without http:// or https://, for example example.com/preview.

5. Save the rule and wait up to one minute for it to take effect.

The event is blocked on the first matching page view, for every Ad Platform. This condition does not wait for a previous event.

Advanced configuration

Use this section when you need to combine conditions, change the rule for All Events, create a different rule for one event, or understand exactly which events and pages are covered.

Which events these rules affect

Blocking rules apply to events that PixelFlow tracks in a visitor's browser.

• Events tracked on your website by PixelFlow follow your All Events or specific-event rule.

• Events sent by another Meta or TikTok tracking tool can be stopped with The call is not from PixelFlow (evaluated for that Ad Platform).

• Events created automatically by PixelFlow's Stripe or Calendly connections do not use these rules.

• WooCommerce events sent by the PixelFlow WordPress plugin do not use these rules.

• Squarespace Purchase events have additional duplicate-order protection.

Stripe, Calendly, and WordPress WooCommerce events

Events created automatically by PixelFlow's Stripe or Calendly connections are still sent when a matching blocking rule exists. For example, a Schedule rule does not block a Schedule event created by the Calendly connection. The same rule does apply to a Schedule event tracked directly on your website.

On a WordPress Site, Event Blocking Rules do not affect WooCommerce AddToCart, InitiateCheckout, or Purchase events sent by the PixelFlow plugin. Events tracked directly on the website still follow your rules. The plugin has its own checks for consent, bots, excluded products, and duplicates.

Create or edit a rule

1. Open Blocking Rules for the selected Site.

2. Select Add Rule.

3. Choose All Events or one specific event.

4. Select a blocking rule.

5. Select Add another condition if needed. Keep AND when both conditions must match. Choose OR when either condition should block the event.

6. Review the live summary and select Save rule.

The live summary is one sentence. Each condition keeps its own scope in its label. Example: block sending Purchase to Meta if the Click ID (fbc) is missing, or block Purchase to every Ad Platform if the same event occurs within 2 seconds.

There can be only one All Events rule and one specific rule for each event. The event picker includes choices that already have a rule. Selecting one opens its existing rule for editing instead of creating another rule.

Saved changes can take up to one minute before the PixelFlow Script begins using them.

All Events and specific-event rules

All Events applies to every browser event that does not have its own specific-event rule.

When a specific-event rule exists, PixelFlow uses that rule instead of All Events for the selected event. It does not combine the two rules.

For example, suppose All Events blocks sending to Meta if the Click ID (fbc) is missing, while a specific Lead rule blocks only repeated Leads. A Lead without fbc is allowed to Meta when it is not a repeat, because the specific Lead rule replaces the All Events rule completely. TikTok was never affected by the fbc condition.

Editable copy of All Events

When you create a new specific-event rule, the Dashboard starts with a copy of the current All Events setup, including The call is not from PixelFlow.

• You may keep, change, or remove any copied condition.

• The saved specific rule is independent.

• Later changes to All Events do not update existing specific rules.

• Removing a copied condition means that condition no longer applies to the specific event.

Review the copied conditions before saving. After you save, this event has its own rule and later All Events changes do not affect it.

Do not block this event

Specific events can use Do not block this event. Saving this option tells PixelFlow not to apply any blocking rule to that event, including conditions from All Events. For Squarespace Purchase, it also turns off duplicate-order protection.

Choosing Do not block removes the conditions currently shown in the form. If you switch back, add the conditions you need again.

All Events cannot use Do not block and must contain at least one complete blocking rule.

Advanced condition combinations

• Use AND when every connected condition must match before the event is blocked for that Ad Platform.

• Use OR when either condition should be enough to block the event for that Ad Platform.

• If the rule does not match for an Ad Platform, the event is sent there.

• PixelFlow checks conditions connected with AND together before moving to the next OR option.

For example:

Block sending to Meta if the Click ID (fbc) is missing OR Block URL AND Same event within 30 seconds

PixelFlow reads this as:

Block sending to Meta if the Click ID (fbc) is missing OR (Block URL AND Same event within 30 seconds)

It does not read it as (fbc missing OR Block URL) AND Same event.

The fbc part skips Meta only. The URL and repeat part, if they match, skip every Ad Platform.

When several repeat conditions are connected with AND, they must all match the same earlier event.

History intervals

For same event, same page URL, and same referrer conditions, choose how long PixelFlow should look for an earlier event.

• Choose a whole number from 1 second to 90 days.

• Event history is saved in the visitor's browser. It does not follow the visitor to another browser or device, and it is removed if they clear their Site data.

• PixelFlow remembers the latest 100 events for up to 30 days. A browser rule cannot find an event older than that, even if you choose a longer interval.

• Some older rules may show an interval longer than 90 days. It stays unchanged until you edit it; any new value must be 90 days or less.

• An event is written to history when any Ad Platform is allowed. It is omitted only when every Ad Platform is blocked.

Same page URL or same referrer can block a repeat by itself. Connect it with AND when another condition must also be true.

Block URL

Choose The page URL matches a pattern to stop an event on a page or section of your Site. It does not prevent the page from loading, and it works on the first visit.

Enter your domain and the optional page path, for example:

• example.com/checkout

• example.com/preview

Always include the domain. Entering only /checkout will not work.

Equal to matches only the page you enter.

Starts with matches the page you enter and any pages below it.

Enter a complete page or section name. For example, example.com/check does not match example.com/checkout. Entering only example.com matches every page on that domain.

When checking a page address, PixelFlow:

• Treats http and https as the same

• Ignores www. at the beginning

• Ignores capital letters in the domain

• Ignores anything after ? or #

• Treats /checkout and /checkout/ as the same page

• Still distinguishes capital letters in the page path

Do not add * to include pages below an address. PixelFlow treats it as normal text; choose Starts with instead.

When this is the only condition, it blocks the first event on the matching page for every Ad Platform. When you connect it to a repeat condition with AND, both conditions must be true.

Block URL compared with same page URL

Block duplicate events from other tracking tools

Use The call is not from PixelFlow when another tool installed on your Site also sends events to Meta or TikTok. PixelFlow blocks the duplicate from the other tool on that Ad Platform and continues sending its own event.

• This works for standard Meta events and standard TikTok events. Some custom commands may not be detected.

• An event sent before PixelFlow finishes loading may not be detected.

• An older merchant ttq stub on the page can miss the wrap. If TikTok duplicates continue, remove the old TikTok Pixel.

• Other conditions in the rule still apply.

To block events from another tool only on checkout pages, connect these conditions with AND:

The call is not from PixelFlow AND The page URL Starts with example.com/checkout

If an event has its own specific rule, keep The call is not from PixelFlow in that rule when you still want to stop duplicates from other tools. Later changes to All Events do not update the specific rule.

Squarespace duplicate Purchase protection

New Squarespace Sites already include protection against repeated orders with the same page address. No setup is normally required.

If you create or change this protection, use a specific Purchase rule and add It is the same page URL from the same visitor. Then:

• Add this condition only once.

• Keep it by itself. Do not connect it to another condition with AND.

• Choose how long PixelFlow should look for a repeated order. New Squarespace Sites use 90 days.

• Connect any other reason to block Purchase with OR, not AND.

PixelFlow compares the current Purchase page address with previous Purchase events for the Site. This check works across different browsers. A hit blocks every Ad Platform.

Use a specific Purchase rule, not only All Events, so PixelFlow can stop the duplicate before any version is sent. Choosing Do not block this event or removing the same-page condition turns off this protection.

The page URL matches a pattern does not turn on duplicate-order protection.

Examples: ready-made combinations

Each example below shows the complete rule setup. If the form contains copied or existing conditions that are not shown, remove them unless you also want those conditions to block the event.

Block an event immediately on preview pages

For the event you want to block on preview pages, add:

The page URL Starts with example.com/preview

The matching event is blocked on the section's first visit and on descendant paths, for every Ad Platform.

Block repeat Lead events on one thank-you page

Connect these two conditions with AND:

The page URL Equal to example.com/thank-you AND It is the same page URL from the same visitor within 24 hours

The first Lead is sent. Another Lead on the same page in the same browser within 24 hours is blocked for every Ad Platform. A Lead on another page is still sent.

Block another Pixel script only in checkout

Connect these two conditions with AND:

The call is not from PixelFlow AND The page URL Starts with example.com/checkout

PixelFlow's own events continue. Standard Meta or TikTok events sent by other tracking tools are blocked on checkout pages for that Ad Platform.

Block a Lead without fbc on Meta, or a repeated Lead everywhere

Connect these two conditions with OR:

Block sending to Meta if the Click ID (fbc) is missing OR It is the same event from the same visitor within 30 seconds

A first Lead with fbc is sent to Meta and to TikTok. A first Lead without fbc skips Meta and still sends to TikTok. A repeated Lead is blocked for every Ad Platform, even if it has fbc.

Test a rule safely

1. Start with one specific event rather than All Events.

2. Review the live summary before saving.

3. Wait at least one minute for the saved change to take effect.

4. Trigger one event that should be blocked and one that should be allowed.

5. Confirm the allowed event appears in PixelFlow Event Logs. Check Sent to for Meta and TikTok.

6. Confirm a fully blocked event does not appear in Event Logs. Confirm a Meta-only skip still appears, with TikTok in Sent to and Meta not sent.

7. Optionally confirm the same outcome in Meta Test Events and TikTok Test Events.

Choose AND when both conditions need to match. Choose OR when either condition can block the event.

Permissions

Viewers can see blocking rules but cannot create, edit, or delete them. Changing rules requires permission to edit the Site and a subscription plan that includes Blocking Rules.