Track Tally Forms Submissions as Google Ads Conversions
Tally Forms can collect a lead in seconds, but Google Ads only learns from that lead if the conversion is sent back reliably. Browser-only methods such as thank-you-page visits and Google Tag Manager events can miss a meaningful share of conversions because of ad blockers, browser privacy limits, and cross-device journeys. This guide shows two server-side approaches: send the conversion when the Tally form is submitted, or hold it until the lead reaches a CRM milestone such as a new deal or a closed-won opportunity.
Why server-side tracking matters for Tally Forms
A Tally form submission is a moment you can observe directly, but the browser is a fragile place to record it. If an ad blocker stops the Google Tag from loading, the submission never reaches Google Ads. If a browser's privacy controls shorten the tracking window, a form filled out days after the ad click can go uncounted. And if the click happens on a work laptop while the form is completed later on a phone, the two events may never be joined. The captured evidence describes these gaps as capable of missing up to 30% of actual conversions.
Server-side tracking moves the record out of the browser. The conversion data travels from your form tool or CRM to Google's servers, so ad blockers and browser privacy settings have less opportunity to interfere. The captured evidence references figures of a 23% average increase in total recorded conversions and a 10% reduction in cost per conversion when server-side tracking is used. Treat those as dated reference points, not a guarantee for your account.
Choose when the conversion should fire
The right setup depends on what you want Google Ads to optimize toward. Use this decision checklist before building anything:
- If a Tally form submission is the meaningful lead event for your business, send the conversion at submit time. This is the simpler path and works well with a purpose-built server-side conversion tool.
- If a form submission is only the beginning of a sales process, capture the Google Ads identifiers with the lead and send the conversion later, when the lead becomes a paying customer or reaches another CRM milestone.
- If you need campaign-level revenue reporting, include the conversion value from the deal or opportunity in your CRM.
- If you rely on automated bidding, make sure the conversion data is accurate; smart bidding learns from the quality of the signals you send.
A recruiting firm illustrates the difference. A campaign for legal recruitment and a campaign for hospitality recruitment may both produce form submissions, but the legal client is likely more profitable. Sending a conversion value from the CRM lets you compare revenue by campaign instead of treating every lead as equal.
Option 1: Send the conversion when the Tally form is submitted
When the form submission itself is the conversion, a server-side conversion tool can handle the handoff without custom JavaScript. The captured workflow describes a visual builder where you choose a trigger, such as a Tally Forms submission on your site, and an action, such as sending a conversion to Google Ads.
On arrival, the tool captures the Google Click ID (GCLID), GBRAID, WBRAID, UTM parameters, User Agent, and other information about how the visitor reached the site. When the visitor submits the Tally form, the tool takes the name, email, phone, and other form details, secures them with SHA-256 as Google requires, combines them with the captured identifiers, and sends the result to Google Ads. The combination gives Google more signals for matching the conversion back to the original ad click.
This route avoids writing custom JavaScript in Google Tag Manager to listen for the submit event, push contact details into the DataLayer, hash them with SHA-256, and post to Google's API. The trade-off is that the conversion fires at lead stage, not at customer stage.
Option 2: Send the conversion when a lead becomes a customer
If Tally feeds a CRM such as Salesforce, HubSpot, or Pipedrive, you can capture the Google Ads identifiers with the form submission and trigger the conversion later. The four hidden fields to add to the Tally form are GCLID, WBRAID, GBRAID, and User Agent.
The sequence has four stages:
- Install the tracking snippet on your website and add the hidden fields to the Tally form. The snippet is provided when you create an account, and step-by-step documentation covers adding the hidden fields.
- When a visitor clicks a Google Ads ad and lands on your site, the snippet captures the identifiers Google Ads needs for a server-side conversion and stores them in the visitor's browser. On form submission, those values are written into the hidden fields and captured with the rest of the lead data.
- Send the submission to your CRM alongside the lead's name, email, phone number, and other form answers. Tally's Connect feature supports native integrations for Pipedrive, HubSpot, Salesforce, ActiveCampaign, and most other major CRMs, with Zapier and Make as fallbacks.
- When the lead reaches the milestone you care about, such as a new deal being created or an opportunity marked closed won, use that event to send the conversion to Google Ads. Zapier and Make can connect to most CRMs and provide a mapping interface for matching the captured GCLID, GBRAID, WBRAID, User Agent, and other values to the right Google Ads fields.
Field and control map for the Tally setup
Use this map to keep the implementation consistent between the form, the CRM, and Google Ads.
- GCLID: the Google Click ID captured from the ad click and stored in a Tally hidden field.
- WBRAID: a Google Ads identifier captured alongside GCLID and stored in a hidden field.
- GBRAID: a Google Ads identifier captured alongside GCLID and stored in a hidden field.
- User Agent: browser and device context captured with the submission and stored in a hidden field.
- Name, email, phone: lead details collected by the Tally form and sent to the CRM.
- Conversion trigger: either the Tally form submission or a CRM milestone such as deal created or closed won.
- Conversion value: optional deal or opportunity value from the CRM, used for revenue reporting.
The exact form-control contract for this page is supplied in the protected module form-controls-contract and should be treated as the authoritative field specification.
What accurate server-side conversions improve
Accurate conversion data affects more than a dashboard. It changes how Google Ads reports performance, how automated bidding behaves, and how you can re-engage visitors.
Reporting: With reliable conversion tracking, you can review conversions, conversion rate, cost per conversion, return on ad spend, and other metrics, then break them down by campaign, ad group, keyword, ad, country, and other dimensions. That helps you decide where budget is producing leads.
Automated bidding: The two bidding modes ask you for different inputs. Manual bidding takes a ceiling on cost per click, so Google stops at your number regardless of who is searching. Smart bidding takes a target cost per conversion and lets the system weigh each auction against the likelihood of a conversion. That second mode is only as good as the conversion signal behind it. If your Tally form conversions are undercounted, the system is learning from a partial picture and may spend on searches that never produce a form fill. Sending complete server-side conversions, ideally with a value attached, gives the bidding model a truer target.
Retargeting: Accurate conversion data supports remarketing lists that include people who visited but did not convert. You can adjust search bids for those audiences, run Display campaigns aimed at them, or serve YouTube ads to them. The captured evidence describes Display and YouTube as inexpensive ways to re-engage visitors who arrived through search ads.
Three reports to review after conversion tracking is in place
Once conversions are flowing, these three report views help turn the data into budget decisions.
Conversions by keyword: Most advertisers bid on multiple keywords across campaigns. This view shows which keywords produce conversions rather than only impressions and clicks, so you can identify profitable terms and adjust budget.
Conversion value by campaign: If you send deal value from the CRM, you can compare revenue by campaign. The recruiting example applies here: a legal recruitment client and a hospitality recruitment client may both convert, but their commission value can differ substantially. Revenue reporting makes that difference visible.
Conversions by geography: Businesses that earn locally, such as driving schools, music schools, dance studios, or martial arts schools, can review conversions by country, state, city, or postcode. If clicks come from areas too far away to become customers, location bid adjustments let you bid more aggressively in productive postcodes and pull back where results are weak.
Keep the conversion signal server-side
Whether you fire the conversion at Tally form submission or wait for a CRM milestone, the important choice is to send it server-side. Browser-only thank-you-page tracking and Google Tag Manager events can leave gaps that affect reporting and bidding. A server-side setup gives Google Ads a more complete view of which clicks become leads and customers, and it gives you a clearer basis for budget decisions.
Frequently asked questions
Which hidden fields should I add to a Tally form for Google Ads tracking?
Add GCLID, WBRAID, GBRAID, and User Agent as hidden fields. These carry the Google Ads identifiers and browser context needed for a server-side conversion.
Should the conversion fire when the Tally form is submitted or later in the CRM?
Fire at submission if the form fill is the meaningful lead event. Wait for a CRM milestone if you want Google Ads to optimize toward paying customers or deal value. The first option is simpler; the second gives a later-stage signal.
Why not just track a thank-you page visit?
Thank-you-page tracking depends on the browser and can miss conversions when ad blockers prevent the Google Tag from loading, when privacy features limit tracking, or when the ad click and form submission happen on different devices. Server-side tracking sends the conversion from your form tool or CRM to Google's servers instead.
Can Tally send form data to my CRM?
Tally's Connect feature supports native integrations for Pipedrive, HubSpot, Salesforce, ActiveCampaign, and most other major CRMs. Zapier and Make can cover other systems.