Problem

On Polar Pixel Events, custom events (sent via the SDK’s custom() / shopifyEventName) are only exposed through the first_event_name and last_event_name session flags. The built-in funnel events (add_to_cart, collection_view, product_page_view) each have a session-level flag computed at query time, so they’re countable and attributable wherever they occur. Custom events don’t, so any mid-session occurrence is invisible to self-serve reporting.

Live impact (Spring Sleep): of 140 occurrences of their questionnaire_ts_eligible event over ~2.5 weeks, only 9 were visible via the first/last flags. The other 131 were mid-session and unreachable, despite the data being fully attributable (every event joins cleanly to its session’s channel, campaign, ad, and UTMs). Getting the breakdown required a manual warehouse pull.

Who it affects

Any tenant sending a custom pixel event who wants to count or attribute it. Not account-specific; it surfaces for every custom-event use case.

Requested behavior

Allow filtering and breakdown of polar_pixel_events by the event’s own name at the event grain, carrying the session’s existing attribution dimensions, the same way the funnel events work.

Engineering note

Per the pixel team’s investigation, an event_name dimension is already declared in dimensions.json but wired to no table. Hooking it up on Polar Pixel Events was described as ~a one-line synth-config change plus a test, in a normal deploy, with no enrichment work, dbt change, or backfill. Because it’s computed at query time, history is covered on ship. Flagged as a product-level change benefiting all tenants, not a per-account build; suggested benchmarking query cost first.

Out of scope

Session-scoped attribution only (each event inherits its landing session’s values), consistent with the funnel events. Not a request for first/last/multi-touch model credit.