Manual Google Ads Call Conversions: How to tag and send calls from Nimbata

While Nimbata usually handles conversions automatically, there are times when you need more control. Whether you're dealing with Google Ads API delays or simply want a human to vet a lead before it hits your ad reports, manual tagging is your best friend. This guide covers how to set up a workflow that only sends a conversion to Google Ads when you manually approve it.

When to use this setup:

• Quality Control: You only want to pay for qualified leads, not every 30-second call.
• Google Sync Issues: If Google is experiencing processing delays, this manual push acts as a reliable fallback.
• Validation: You want to listen to the recording first to ensure the lead is legitimate.

Prerequisites

Before diving in, ensure:

1. Your Google Ads integration is connected (Integrations > Google Ads).
2. You have at least one Conversion Action mapped in Nimbata.

Step 1. Pause your automatic workflows. To avoid double-counting, you need to stop Nimbata from sending conversions automatically (e.g., based on duration).

1. Go to Workflows.
2. Locate any existing Google Ads conversion workflows.
3. Disable them by toggling the green button off and/or delete them.

Step 2. Create the workflow. You need to build a workflow that only fires when you take action.

1. Click '+ Create', select 'From Scratch', and name it something clear, like 'Google Backup - Manual Approval'.
2. Under Trigger Enrollment, select 'User updates property'.

Step 3. Filter for the 'Conversion' tag. We don't want the workflow to fire for every action (like adding a note). We only want it to fire when you apply a specific tag.

1. Click the '+' plus icon under the trigger enrollment menu and select 'Add Filter'.
2. Select the 'Tag' filter, and set it to 'Conversion'.

Step 4. Set the Google Ads action

1. Click the '+' plus icon under the filter and select Perform action.
2. Select Google Ads from the list of integrations.
3. Choose the Conversion Name that matches your Google Ads account.
4. Save and Enable the workflow.

Step 5. Start approving leads. Now for the easy part. When you're reviewing your activity:

1. Go to Activity > Calls.
2. Review the call (listen to the recording or check the transcript).
3. If it’s a valid conversion, simply click on the 'Tags' field > Call Status > and add the tag 'Conversion' to the call.

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

A Quick Word on GCLIDs

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

• If a call has no GCLID, it means the visitor likely didn't come from an ad, or their browser stripped the tracking code.
• Pro Tip: If you see "No GCLID" for calls that should be from ads, check your Google Ads account to ensure Auto-tagging is turned on.

Troubleshooting

• Conversions not showing? Google can take up to 24 hours to process API uploads. Check back tomorrow!
• Workflow not firing? Double-check that your tag spelling matches exactly (e.g., 'Conversion' vs 'conversion').

This manual-tagging workflow is useful when you want tighter control over which calls are sent to Google Ads, during periods of instability, or for high-value campaigns. When automatic tracking is reliable again, you can switch back to your previous workflow or continue using this approach selectively.

Updated on: 11/03/2026