Skip to content

Track ActiveCampaign Form Submissions as Google Ads Conversions

If your ads bring visitors to an ActiveCampaign form, you need the click that started the visit to travel with the lead — so Google Ads can credit the right campaign, keyword, and location. Browser-only tracking often loses that link. A server-side flow captures the ad identifiers at submission, stores them on the contact record, and sends the conversion back when you choose: at submission or at a later revenue milestone.

Why browser tracking misses conversions

Browser-based methods depend on scripts running on the visitor's device. Ad blockers can stop the Google Tag, Safari's Intelligent Tracking Prevention can clear tracking cookies after a day or two, and a click on one device followed by a submission on another breaks the session link. Thank-you-page tracking adds further noise from refreshes, slow loads, and dropped connections. Sending the event from a server instead avoids the browser entirely: the identifiers captured with the form are delivered directly to Google, so blockers and short-lived cookies do not intervene. Captured evidence cited in the source attributes to this approach a 23% average increase in recorded conversions and a 10% reduction in cost per conversion, because more complete data improves automated bidding.

Choose your conversion trigger

Decide first when the conversion should count. Firing at submission measures lead creation and gives bidding data quickly. Waiting for a deal or won opportunity measures revenue quality, but requires the identifiers to survive in your CRM until that milestone. Both paths share the same capture step; they differ only in the trigger that sends the event.

Option 1: Fire at form submission

Pick a trigger such as an ActiveCampaign form submission, then pair it with a Google Ads conversion action. On landing, the tool records the Google Click ID (GCLID), GBRAID, WBRAID, UTM parameters, and User Agent. At submission it takes the submitted name, email, and phone, hashes them with SHA-256 as Google requires, and sends the combined payload server-side. The identity data plus click identifiers make matching back to the original ad click far more likely, without custom code for triggers, tags, or variables.

Option 2: Fire when the lead becomes a customer

Install the capture snippet in the site head, as you would a Google Analytics tag. In ActiveCampaign, create custom fields on the contact record first — GCLID, WBRAID, GBRAID, and User Agent — set each field type to Hidden Field, and apply the exact names and default values specified in the capture tool's help documentation. Then add those fields to the form in the builder; placing them just above the submit button is a convenient convention. When a visitor arrives from a Google ad, the tool stores the identifiers in the browser; when the form is submitted, it writes them into the hidden fields so they are saved with the submission. The data lands on the contact record automatically in ActiveCampaign, and can be pushed to Salesforce, HubSpot, Pipedrive, or another CRM via native integrations or Zapier. Later, when the lead reaches your milestone — a deal created or an opportunity won, for example — an automation tool such as Zapier or Make reads the stored identifiers from the CRM record and sends the conversion to Google Ads, using its visual mapping to match each stored value to the correct Google Ads field. If you also send the deal value, Google Ads can report revenue, not just lead counts.

What server-side tracking fixes

Server-side events are not just more complete; they are cleaner. Because the conversion fires only on a successful submission rather than a page load, counts align more closely with actual CRM leads, without double-counting from refreshes or losses from slow loads. Identity data also lets Google stitch a phone click to a later desktop submission, and survives the cookie deletion that breaks delayed conversions on Safari and iOS.

Three reports to run once tracking is live

Conversions by keyword shows which search terms produce submissions rather than only clicks, so budget can shift toward profitable terms. Conversion value by campaign separates high-value wins from low-value ones — for example, a premium treatment client versus a basic service client — instead of treating every lead as equal. Conversions by geography breaks results down to country, state, city, or postcode, revealing whether leads cluster in your service area; Location Bid Adjustments can then raise bids where paying customers originate and reduce them where clicks never convert.

Pre-launch checklist

Use this checklist before enabling bidding on the new data: confirm the four hidden fields exist on the contact record and appear in the form; submit a test form from a Google Ads click and verify the identifiers are stored on the contact; confirm the conversion arrives in Google Ads exactly once; check that hashed contact details are included; and, for delayed conversions, verify the identifiers persist in the CRM until the milestone fires. Accurate input is what makes both manual bid adjustments and automated bidding perform better — thank-you-page or browser-event data will not deliver the same result.