Measure newsletter signups as a sign_up event
Every newsletter subscription sends a GA4 sign_up event, so you can build a funnel from landing page visit to completed signup.
New submission on your newsletter signup form
Send a GA4 sign_up event with the signup method passed as a parameter
One-directional. A submission triggers the action — nothing is written back into your form.
Newsletter numbers usually live in the email tool and traffic numbers live in Google Analytics, so nobody can say which article actually earned the subscriber. Sending a sign_up event on submission puts both halves in one place.
Content teams reach for this when a subscriber target lands in the quarterly plan. With the event recorded, a funnel exploration runs from first visit to signup, and the method parameter separates the footer form from the popup and the dedicated landing page.
Setting it up
- 1
Publish the newsletter signup form in formformform. If the same form runs as a footer block, a popup and a standalone page, publish a copy per placement so each one can carry its own method value.
- 2
In Google Analytics, copy the Measurement ID from Admin → Data Streams and create a Measurement Protocol API secret for this Zap.
- 3
Build the Zap: formformform as the trigger app, New Submission as the event, and the published newsletter form as the source.
- 4
Add the Measurement Protocol action, paste the Measurement ID and API secret, and set the event name to sign_up — GA4 recognises it already, so it appears in reports without extra setup.
- 5
Set the method parameter by hand to a fixed value describing the placement, such as footer_form or article_popup. GA4 expects method on sign_up, and a constant is steadier than a typed answer.
- 6
Map "Topics You're Interested In" into a topics parameter, then register topics as an event-scoped custom dimension so you can see which subject pulls people in.
- 7
Add a second action that writes the subscriber into your email tool. Google Analytics gets the count; the email tool gets the address.
- 8
Subscribe once yourself, check Realtime for the sign_up event and its method value, then turn the Zap on.
What maps where
Using the Newsletter Signup Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Google Analytics |
|---|---|
| Email Address | Hashed into a non-identifying user_id; the plain address goes to your email tool in a separate step and never to Google Analytics |
| Topics You're Interested In | topics event parameter, registered as an event-scoped custom dimension |
| First Name | Deliberately left out of the event — Google Analytics must not receive names, so it stays in formformform for the welcome email |
Variations worth knowing
Add Zapier paths on "Topics You're Interested In" and send sign_up with a different content_group parameter for each. The subscriber total stays one number in GA4, and the parameter tells you whether the product newsletter or the research digest is doing the work.
With double opt-in, a submission is a request rather than a subscriber. Keep this event as sign_up with a method of pending, and let a second Zap triggered by your email tool's confirmation send a confirmed event. The gap between the two is your opt-in rate.
If something isn't arriving
Duplicates and bounces are filtered by the email tool, not by the Zap. Google Analytics counts the submission; the email tool counts the deliverable address. Add a Zapier filter that drops repeat submissions from the same hashed address if the two numbers need to agree.
GA4 collapses a dimension once it passes its cardinality limit. A multi-select answer sent as one joined string creates a new value for every combination people pick. Send the first selected topic, or map each option to a short fixed code before it goes into the parameter.
Frequently asked questions
Should I use sign_up or generate_lead for a newsletter?
sign_up. It is one of GA4's recommended events, so reports understand it without configuration, and it keeps subscriptions apart from sales enquiries. Save generate_lead for forms a sales team acts on, otherwise both end up inside the same conversion number.
Can I see which article the subscriber was reading?
Only where the event can be tied to that visitor's session. An event sent from Zapier carries the client ID you give it, so if you cannot supply the real one, read the page-level story from your on-page tag and use this event as the count.
Does the event include the subscriber's email address?
Not unless you map it in, and you should not. Google Analytics terms exclude personal data. Send a hashed value as user_id if you need to join sessions, and keep the address itself in formformform and your email tool.
Related automations
- Count demo requests as a generate_lead conversion
Each demo request fires a GA4 generate_lead event, so completions sit in your reports next to the campaigns that produced them.
- Log support requests with the issue category attached
Each support request sends a form_submit event carrying the issue category, so you can see which topics drive people off the docs.
- Record webinar registrations as a conversion event
Every webinar registration fires a GA4 sign_up event carrying the session name, so registrations can be attributed campaign by campaign.
- Track survey completions with the rating attached
Every product survey response sends a custom feedback_submitted event carrying the rating, so respondents become a segment you can analyse.
- Weigh quote requests by estimated deal size
Each quote request sends a generate_lead event with a value attached, so pages bringing bigger requests stand out from pages bringing many.
- Add webinar registrants to a remarketing list
Every webinar registration joins a Customer Match audience you can run follow-up campaigns to after the session.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free