TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-042

SYMPTOM FILE SYM-042 FILED 08 NOV 2026 · REVISED 22 NOV 2026

GA4 custom parameters not showing in reports: what to check, in order.

ALSO FILED AS
  • “GA4 custom parameters not showing in reports”
  • “GA4 event parameters not showing in reports”
  • “GA4 custom event parameter in DebugView but not in reports”
  • “GA4 custom dimension not showing in reports”
  • “GA4 custom dimension showing (not set)”
  • “can't find custom dimension in GA4 report”
  • “GTM event parameter not showing in GA4”
  • “GA4 test events in DebugView but not in reports”
  • “GA4 custom dimension or custom metric”

Baris Asa, tracking consultant, London · Last checked: 22 November 2026

GA4 custom parameters not showing in reports? If DebugView shows the parameter was sent, the usual cause is that nobody registered it: reports only offer a custom parameter once it is a custom dimension or metric in Admin, Data display, Custom definitions. After registering, allow 24 to 48 hours. Google’s pages don’t say earlier data is added, so plan on reporting from registration onward. Other causes: a name that differs by a character, the wrong scope, or test events a developer filter removes.

Check DebugView first. If the parameter is there, this is a reporting fault (F-601 ). If not, jump to If DebugView doesn’t show it.

The site sends checkout_type on every purchase. Your developer is right about that: DebugView shows it. The reports don’t. Or a custom dimension exists, and every row reads (not set).

That gap is on file as F-601 , and the Atlas entry for F-601 explains why GA4 splits collection from reporting. This note is the check, in the order I run it, and where to find the dimension once it works.

A check you can do without a developer

You need access to the GA4 property, nothing else.

  1. Ask whoever set up your tags for the list of custom parameters the site sends. Names, exactly as written.
  2. In GA4, open Admin, Data display, Custom definitions.
  3. Look down the Event parameter column, not the dimension name. The dimension name is a label and can be anything. The event parameter is what GA4 matches against the incoming data.

A name on the list with no matching row is the fault, found. A row that is close but not the same (checkoutType against checkout_type) is the fault too. Everything else on the list is registered, and the rest of this note goes through what can still hide it.

If nobody can give you the list, that is a finding in itself. It belongs in the tracking documentation, on file as F-501 when it doesn’t exist.

Before you blame registration

Three things make a registered parameter look missing. Rule them out first.

  • Your test traffic is filtered out. If you only tested in debug mode (Tag Assistant or GTM Preview), and the property’s Data filters page (in Admin) has a Developer traffic filter set to Active, those test events never reach reports. DebugView still shows them. Google says excluded data is never processed. Check with a real visit, or read the report a day after real traffic has flowed.
  • DebugView and the report are different properties. Check the property name at the top of both screens. A site with a staging and a live property, or two web streams, catches people here.
  • Rows are withheld, not missing. Low-volume rows can be held back by data thresholds, and rare values grouped into one row called (other). That is R-502 , covered in GA4 data thresholding applied.

The order I check it in

This part is for whoever set up your tags. The why behind each step is in the F-601 entry; here is only what to do.

  1. Read the hit. Open the site through Tag Assistant or GTM Preview, then GA4 Admin, Data display, DebugView. Fire the event and click it. Google lists every parameter that came with it. Copy each custom name exactly. Not there at all? Skip to If DebugView doesn’t show it.
  2. Match the name. Find the Custom definitions row whose Event parameter is that name, character for character. No row: register it. A near miss: Google doesn’t let you edit the event parameter after saving, so create a new dimension.
  3. Match the scope. Event for a detail of one action. Item for a detail of one product, sent inside the items array. User for a detail of the person, sent as a user property. Scope is also locked once saved.
  4. Check the date. Google says a new dimension is usable 24 to 48 hours after it was created and the data was sent, and that (not set) can show in the first 24 hours. Start the report range after the creation date: Google’s pages don’t say earlier data is added.
  5. Check the rows. Put Event name next to the dimension. (not set) on events that never send the parameter is correct.

Quota information on the Custom definitions page shows how many slots are left. A full quota is a quiet reason the rest of the list never got registered.

In DebugView (sent)Custom definitions (Event parameter)Scope · createdReport reads
checkout_type: expresscheckoutTypeEvent · 3 weeks ago(not set) on every purchase
promo_source: newsletternonen/anot in the picker
items[0].fabric: linenfabricEvent · 3 weeks ago(not set): sent in items, needs Item scope
customer_tier: returningcustomer_tierEvent · yesterday(not set): under 24 hours, wait
GA4 · DebugView beside Custom definitions · one purchase event · what the side-by-side shows · reconstructed from a test property, not a client account

Four rows, four different reasons, one symptom. Only the second is “never registered”. The first and third need a new dimension, because neither name nor scope can be edited. The fourth needs up to 48 hours.

How do I register a GA4 custom parameter?

You need Editor access or above on the property.

  1. Admin, Data display, Custom definitions, Custom dimensions tab, Create custom dimensions.
  2. Dimension name: a label people will understand, such as Checkout type. Google doesn’t allow hyphens in the name.
  3. Scope: Event, Item or User.
  4. Event parameter: the name from DebugView, typed exactly. For user scope, the user property name.
  5. Save.

A number you want to add up or average, such as a discount amount, goes in as a custom metric on the Custom metrics tab instead.

Replacing a wrong dimension? Create the new one, then archive the old one. Google says archiving can’t be undone, explorations and reports using the dimension stop loading until it is removed from them, and an audience using it stops collecting users. Check those first.

Don’t register everything. Google advises against unnecessary high-cardinality dimensions, meaning values that differ on almost every hit, such as order IDs or timestamps: they crowd reports and push rows into (other). Registering a value GA4 already has, such as page or transaction ID, Google says isn’t best practice, and it uses a slot.

Where do I find it after registering?

  • In an exploration. Explore, Blank. Click + next to Dimensions, open the Custom tab, tick the dimension and import it. Drag it to Rows, add Event name beside it and Event count as the metric. This works for every scope and is how I check.
  • In a standard report. Editors and administrators can open a detail report, click Customize report, then Dimensions, Add dimension, Apply, then Save and Save changes to current report. No Customize report button means no access. Item-scoped dimensions can’t be added here.

If DebugView doesn’t show it

Then it is a sending problem, and the fix is in Google Tag Manager or the site code, not in GA4.

  • The tag doesn’t list it. In GTM, open the GA4 Event tag. Under Event Parameters, each custom parameter needs a Parameter Name and a Value, usually a Data Layer Variable. Not listed, not sent.
  • The variable reads empty. In GTM Preview, click the event’s message and open the Variables tab. Empty there means the tag fired before the push (F-103 , see GTM tag fires before the dataLayer is ready) or the site never pushes it (F-301 , see GA4 purchase events missing items or value).
  • The name breaks Google’s rules. Parameter names can’t begin with _, firebase_, ga_, google_ or gtag., and can be up to 40 characters.
  • It is over a limit. On a standard property, Google allows 25 parameters per event and values up to 100 characters (page_title, page_referrer and page_location are allowed longer), and says it doesn’t log parameters over those limits, so check long free-text values first.

Fix the sending, confirm it in DebugView, then go back to the check.

Can I get the missing months back?

Google’s pages don’t say reports are filled in for earlier dates. Plan as if reporting starts on the day the dimension was registered. If the GA4 BigQuery export was running, every parameter that was sent, registered or not, is in the raw events (event_params, and items.item_params for item details), and the history can be read there.

How do I know it’s fixed?

  • DebugView shows the parameter on the event under the same name as the Event parameter field in Custom definitions.
  • Two days after registering, an exploration with the dimension and Event name shows real values on that event, and (not set) only on events that never send it.
  • The custom definitions list matches the list of parameters the site sends, apart from the ones you chose not to report on, and each registration has its date written down.

When the list of what the site sends doesn’t exist, the job is to build it from the container and DebugView, set it against Custom definitions, fix the gaps and hand the list over. The wider fault is filed as F-601 .

Common questions

Why are my GA4 custom parameters not showing in reports?

Usually because nobody registered them. GA4 stores the parameters your tag sends, within its collection limits, but reports only offer custom parameters registered as a custom dimension or metric in Admin, Data display, Custom definitions. The other causes are a registration under a slightly different name, the wrong scope, or a dimension created in the last 24 to 48 hours (Google’s pages don’t say earlier data is added).

I registered the custom dimension. Why does it still show nothing or (not set)?

Check three things. Has it been up to 48 hours since you created it and sent new data? Does the Event parameter field match the name in DebugView character for character? Are you reading rows for an event that carries the parameter? A purchase-only parameter reads (not set) on page_view rows, which is correct.

Where do I find a custom dimension once it is registered?

In a free-form exploration: click + next to Dimensions, open the Custom tab and import it. Editors and administrators can also add an event-scoped dimension to a standard report with Customize report. Item-scoped custom dimensions can’t be added to standard reports; use an exploration.

Do my DebugView test events show up in reports?

Not if the property has an active Developer traffic data filter. It excludes events sent in debug mode from reports while DebugView keeps showing them, and Google says excluded data is never processed. Test with a real visit, or check the Data filters page before deciding the parameter is missing.

Should a numeric parameter be a custom dimension or a custom metric?

A custom metric if you want to add it up or average it, such as a discount amount. A custom dimension if you want to group rows by it, such as a size band. Decide before registering: each is created on its own tab in Custom definitions.

The parameter isn’t in DebugView either. Is it the same problem?

No. Registration can’t report what never arrived. Missing on some hits only usually means the tag fired before the data was pushed (F-103 ). Missing on every hit means the site or the GTM tag never sends it, a collection fault rather than a reporting one.

Sources

Read on 8 November 2026 (the Create event-scoped custom dimensions page re-read on 22 November 2026 for the 24 to 48 hour wait, no hyphens in the name, Editor role and locked scope and parameter; that Google documents no backfill is not stated there, so the note treats it as an inference):

  • Google Analytics Help, Create event-scoped custom dimensions (Admin, Data display, Custom definitions; Editor or above; no hyphens in the dimension name; scope and event parameter can’t be changed after saving; usable 24 to 48 hours after the data was sent and the dimension created; importing it into a free-form exploration from the Custom tab)
  • Google Analytics Help, About custom dimensions and metrics (standard limits of 25 user-scoped, 50 event-scoped, 10 item-scoped dimensions and 50 custom metrics; avoid unnecessary high-cardinality dimensions; registering a predefined dimension such as page or transaction ID is not a best practice and uses quota)
  • Google Analytics Help, Create item-scoped custom dimensions (parameters in the items array; can’t be added to standard reports, use a free-form exploration)
  • Google Analytics Help, Archive custom dimensions and metrics (Editor or above; can’t be undone; explorations and reports using it stop loading until it is removed; an audience using it stops collecting users)
  • Google Analytics Help, What the value (not set) means ((not set) can show in the first 24 hours after registering a custom parameter)
  • Google Analytics Help, Monitor events in DebugView (Admin, Data display, DebugView; Tag Assistant or preview mode turns on debug mode; click an event to see its parameters; Current User Properties panel)
  • Google Analytics Help, Filter out developer traffic (excludes activity from developers using debug mode while DebugView keeps working) and Data filters (Testing and Active states; excluded data is never processed and the effect is permanent; filters apply from creation forward)
  • Google Analytics Help, Event collection limits (25 parameters per event; names up to 40 characters; values up to 100 characters, with page_title 300, page_referrer 420 and page_location 1,000; events, parameters and user properties over the limits are not logged) and Event naming rules (parameter names can’t begin with , firebase, ga_, google_ or gtag.)
  • Google Analytics Help, Customize detail reports (editors and administrators; Customize report, Dimensions, Add dimension, Apply, Save, Save changes to current report)
  • Google for Developers, Set up event parameters (GA4 Event tag, Event Parameters, Parameter Name and Value; parameters must be registered as custom dimensions or metrics to be available in reports)
  • Google Analytics Help, BigQuery Export schema (event_params and items.item_params hold each parameter as a key and value)

← back to the reading room