Advanced parameters

Advanced parameters are extra fields TrackingCoder can attach to every event it generates, computed on the fly at the moment the event fires. They show up as custom event parameters in GA4 (and equivalents in Meta / Ads), where you can use them as report dimensions or audience criteria.

What's available

• hour_of_day — 0–23, in the visitor's local timezone.
• day_of_week — Mon / Tue / etc., visitor's local timezone.
• time_on_page — seconds since the page loaded when the event fired.
• scroll_at_event — % of page scrolled when the event fired (0–100).
• traffic_source — broad category derived from document.referrer (Direct / Organic Search / Social / Email / Paid / Referral).
• prev_page — URL the visitor came from (same-session referrer).
• device_category — Desktop / Mobile / Tablet, derived from user-agent + viewport.
• page_section — for sites with semantic <section data-tc-section=...> markers, the section the clicked element lives in.
• visitor_count — visit number for this user (1 = first visit), counted via a first-party cookie set by the generated code.

Cost

Advanced parameters are part of the standard 1-credit-per-event price. Tick as many as you want during the wizard — no per-param surcharge.

How they're emitted

Each parameter is computed fresh per event (not at page load) so values like time_on_page and scroll_at_event reflect the moment the event actually fired, not the moment the script loaded. They're attached to the GA4 event object, the Meta Pixel custom event, and the dataLayer push.

Using them in GA4

GA4 needs custom dimensions registered before it can use parameters in reports. In your GA4 property: Admin → Custom definitions → Create custom dimension, and register each parameter name you've generated. Use the same name (e.g. hour_of_day) for the Event parameter. Once registered, you can filter and segment by the parameter within ~24 hours of the first event firing with it.

Common questions

Does TrackingCoder set first-party cookies for these? Only for visitor_count, which needs persistence across visits. All others are derived at event time without storage. visitor_count's cookie is named tc_vc, lasts 365 days, and is first-party (set on your domain).

Will adding params slow down the page? No — the computation is microseconds per event and happens after the platform send, not before.