Send Conversions to Google Ads from Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Add to Google Ads workflow action sends conversion events back to Google Ads using the click ID captured on the contact (GCLID, GBRAID, or WBRAID). Use it to feed offline conversions like form submissions, calls, and chat replies into Google's optimization engine.

The Add to Google Ads action sends conversion events from a Sparkforge workflow back into your Google Ads account. It is built for offline conversions: the form fill, the call, the chat reply, or the booking that happens after someone clicks an ad. Tying those events back to the original click gives Google the signal it needs to optimize the campaign.

Sparkforge does this by reading the click ID stored on the contact - GCLID for Search, GBRAID or WBRAID for iOS and Android app campaigns. If those IDs are not on the contact record, the conversion cannot be attributed.

Prerequisite: the conversion action must already exist in Google Ads before this workflow action can use it.

Why use this action

  • Offline conversion tracking for events that happen after the click.
  • Direct sync to Google Ads - no Zapier, no manual CSV uploads.
  • Better campaign optimization because Google sees the real downstream conversions.
  • Click ID coverage for GCLID, GBRAID, and WBRAID.
  • Flexible triggers: form submissions, link clicks, page views, calls, chat replies.
  • Lead-quality attribution tied to specific campaigns and ad groups.

Set it up

Connect Google Ads

Go to Settings > Integrations in your sub-account, choose Google, and authenticate. Make sure you link the right Google Ads account if you manage several. Without this connection the workflow action will not run.

Inside Google Ads, you must already have at least one conversion action created. Sparkforge pulls the list of conversions directly from Google Ads at setup time. If none exist, the dropdown in the workflow will be empty.

Step 1: Open the workflow builder

Log in to the sub-account and go to Automations > Workflows. Create a new workflow or open an existing one.

Step 2: Add a relevant trigger

Pick a trigger that maps to the conversion you care about: Form Submitted, Appointment Booked, Trigger Link Clicked, Customer Replied, Order Form Submission, Survey Submission, Call Status for number-pool calls, or chat-widget replies.

Step 3: Add the Add to Google Ads action

Click + after the trigger, search for Add to Google Ads, and select it. The configuration panel opens on the right.

Step 4: Configure the action

Three things must be true in Google Ads first:

  1. The conversion action exists in your Google Ads account.
  2. You copy the conversion name exactly - capitalization, spacing, and punctuation must match.
  3. Your ad URLs are passing GCLID (Search) or GBRAID/WBRAID (iOS/Android app) so Sparkforge can capture the click ID on the contact.

Then fill in the action:

  • Action Name: something descriptive like "Submit Lead Conversion."
  • Conversion: pick or paste the exact Google Ads conversion name.
  • Currency: the currency the conversion value should be reported in.
  • Conversion Value: the value of the conversion in that currency (for example, $100 per dental checkup lead).
  • Custom Mapping: toggle on if you need to manually map GCLID, GBRAID, or WBRAID to specific custom fields.

If your conversion is set to One Per Click, GCLID is required - GBRAID and WBRAID only work with Many Per Click.

Step 5: Save and publish

Click Save Action, then publish the workflow.

Step 6: Watch execution logs

Open the workflow's Execution Logs tab and look for the Add to Google Ads action. You will see one of two outcomes:

  • Executed - the conversion was sent to Google Ads.
  • Skipped - something is wrong (missing click ID, mismatched conversion name, or wrong conversion type).

Common workflow recipes

Form, order, or survey submission

  1. Create a workflow with the Form Submitted, Order Form Submission, or Survey Submission trigger.
  2. Add filters that scope to the right form, order form, or survey, then save the trigger.
  3. Add the Add to Google Ads action and select the matching conversion from Google.
  4. Set the currency and conversion value.
  5. Save and publish.

Number pool calling

  1. Create a workflow with the Call Status trigger.
  2. Filter on Call Direction = Incoming and Pool Number = your tracked pool.
  3. Make sure the pool-number script is installed in the funnel or website header.
  4. Add the Add to Google Ads action with the matching conversion.
  5. Set currency and value, then save and publish.

Chat widget

  1. Create a workflow with the Customer Replied trigger and filter Reply Channel = Chat Widget.
  2. Add the Add to Google Ads action with the matching conversion.
  3. Set currency and value, then save and publish.

Frequently Asked Questions

How do I know the conversion is firing?
Open the workflow's history or execution logs and look for the Add to Google Ads action. "Executed" means it sent successfully. "Skipped" means a click ID or conversion name was wrong.
How long until conversions show up in Google Ads?
It takes roughly 5 minutes after a contact arrives with a valid UTM source and GCLID, GBRAID, or WBRAID for the conversion to appear in Google Ads and in workflow triggers.
What triggers does this action support?
Form Submission, Order Purchase, Number Pool Calling, Survey Submission, and Chat Widget.
What does "Skipped" mean in the logs?
Either the contact has no valid GCLID, GBRAID, or WBRAID, or the conversion name in the action does not match exactly what is in Google Ads. Both must be correct for the event to fire.
What is the difference between GCLID, GBRAID, and WBRAID?
GCLID is the standard web click ID. GBRAID and WBRAID are privacy-focused click IDs used mostly on iOS. GBRAID and WBRAID only work with "Many Per Click" conversions; "One Per Click" conversions require GCLID.
Do I need Google Tag Manager for this to work?
No. This action does not require GTM. GTM can still be useful if you want to track additional client-side events alongside this server-side conversion.

Was this article helpful?