Meta Pixel /tr request
The Meta Pixel event request. Every page view or event the Pixel reports is sent to facebook.com/tr.
The request at a glance
- Request
GET or POSThttps://www.facebook.com/tr/- Sent by
- Meta Pixel
- Typically triggered by
- fbq('track', ...) calls, starting with PageView
- Related cookies
- _fbp
What this request is
facebook.com/tr is the Meta Pixel's event endpoint. Both the JavaScript Pixel (fbq) and its noscript image fallback report events here.
The Pixel ID and the event name are in the request, along with any custom data such as a purchase value and currency.
What typically triggers it
- fbq('track', 'PageView') when the Pixel base code loads.
- Standard events such as ViewContent, AddToCart, Purchase or Lead, and custom events sent with fbq('trackCustom', ...).
Important parameters
| Parameter | What it means | Source |
|---|---|---|
id | The Pixel ID. | Vendor-documented |
ev | Event name, for example PageView or Purchase. | Vendor-documented |
cd[...] | Custom data, for example cd[value], cd[currency] or cd[content_ids]. | Vendor-documented |
noscript | Set to 1 on the image fallback. | Vendor-documented |
fbp | The value of the _fbp cookie. | Commonly observed, not documented by the vendor |
fbc | The value of the _fbc cookie, when the visitor arrived from a Meta ad. | Commonly observed, not documented by the vendor |
dl | The page URL. | Commonly observed, not documented by the vendor |
eid | Event ID, used to deduplicate against the Conversions API. | Commonly observed, not documented by the vendor |
How to find it on a site
- Open the site in Chrome, open DevTools (F12, or Cmd+Option+I on a Mac) and go to the Network tab.
- Reload the page and type
facebook.com/trinto the filter box. - Click a matching request and open Payload to read its parameters. Some may be in the request body rather than the URL.
- If more than one id appears across requests, the page is sending events to more than one Pixel.
Sources
- Meta for Developers: Meta Pixel advanced
- Meta for Developers: Get started with the Meta Pixel
- Meta for Developers: fbp and fbc parameters (Conversions API)
The endpoint, the sender and the parameters marked vendor-documented were checked against the sources above on . Parameters marked commonly observed reflect how the request is widely read by practitioners; the vendor does not document them and can change them without notice. Browse all network requests.
Know when a tag stops firing
TagPipes Auditor checks with real browsers that your marketing pixels fire with the right parameters, and alerts you when tracking breaks. Pulse checks how marketing tags behave against your consent banner.
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.