Confort Oculaire
Five Meta pixels on one store, with no interference
Talk about my projectFlow: YouCan store, to GTM · JavaScript (5 Meta pixels), then Brand 1, Brand 2, Brand 3, Brand 4, Brand 5.
5
brands, each tracked by its own pixel, with no audience overlap
Source: GTM configuration delivered to the client
Multi-Pixel Meta setup on a YouCan store — 5 distinct pixels with dynamic sessionStorage routing to isolate each brand without cross-contamination. A project that required solid tracking architecture thinking before anything else.
5 active Meta Pixels · zero audience cross-contamination
- Context
- E-commerce · France · Eye health
- Services
- Tools
01 — The context
The client managed multiple product lines and brands under a single YouCan domain. Pixel events were mixing — wrong attribution uncalculable ROAS per catalog. A clean routing solution was needed without touching the backend.
02 — Before / after
| Before | After |
|---|---|
| Single Pixel for all brands | 5 Pixels routed via sessionStorage |
| Unsegmented purchase events | Each Pixel only receives its own events |
| Uncalculable ROAS per catalog | GTM container KX57TKZ3 structured & documented |
| Optimization impossible per product line | Solid foundation for per-brand scaling |
03 — The result
GTM/Pixel architecture live letting the client manage 5 brands independently in Ads Manager — clean attribution no signal loss solid base to scale each catalog separately.
04 — My role
Independent tracking consultant on a short-term engagement — designed and implemented the Pixel routing architecture without backend access.
05 — What I took away
Documenting the brand → Pixel mapping from day one avoids a black-box effect if the client adds a 6th brand later.
