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

Manual call conversion governance in Nimbata (regular use + Google issues backup)

This guide explains how to use Nimbata workflows and manual call tagging to control which calls are sent to Google Ads as conversions. This approach is useful both for everyday quality control and as a fallback when automatic conversion tracking is unreliable.

Use this guide when

Use this setup when:

• Google Ads is experiencing delays or issues with conversion processing
• Your automatic call conversion workflow is enabled, but you want additional validation before sending conversions
• You want to manually approve which calls are sent to Google Ads during periods of instability

Nimbata sends call conversions to Google Ads via workflows using the Google Ads API.

What you need to prepare

Before you start, make sure:

• The Google Ads integration is connected in Nimbata (Integrations > Google Ads)
• At least one Google Ads conversion action exists and is mapped in Nimbata

Step 1. Disable or delete your current Google Ads workflow in Nimbata

If you currently have a workflow that automatically sends call conversions to Google Ads (e.g. based on call duration or caller country), disable or delete it so it doesn’t conflict with manual tagging.

1. In Nimbata, go to Workflows.
2. Locate your existing Google Ads call conversion workflow.
3. Disable it or delete it (depending on your preference).

This ensures that only your manual-tag workflow sends conversions to Google Ads while this setup is active.

Step 2. Create a new workflow triggered by 'User performs action'

You will now create a backup workflow that runs only when you perform an action on a call.

1. In Nimbata, go to Workflows and click + Add.
2. Give the workflow a descriptive name (e.g. 'Google backup - manual conversions').
3. Under Trigger, select 'User performs action'.

This ensures the workflow runs only when you manually perform an action on a call, such as adding a tag.

Step 3. Add a filter to run only when Tag = Conversion

Next, you’ll restrict the workflow so that it only fires for calls you mark as conversions.

1. In the workflow editor, click the + icon under the trigger.
2. Select Add filter.
3. Choose Simple filter.
4. Add a rule: Field: Tag, Condition: equals, Value: Conversion

Now the workflow will only process calls that have the Conversion tag.

Step 4. Add the action 'Send to Google Ads'

Now connect this condition to a Google Ads conversion action.

1. Under the filter, click the + icon.
2. Select Perform action.
3. Click + Add task.
4. Under Integrations, select Google Ads.
5. Choose the correct Google Ads configuration (conversion name) that should receive these calls.

Save and Enable the workflow.

Step 5. Manually tag calls as Conversion

Once the workflow is enabled, you can begin manually approving calls to be sent as conversions.

1. Go to Activity > Calls.
2. Open each call you want to review.
3. Listen to the call recording if needed.
4. When you decide it is a valid lead, add the Conversion tag to the call.

When you tag a call with Conversion, the workflow runs, checks that the tag condition is met, and sends the call to the selected Google Ads conversion action.

How GCLID affects this backup method

This workflow follows Google Ads’ standard technical requirements for offline and API conversions. For Google Ads to accept an offline or API call conversion:

• The original click needs a GCLID (Google Click ID).
• The GCLID must be present in the URL when the visitor lands on your site.

Nimbata captures the GCLID from the landing page session and associates it with the call. When the workflow sends a conversion, it includes this GCLID so Google Ads can match the conversion back to the click.

If a call does not have a GCLID:

• Nimbata cannot associate it with a specific Google Ads click
• Google Ads may not attribute or accept the conversion as a click-based offline conversion

Troubleshooting common issues during Google Ads disruptions

1. Conversions still not appearing in Google Ads

Check:

• Is the call tagged as Conversion?
• Is the workflow enabled?
• Does the call have a GCLID? In Nimbata, check the call’s Click ID column or call details.
• Is Google Ads itself delayed? Offline/ API conversions are not always visible immediately; Google can take hours to process them.

2. Calls have no GCLID even though they come from Google Ads

The most common causes are:

• Auto-tagging disabled in Google Ads.
• Landing page redirects or intermediate tools that strip the gclid parameter.
• Third-party tracking templates (for fraud detection, link tracking, etc.) that don’t preserve query parameters like gclid when forwarding the user to the final URL.

In practice:

• If you use a third-party tracking template, test it with Google Ads’ 'Test' feature and confirm that the final URL still includes ?gclid=...
• If the GCLID disappears, you’ll need to fix or remove the template so Nimbata can receive it.

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: 16/02/2026