The subscribe event
A subscribe event records when a visitor subscribes — to a newsletter, an updates list, or a paid plan. Unlike many e-commerce events, subscribe is not in GA4's standard recommended-events list for the web, so it is typically implemented as a custom event with consistent parameters. It marks an ongoing-relationship commitment distinct from a one-off purchase.
What this means
Subscribing is opting into an ongoing relationship — a newsletter, a content list, or a recurring paid plan. GA4 publishes a fixed set of recommended events, and a general web 'subscribe' is not among the standard recommended names, so it is usually implemented as a custom event. Define a stable event name and parameters (such as a subscription type and, for paid plans, currency and value) and apply them consistently.
It captures a commitment that is recurring by nature, unlike a single purchase.
Modelling subscriptions
Because it is a custom event, governance matters: pick one event name and one parameter schema so the data stays clean, following GA4's event-naming guidance. Distinguish free list opt-ins from paid subscriptions, since they mean very different things. For paid plans, you can attach an estimated value with currency. Keep the subscriber's email and contact details out of analytics entirely.
- Typically a custom event, not a standard recommended one
- Separate free opt-ins from paid subscriptions
- Record type and optional value, never contact details
How it appears in analytics and logs
A subscribe event means a visitor opted into an ongoing relationship. Read it separately from purchase: a subscription implies recurring value, not a single transaction.
Diagnostic use case
Mark newsletter or plan subscriptions as a conversion, distinguishing recurring commitments from one-time purchases or single leads.
What WebmasterID can help detect
WebmasterID can record subscribe events first-party as a custom event, so subscription conversions are measurable without storing subscriber contact data.
Common mistakes
- Assuming subscribe is a built-in GA4 recommended event.
- Mixing free opt-ins and paid plans under one label.
- Storing subscriber email in the event.
Privacy and accuracy notes
A subscribe event should record that a subscription happened and its type, not the email address or contact details. This is educational, not legal advice.
Related pages
- The sign_up event
sign_up is a GA4 recommended event that fires when a visitor creates an account. It carries a method parameter naming the registration mechanism, such as 'Google', 'email', or 'Apple'. It is a key activation event for products with accounts, marking the move from anonymous visitor to registered user — distinct from logging in, which returning users do repeatedly.
- The generate_lead event
generate_lead is a GA4 recommended event that fires when a visitor expresses interest in a product or service — typically a form submission for a quote, demo, or contact. It can carry currency and value to express an estimated lead worth. It is the core conversion event for lead-generation sites, but a raw lead count says nothing about lead quality.
- Event naming conventions
An event naming convention is the agreed rule for what events are called: the case, the separators, and the vocabulary. It sounds trivial but it is the difference between clean analytics and a fragmented mess where signup, sign_up, and SignUp count as three things. This page covers the conventions that work, reserved names to avoid, and why a documented taxonomy matters more than any single rule.
- Events documentation
Define custom subscribe events cleanly.
Sources and verification notes
- Google — GA4 recommended events (standard list)Used to confirm 'subscribe' is not a standard web recommended event; treat as custom.
- Google — GA4 events naming guidance
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.