Your storefront sends a large amount of detail with every event β manufacturer part number, price band, dropship status, lifecycle, shipping class, and more. Analytics receives all of it and shows none of it, until you register each field as a custom dimension.
This is a one-time setup and itβs the difference between collecting data and being able to use it.
βΉοΈ Note: This is standard Analytics behavior, not a limitation of your store. GA4 ignores any parameter it hasnβt been told to keep. The data is already arriving β youβre switching on the reporting.
Why it works this way
GA4 has a fixed set of built-in dimensions. Anything beyond that is a custom parameter, which arrives with the event, is stored on the hit, and is invisible in every report until registered.
β οΈ Warning: Registration is not retroactive. Only data collected after you register a dimension is reportable. Do this early β waiting six months means six months you canβt analyze.
Item-scoped dimensions
These describe a product. Admin β Custom definitions β Custom dimensions β Create, with Scope: Item.
| Parameter | Suggested name | Answers |
|---|---|---|
item_mpn |
Manufacturer Part Number | Which MPNs sell |
item_price_bucket |
Price Band | Which price range drives revenue |
item_is_on_sale |
On Sale | Do discounts actually lift sales |
item_is_dropship |
Dropship | Do dropshipped items convert differently |
item_lifecycle_status |
Lifecycle Status | Active vs discontinued performance |
item_is_superseded |
Superseded | Are shoppers landing on replaced parts |
item_freight_required |
Freight Required | Does freight suppress conversion |
item_shipping_class |
Shipping Class | Shipping profile vs sales |
item_has_video |
Has Video | Does video content sell |
item_has_downloads |
Has Documents | Do spec sheets sell |
item_days_on_shelf |
Days On Shelf | How long stock takes to move |
item_sku |
SKU | Your own identifier |
item_part_number |
Part Number | Catalog part number |
π‘ Tip: You have room for 27 item-scoped dimensions. Register the ones tied to a decision youβd actually make β start with price band, dropship, on-sale, and freight.
πΈ Screenshot placeholder: GA4 Admin β Custom definitions, creating an item-scoped dimension.
Event-scoped dimensions
These describe the visit. Same screen, Scope: Event.
| Parameter | Suggested name | Answers |
|---|---|---|
page_type |
Page Type | Which page types convert |
user_logged_in |
Logged In | Do accounts convert better |
session_count |
Session Count | How many visits before buying |
first_touch_source |
First Touch Source | What originally introduced them |
first_touch_medium |
First Touch Medium | The channel that introduced them |
first_touch_campaign |
First Touch Campaign | Which campaign started it |
lead_type |
Lead Type | Which lead kinds convert |
form_name |
Form Name | Which forms perform |
search_term |
Search Term | What shoppers look for |
metric / rating |
Web Vital / Rating | Page-speed detail |
π‘ Tip:
first_touch_*is the valuable set. GA4βs built-in attribution is last-click by default β registering these lets you compare what introduced a customer against what closed them.
Doing it
- Open Analytics β Admin (gear, bottom-left)
- Custom definitions β Custom dimensions
- Create custom dimension
- Dimension name β what youβll see in reports (βPrice Bandβ)
- Scope β Item or Event, per the tables above
- Event parameter β the exact parameter name, spelled precisely (
item_price_bucket) - Save, and repeat
β οΈ Warning: The parameter name must match exactly, including underscores. A typo produces a dimension that silently stays empty forever.
Using them
After 24β48 hours of collection, they appear as dimensions in Explore and in custom reports.
Worth building first:
- Revenue by price band β which tier actually carries the business
- Conversion rate by dropship status β whether dropship hurts
- Revenue by first-touch source β true channel value, not last-click
- Sessions before purchase β your real consideration cycle
πΈ Screenshot placeholder: A GA4 Explore report using a custom item dimension.
