Articles on: Workflows

Google Ads call conversions: how to manually tag and send calls

Before you start, make sure your Google Ads integration is connected under Integrations > Google Ads, and that you have at least one Conversion Action mapped in Nimbata. Need help? See: Google Ads integration: how to set it up in Nimbata.


Nimbata usually handles conversions automatically, but sometimes you need more control.

This guide shows you how to build a workflow that only sends a conversion to Google Ads when you manually approve a call by tagging it.

Use this approach when you want to vet leads before they reach your ad reports, or as a fallback when Google Ads API delays occur.


Step 1. Disable any existing automatic Google Ads conversion workflows


  • Go to Workflows.
  • Locate any existing Google Ads conversion workflows.
  • Toggle them off or delete them.


This prevents double-counting.



Step 2. Create a new workflow triggered by a property update


  • Click + Create.
  • Select From Scratch.
  • Give the workflow a clear name, such as Google Backup - Manual Approval.
  • Under Trigger Enrollment, select User updates property.



Step 3. Add a Tag filter for "Conversion"


  • Click the + icon under the trigger block.
  • Select Add filter.
  • Select the Tag filter.
  • Set the value to Conversion.
  • Click OK.


This ensures the workflow only fires when you manually apply the Conversion tag.



Step 4. Add the Google Ads action


  • Click the + icon under the filter.
  • Select Perform action.
  • Select Google Ads from the integrations list.
  • Choose the Conversion Name that matches your Google Ads account.
  • Click Save, then Enable the workflow.



Step 5. Approve conversions manually by tagging calls


  • Go to Activity > Calls.
  • Review the call: Listen to the recording or read the transcript.
  • If the call is a valid conversion, click the Tags field.
  • Select Call Status > Conversion.



The moment you apply the tag, Nimbata pushes the data to Google Ads via the API.


🎉 Your manual approval workflow is live. Only calls you tag as Conversion will be sent to Google Ads.


A note on GCLIDs


For Google to accept a conversion, the call must have a GCLID (Google Click ID).

A call without a GCLID means the visitor likely didn't come from an ad, or their browser stripped the tracking parameter.

If you see calls with no GCLID that should be from ads, check that Auto-tagging is enabled in your Google Ads account.


Troubleshooting


Conversions not showing in Google Ads? Google can take up to 24 hours to process API uploads. Check back the next day.

Workflow not firing? Confirm that your tag spelling matches exactly, e.g. Conversion not conversion.


Detailed Guide: Template: how to create a Google Ads Call Conversion workflow

Detailed Guide: Google Ads integration: how to set it up in Nimbata

Detailed Guide: Multiple conversions setup: Google Ads, Meta Ads, and Microsoft Ads


Updated on: 14/04/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!