Browser code observes what happens
A pixel or snippet runs in your visitor’s browser. It can observe available measurement signals and consent updates. Data the browser withholds or blocks has not been captured simply because the code is installed.
First-party tracking on your store’s own domain.
Collect available measurement data through your store’s own domain and connect it with your orders. Give campaigns more complete purchase data and see what reaches your advertising channels for each order.
The pixel, endpoint and server each have a role.
Your endpoint receives data
An address such as measure.yourstore.com can receive your measurements. This optional subdomain requires suitable DNS and Cloudflare configuration. An endpoint alone does not produce a complete purchase measurement.
The server processes eligible purchases
A connected order source supplies order data. Eligible purchase data can then be sent from the server to Google Ads or Meta when the required consent and platform data are available.
Example: from a store visit to an order check.
Fictional example: a visitor views a product, accepts the relevant cookies and places order EXAMPLE-104 for €79.00. The snippet sends available browser data through measure.yourstore.com. Your order connection supplies the order reference, amount and currency separately.
In the order view, compare the purchase, recorded consent and available measurement data. Then check whether an eligible platform event was sent and what response came back. Missing browser data remains missing; your own endpoint does not fill it in automatically.
Set up an endpoint on your domain.
Confirm the route and access you need
Review your store, order source, consent banner and advertising platforms. Ask your domain administrator to check whether the required DNS and Cloudflare configuration is possible.
Connect the endpoint and browser code
Follow the instructions for your subdomain and install the snippet in your store. Connect your order data as well; this is a separate step from browser collection.
Verify the complete route
Check that the endpoint is reachable and data arrives. Then compare an agreed test order with the recorded consent, order amount and platform delivery status.
What first-party tracking can and cannot solve.
Your own endpoint provides a collection route on your domain. It does not guarantee collection through every ad blocker or browser restriction.
First-party tracking does not replace consent. A different endpoint does not turn denied or unknown consent into permission.
This route requires domain access, suitable Cloudflare configuration and a usable order source. Platform availability and setup requirements are confirmed before you connect.
Questions about this connection.
Is a first-party pixel the same as server-side tracking?
No. The pixel collects data in the browser. Your endpoint receives data. Server-side delivery is the separate step that sends eligible data from a server to an advertising platform.
Do I need my own subdomain?
No, a custom endpoint is optional. Discuss the route that fits your domain access and store. In every setup, verify browser collection, the order source and platform connections separately.
Can I remove my consent banner?
An endpoint on your domain does not remove consent requirements. Keep your banner and consent signals part of the setup and assess which processing is permitted in your situation.
Continue exploring.
Would your store benefit from its own endpoint?
Discuss your domain and current measurement setup. We will establish the access and connections you need.
Discuss my store