Skip to content

Send Paperform submissions to Google Ads as server-side conversions

If your Paperform is where enquiries arrive, the useful question is not whether someone clicked an ad, but whether that click produced a real lead. This guide explains how to pass each completed submission back to Google Ads from the server, so blocked browser tags do not erase the result.

Why browser tracking misses Paperform conversions

Browser tracking depends on scripts running in the visitor's browser. Ad blockers can prevent the Google tag loading at all. Privacy features in browsers such as Safari can remove tracking cookies within a day or two, breaking the link between a click on Monday and a submission on Friday. A person may also click on a phone and submit later on a laptop, which browser storage cannot connect.

Server-side tracking changes the route. Instead of hoping a browser event fires, your system sends a direct message to Google after a genuine submission, carrying the lead details and the original click identifier. Because the message does not depend on the browser, blockers and cookie expiry have nothing to interrupt.

What server-side tracking can improve

Google's own data indicates that server-side tracking tends to produce a 23% average increase in total recorded conversions and a 10% cut in cost per conversion. Those are averages, not a promise for any individual account. The mechanism is straightforward: more complete conversion data gives Google's bidding systems a clearer picture of which clicks lead to valuable enquiries.

Option 1: Send the conversion when the form is submitted

Choose a trigger for a new Paperform submission and an action that sends a conversion to Google Ads. The sending tool should collect the lead's name, email and phone, hash those fields with SHA-256 as Google requires, and include the Google Click ID and other available signals. That combination helps Google match the submission to the campaign, ad and keyword that drove the visit.

Use this route when a submitted form is itself the conversion you want to optimise for, and when you want feedback quickly without building custom tag logic.

Option 2: Send the conversion when the lead becomes a customer

If a lead is only valuable once it becomes a customer, capture the click identifier at submission and store it for later.

  • Add the capture snippet to your website, then add a hidden field to the Paperform form and give it a prefill key such as gclid, so the click identifier can be written into the form.
  • When a visitor arrives from a Google Ads click, the identifier is stored in the browser and written into that hidden field at submission time.
  • On submission, the identifier is captured with the other fields the person entered and pushed to your CRM through a Paperform integration or a tool such as Zapier or Make, where it sits on the contact record.
  • When the contact reaches your chosen milestone, such as a deal being created or a purchase completing, use a connector such as Zapier or Make to send the conversion, and any value from the CRM record, back to Google Ads.

Use this route when downstream revenue matters more than raw lead volume, because it lets you optimise campaigns for customers rather than enquiries.

Cleaner counts and reports worth running

Server-side sending also avoids a common counting error. Counting thank-you page views or submit-button clicks can log a conversion even when a submission fails validation, and a corrected resubmission then counts twice. Logging only completed submissions keeps the total closer to the number of real leads.

Once conversions are flowing, three reports become practical. Conversions by keyword show which search terms produce enquiries rather than only impressions and clicks, helping you shift budget to terms that earn their keep. Conversion value by campaign, using the value stored on the CRM contact or deal, shows which campaigns produce higher-value customers, since not every customer is worth the same. Conversions by geography, down to country, state, city or postcode, shows whether leads come from the areas you actually serve, and can inform Location Bid Adjustments that bid more where results are strong and less where they are not.

Before you go live: a short checklist

Decide first whether your conversion is a submitted lead or a paying customer, then set up the matching route above. Check that the click identifier is present on test submissions, that lead fields are hashed correctly, and that each completed submission produces exactly one conversion in Google Ads. Before committing to any paid plan, confirm the current trial length, pricing and cancellation terms directly with the provider you choose.

Choosing when to send the conversion
SituationRecommended timingWhat to store
Form submission is the goalOn submissionName, email, phone hashed with SHA-256, plus Google Click ID
Customer revenue is the goalAt CRM milestone such as deal or purchaseGoogle Click ID on the CRM contact, plus conversion value

Captured source evidence; outcomes vary by account.

Frequently asked questions

Why not rely on a thank-you page or a browser form event?

Browser-based setups can lose a substantial share of events when tags are blocked or cookies expire, and they cannot reliably link a click on one device to a later form submission on another. Sending the event from the server with the lead details and click identifier avoids those browser dependencies.

When should the conversion be sent to Google Ads?

You can send it immediately on submission, or store the click identifier on the CRM contact and send it later when the lead reaches a milestone such as becoming a customer. The choice depends on whether you want Google Ads optimised for leads or for downstream revenue.

What lead data travels with a server-side conversion?

The captured evidence describes name, email and phone being hashed with SHA-256 as required by Google, alongside the Google Click ID and other signals, so Google can match the conversion to the campaign, ad and keyword that generated the click.