Connect Zunoform to Google Analytics via Zapier
This is not a one-click native integration. Zunoform posts every completed response to a Zapier catch hook, and your Zap does the rest — so there is no Google Analytics button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook connection with field mapping you control in Zapier.
Sends an event to Google Analytics when a form is completed, so conversions show up in the same reports as the rest of your funnel.
The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Webhooks by Zapier requires a paid Zapier plan; destination account requirements and task limits also apply.
This is a server-side event fired by Zapier after the response is stored, not a browser event from the respondent's session. It will not carry their session, campaign attribution, or device data, and the timing lags the actual submission. For attribution you want a client-side event on your thank-you page instead.
Example workflow
Count completed forms without confusing setup with measurement
A server-side completion event can help count submissions in GA4, but it does not automatically inherit the browser's campaign or session. Decide whether you need a submission count or marketing attribution before choosing this workflow.
Prepare your Google Analytics account
Choose the correct GA4 property and a measurement-event action suitable for its stream. An action that creates a key-event definition configures reporting; it does not send one respondent's completion. Keep secrets in the integration configuration, never in public form fields.
Four steps, start to finish
Start with a published Zunoform form, a Zapier plan that includes webhooks, and access to the destination account. Some destinations require additional permissions or setup.
Create a Zap with a Catch Hook trigger
In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event. Zapier generates a URL for you and shows it on the next screen. Copy it.
Paste the URL on the Zapier card in Zunoform
Open your form in the Zunoform builder, go to the Integrations tab, and paste the URL on the Zapier card. We only accept an https address on zapier.com, so a typo is rejected rather than silently failing later.
Submit a test response so Zapier learns the shape
Publish the form and fill it in once yourself. Zapier's trigger step will pick that submission up as sample data — without it, the field list in the next step is empty and there is nothing to map.
Map your fields to Google Analytics
Add an action step and choose Google Analytics. Connect your account, then pick the action that sends a measurement event to your property. Zapier's action list changes over time, so choose from what it shows you rather than hunting for an exact name. Drag your form's answers into the fields, test the Zap, and turn it on.
Suggested field mapping
Use this example to plan your form. Select the actual fields from your captured test response and the action available in your account; these are mapping suggestions, not a preconfigured Zap.
- Fixed event name
- Destination: Measurement event name
- Example: zunoform_submission. Keep naming consistent across tests.
- Form ID
- Destination: Non-personal event parameter
- Use an identifier instead of a title that might contain personal information.
- Required measurement identifiers
- Destination: Action-specific identity fields
- Configure these deliberately; do not invent browser session context.
- Test or production destination
- Destination: GA4 property configuration
- Keep test submissions out of production totals where possible.
What Zapier receives
The payload includes formId, formName, responseId, submittedAt, status, answers and metadata. Answers are keyed by field ID, not by question label; inspect a test response to identify the answer you want. Multi-part answers can contain nested values, and uploads contain file references rather than binary attachments. Replacing a question can change its ID, so retest mappings after editing the form.
Delivery uses a background queue with retries for failed webhook requests. A successful hook does not confirm the later Google Analytics action succeeded. Check Zap history, and use responseId in a lookup or a processed-response log when duplicate processing would matter. Earlier responses are not automatically replayed when you connect the hook.
Test before sharing your form
Send one test completion and confirm it reaches the intended reporting destination. Check that a browser event and the Zap are not both counting the same submission. Do not interpret a successful HTTP response alone as a verified report entry.
If the result is missing or wrong
If totals or acquisition reports look wrong, inspect duplicate events and missing session identifiers separately. Never send email addresses, phone numbers or free-text form answers to Analytics as event parameters.
Check the current Google Analytics actions in Zapier and Zapier’s webhook setup and plan requirements before configuring your account. Action availability and permissions depend on your connected account.
Questions people ask
Will this attribute conversions to the right campaign?
Generally not. The event comes from Zapier's servers rather than the visitor's browser, so session and campaign context are missing unless you collect and pass identifiers yourself. Use this for counting completions, not for attribution.
What is the better way to track form conversions?
For attribution, implement completion tracking in a browser flow where you can reliably detect a successful submission and preserve the required session context. An iframe load or submit-button click is not proof of completion. Use the server-side workflow for its intended measurement purpose and test for duplicate events.
Is this a native Zunoform integration?
No. Zunoform sends each completed response to your Zapier catch hook; you configure the destination and field mapping in Zapier. The Zunoform connection is included on Free, but Webhooks by Zapier requires a paid Zapier plan. Native options include Google Sheets and Zoho CRM on Free, with Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Form notification emails on Free require your own SMTP configuration; platform-sent form emails require Pro or Business.
Ready when you are
Better forms.
Better data.
Start with a conversation, a document or a single page.
Unlimited forms and 500 responses per month on Free.
No card required.
- No credit card
- Unlimited forms
- 500 responses / month