URL triggers
Fire any Meta event the moment a page loads. No button to tag, no code, and it can read the details from the URL too.
Free trial. No card, no tag manager.
Trigger events when a page is loaded
Select an event and a page. The event is triggered on page load.
Page URL
https://
yoursite.com/thank-you
Event to trigger
Purchase
Event value
79.00
Create trigger
Match the start of a URL
Enter the beginning of a path and one trigger covers every order or booking confirmation, whatever comes after it.
Any standard event
Purchase, Lead, Schedule, CompleteRegistration or any other Meta standard event.
Fires once
Pair it with a blocking rule so a refresh of the page does not fire it again.
Improve accuracy with blocking rules
A thank-you page gets refreshed, bookmarked and reopened from the back button, and a plain URL trigger would fire a Purchase every time. A blocking rule stops that.
Block the same event from the same visitor within 30 minutes, block it when the Meta click ID is missing, or combine conditions with AND and OR, and the trigger only fires for conversions that actually happened.
1. Which event is this rule for?
Purchase
2. When should it be blocked?
Block when
It is the same event from the same visitor
within
30
minutes
AND
OR
Either one is enough
Block when
The Meta Click ID (fbc) is missing
Chose what to extract from the URL:
https://pixelflow.so/thankyou/?name=emmett&phone=123123
Data from URL (click to see in URL)
Data sent to Facebook
name -
emmett
First name (fn)
phone -
123123
Phone (ph)
Extract information from the URL
Booking tools like Calendly and TidyCal can send people to your thank-you page with the booking details in the URL: name, email, phone. Map those parameters once and PixelFlow attaches them to the event as hashed customer data, so a booked call arrives at Meta as a Schedule event with the identifiers it needs to match the person.
Map query parameters to Meta fields
If the URL carries data, PixelFlow can use it. Map value and currency for purchase amounts, and email, phone, first name, last name and location fields for matching. The dashboard suggests mappings from the parameters it sees.
Event Match Quality · Purchase
Events Manager
9.1
/ 10 · Great
was 5.4
Sent with every event
fbc click ID
fbp browser ID
external_id
IP + user agent
em · ph · fn · ln hashed
event_id
Connected
2 active
Stripe
Purchase, Subscribe, StartTrial
Calendly
Schedule
Platforms
Webflow
Framer
Squarespace
WordPress
Shopify
+ 9 more
Built for redirects from booking and payment tools
Calendly can append booking details to your thank-you URL. A URL trigger with parameter mapping turns that redirect into a Schedule event with the booker’s details attached, without the native integration.
FAQ
Everything you need to know about URL triggers.
Do URL triggers work with single-page apps?
Yes. PixelFlow listens for route changes on Framer, Webflow, Next.js and similar sites, not just full page loads.
Can one page fire two events?
Yes. Create two triggers on the same pattern with different events.
What if the confirmation page has no parameters?
The trigger still fires the event. Value and customer fields are simply not attached.
Can I read values from the path instead of query parameters?
Parameter mapping reads query parameters. Path segments can be matched by the trigger pattern but are not mapped to fields.
Which fields can I map to?
Value, currency, email, phone, first name, last name, full name, country, city, state and zip.
Does this replace the Calendly or Stripe integration?
It is the fallback. The native integrations send the event server-side from the tool itself, which is more reliable than a redirect.
Smarter, server-side tracking
Start sending accurate conversions today - no tag manager, no code, no developer required.
Compatible with
