Analytics and Tracking

Event Parameter

Also called GA4 parameter

Extra detail sent with an event — which form, which product, what value — so a count becomes an explanation.

Quick facts: Event Parameter

Category
Analytics and Tracking
Also called
GA4 parameter
Level
Intermediate
Affects
Report detail, custom dimensions, audience building, data privacy
Where to see it
GA4 (DebugView, Admin, Custom definitions), Google Tag Manager
In this article4
  1. How an event parameter works
  2. Why event parameters matter
  3. Common mistakes with event parameters
  4. How to act on it

How an event parameter works

An event name says what happened. Parameters say which one, where, and what it was worth. A form_submit event with a parameter naming the form tells you not just that enquiries came in but which page earned them. A purchase event carries the value and the currency. Without parameters you have a tally; with them you have something you can act on.

Some parameters are attached for you. Every event arrives with the page location, page title, referrer and language already in place, which is why the standard reports work before anyone configures anything. Beyond that, parameters are whatever you choose to send, subject to limits on how many one event may carry and how long a name or value can be.

Why event parameters matter

They are the difference between a number and a decision. Knowing that enquiries rose is mildly interesting. Knowing that the rise came from one service page, one form and one traffic source is what tells you where to spend next month. That detail has to be attached at the moment the event fires; it cannot be reconstructed later.

There is a catch that trips up almost everyone new to GA4. A custom parameter you send does not appear in standard reports on its own. It has to be registered as a custom dimension or metric first, and registration only applies from that moment onwards — the parameter’s earlier values are not backfilled. Sending a parameter and forgetting to register it is the most common reason a client is told the data exists but cannot see it.

Common mistakes with event parameters

The serious one is sending personal information. Email addresses, phone numbers, names and full postal addresses must never be placed in a parameter, and neither must a URL that happens to contain them in its query string. This breaks Google’s terms, it cannot be cleaned out retrospectively with any confidence, and in a lead-generation business it is easy to do by accident when a form posts its values into the page address.

The everyday one is high cardinality: sending a parameter with an almost unique value each time, such as a timestamp or an order reference, and then registering it. Reports handle a limited number of distinct values gracefully and group the rest into an unhelpful catch-all row. Detail that is genuinely unique per transaction belongs in an export, not in a custom dimension.

How to act on it

For each event you plan, write down the question the parameter is meant to answer. If there is no question, do not send the parameter. If there is, name it in the same lower case and underscore style as your event names, keep the set of possible values small and stable, and register it before you expect to see it in a report.

Then verify what actually arrives in DebugView, including a check that no field contains anything identifying a person. Building that check into the tagging work is standard practice on any careful analytics and tracking implementation, and it is far cheaper than discovering the problem in an audit.

Do and do not

Do

  • Write the question each parameter is meant to answer
  • Register a custom parameter before expecting it in reports
  • Keep the set of possible values small and stable

Do not

  • Send emails, phone numbers or names in any parameter
  • Register a value that is unique on every event
  • Assume registration backfills the values already collected

Questions people ask about this

Why can I not see my custom parameter in GA4 reports?

Because sending a parameter and reporting on it are two separate steps. Until the parameter is registered as a custom dimension or custom metric in Admin, it is collected but not exposed in standard reports. Registration also works forward only, so values sent before you registered it will not appear. Check DebugView first to confirm the parameter is genuinely arriving, then register it.

Can I send a customer's email address as a parameter?

No. Sending anything that identifies a person — email, phone number, full name, exact address — breaks Google's terms and puts your property at risk. Watch out for indirect cases too: if a form submits its fields into the page URL, the automatically collected page location parameter will carry them. Fix the form so those values never reach the address bar.

How many parameters should one event carry?

Only as many as answer a real question. Each event has a limit on how many parameters it may carry, but hitting it is rarely the problem. The practical limit is human: a parameter nobody uses still has to be maintained, documented and checked after every site change. Send the ones that will change a decision and leave the rest out.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.