Track Store Events More Reliably with Jeepno Pixel Pilot
Learn how Jeepno Pixel Pilot connects browser and server-side events for clearer ecommerce campaign measurement.
Marketing decisions depend on knowing what visitors do after they reach a store. Browser restrictions and connection loss can make that picture incomplete. Jeepno Pixel Pilot helps a business configure browser and server-side event delivery from one store dashboard.
What is Jeepno Pixel Pilot?
Pixel Pilot is Jeepno's Facebook Pixel and Conversions API integration plugin. It manages tracking connections and sends supported storefront events through browser, server or combined methods selected by the store.
Browser Pixel tracking
The browser method sends events from the visitor's browser using the configured Pixel ID. It is useful for normal client-side measurement and compatible campaign tools.
Conversions API support
The server method uses the store's access token to send supported events through a server-side connection. This can improve delivery reliability, although it does not guarantee attribution or bypass platform policies.
Store-owned credentials and controls
The store supplies its own Pixel ID and, when CAPI is enabled, its own access token. Browser and server methods can be enabled independently. An optional test-event code supports initial verification and should be removed after testing.
Tracking channels and assignment
Pixel Pilot supports tracking channels and assignment helpers so events can use the relevant configured connection. This is useful when a store needs more structure than one hard-coded script.
Event diagnostics
The dashboard and tracking flow provide operational visibility for configured pixels and event delivery. Diagnostics help teams notice missing credentials or setup issues before relying on campaign reports.
How Pixel Pilot benefits a business
- Centralizes browser Pixel and server-side CAPI configuration.
- Lets the store choose its active delivery methods.
- Uses store-owned credentials.
- Supports test-event verification.
- Connects supported commerce events to tracking channels.
- Provides a clearer setup and diagnostic workflow.
Privacy and platform responsibility
The store must obtain appropriate consent, protect credentials and follow Meta's terms, local privacy rules and advertising requirements. Tracking quality depends on correct configuration and the data available for each event.
