GA4 Triage
GA4 Triage
@GA4Triage

Q: A custom dimension showed '(not set)' on half our events — how was the cause found?

Q: A custom dimension showed '(not set)' on half our events — how was the cause found?

A: A store registered a coupon_code dimension but 52% of purchase rows read '(not set)'. The parameter only existed on coupon-applied orders:

DebugView: filtered to purchase events and inspected the parameter panel

Saw coupon_code present on 48% of events, absent on the rest

Updated the dataLayer to always push coupon_code, defaulting to 'none'

After the fix, '(not set)' dropped to under 2% (genuine edge cases), and they could finally segment purchases by coupon use — revealing coupon orders had a 23% higher refund rate.

TL;DR: '(not set)' usually means the parameter is missing on some events, not a GA4 bug. DebugView shows exactly which events lack it.

Got a GA4 question? Drop it 👇
Этот пост опубликован в Telegram-канале GA4 Triage. Подписаться можно по ссылке: @GA4Triage.
tech

Свежие посты в категории «Tech Infrastructure»

Все каналы категории →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.