See who starts your survey, where they drop off and who finishes, in every tag you run
A survey is a short journey with a clear start, a series of questions and a finish line. Google Tag Manager is where most marketing and analytics teams already decide which tools see that kind of journey. Responsly connects the two: paste a container ID into the survey, and every start, question view and completed response becomes an event your GTM tags can act on.
That gives the team that owns acquisition and conversion the same signals for a survey that they already have for a landing page. Completion becomes a Google Ads conversion, the question where people quit shows up in a GA4 funnel, and people who started but did not finish can be reached again, all configured in GTM rather than in code.
Why GTM is the right home for survey tracking
Analytics and advertising tags change often. Keeping them in a GTM container means one person can add a GA4 event, a Google Ads conversion or a remarketing tag for the survey without waiting for a release, and the same container rules apply to the survey and to the rest of the site. If you only need page-level reporting, the Google Analytics integration is simpler; GTM is the better fit once more than one tool needs the survey’s signals.
Use cases
Google Ads conversions for completed lead forms
A B2B SaaS company runs a qualification survey behind its “Talk to sales” ads. responsly_form_submit fires a Google Ads conversion tag only after the response is saved, so Smart Bidding learns from finished forms, not from button clicks. Sales still reads the answers in Responsly or in the CRM, while the ad account only receives the conversion.
Finding the question where respondents quit
A product team sees fewer completions than starts on its onboarding survey. With responsly_step sent to GA4 and question_number as a parameter, a funnel exploration shows the share of respondents reaching each question. The drop at question 6 points to the one item worth rewriting; the feedback analytics view then shows how the change affects the answers themselves.
Bringing back people who started but did not finish
An e-commerce brand runs a post-purchase survey with a discount at the end. In GA4, an audience of visitors with responsly_form_start but no responsly_form_submit goes to Google Ads, or to Meta through the Meta Pixel integration, for a gentle reminder campaign. People who already finished are excluded automatically.
Comparing campaigns that send traffic to one survey
A services company promotes the same survey in a newsletter, on LinkedIn and in paid search, each link tagged with UTM parameters. GA4 attributes starts and completions to each source, so the team can see which channel brings people who actually finish. The same UTM values can be stored with every response through hidden variables, which keeps the answers and the campaign together in Responsly.
Quiz and contest promotions
A brand runs a prize quiz with questions drawn at random from a pool. Because question_id identifies each question regardless of the order a participant saw it in, the marketing team can count how many participants reached each question and how many completed the quiz per campaign, while prize decisions stay in Responsly where the scores are.
Consent-first measurement in regulated teams
A healthcare provider or an HR team needs consent before any analytics runs. The survey’s built-in cookie consent banner keeps the container from loading until the respondent accepts analytical cookies; events wait in the meantime and are delivered after acceptance. Teams that already manage consent with Cookiebot or a similar platform can run it from the container instead. See our GDPR-compliant survey guide for the wider picture.
What data moves, and what does not
| Event | When | Parameters |
|---|---|---|
responsly_form_start | The respondent starts the survey | form_id |
responsly_step | A question is shown for the first time in the session | form_id, question_number, question_id |
responsly_form_submit | The response has been saved | form_id |
- No answers, no personal data. The events describe progress, not content. Answers move through webhooks, Google Sheets or the CRM integrations instead.
- One step per question. Going back and forward again does not repeat
responsly_step, so funnels are not inflated. - Respondent order.
question_numberfollows the order the respondent saw;question_idstays the same when questions are shuffled. - Container or GA4. A
GTM-container ID loads the standard GTM container; aG-Measurement ID sends the same events straight to GA4. - Consent respected. With the consent banner on, nothing loads and nothing is sent until the respondent agrees to analytical cookies.
Setting it up
- Open your survey and add the GTM container ID in its integration settings.
- In GTM, create Custom Event triggers for the events you need and Data Layer Variables for their parameters.
- Attach the triggers to your GA4, Google Ads or other tags and publish the container.
- Check the events in GTM Preview on the live survey.
The click-by-click guide, with the exact labels and a troubleshooting table, is in the Google Tag Manager help article. Consent options, including Cookiebot through GTM, are covered in cookie consent banner for surveys.
Pair it with other integrations
GTM covers the signals about the survey journey. For page-level reporting without a container, use Google Analytics; for Meta audiences, add the Meta Pixel. To move the answers themselves into apps that have no dedicated integration, connect the survey to Zapier. If the survey runs on your own site, website surveys explains the widget and embed options, and the voice of the customer tools guide shows where survey data fits in a wider stack.
Start with one survey and one conversion: add the container, publish a trigger on responsly_form_submit, and completed responses start showing up in your reports as conversions.
