How to manually tag calls as conversions and send them to Google Ads

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

Learn how to use Nimbata workflows and manual call tagging to:

1. Run high-quality, human-approved conversions every day, and
2. Switch into a safe backup mode when Google or third-party tracking tools misbehave.

Use this guide when

Use this setup when:

• Google Ads is having temporary issues or delays with conversion processing.
• Your normal, automatic call conversion workflow is set up correctly, but you don’t trust the data yet (e.g. after a big change or suspected bug).
• You want to make sure only verified, high-quality calls are sent as conversions while things are unstable on the Google side.

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

What you need to prepare

Before you start, make sure:

• Google Ads integration is connected in Nimbata (Integrations > Google Ads).
• You have at least one Google Ads conversion created and mapped to 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).

[*Image*: Workflow list with a Google Ads workflow selected.]

This makes sure that, for the duration of the Google issue, only your manual-tag workflow sends conversions to Google Ads.

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'.

[*Image*: Workflow editor with Trigger set to 'User performs action']

This ensures the workflow fires only when you manually interact with a call (such as tagging it).

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

[*Image:* Simple filter with rule 'Tag = Conversion']

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

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

Now wire that condition into an actual Google Ads conversion send.

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.

[*Image:* Workflow 'Perform action' panel with Google Ads integration task selected.]

Save and Enable the workflow.

Step 5. Manually tag calls as Conversion

Once the workflow is active, you can start feeding it with manually approved calls.

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.

[*Image:* Call details screen with tag selector showing 'Conversion'.]

Each time you tag a call as Conversion:

• The User performs action trigger fires.
• The filter Tag = Conversion passes.
• The Send to Google Ads action runs and sends that call as a conversion to your mapped Google Ads conversion.

Nimbata uses the Google Ads API to upload these conversions; Google may take some time to process and display them in your Google Ads reports.

How GCLID affects this backup method

This workflow does not bypass Google’s technical requirements. 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 the call has no GCLID:

• Nimbata cannot associate it with a specific Google Ads click.
• Google Ads can’t attribute the conversion to a keyword/campaign and may not accept it as a standard click-based offline conversion.

Troubleshooting 2 common issues during Google problems

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 backup workflow is ideal when Google or Google Ads is unstable or under investigation, when you want precise control over which calls become conversions, or when you’re comfortable manually reviewing and tagging calls. When everything is stable again, you can re-enable your previous automatic workflow, or keep this manual-tagging approach for high-value campaigns only.

Updated on: 05/12/2025