Troubleshooting Google Ads integration issues

This guide covers the most common problems with Nimbata's Google Ads integration and how to resolve each one.

The integration shows "Inactive" status

An Inactive status in Nimbata's Google Ads integration is expected when the setup is complete but no conversions have been sent yet.

Step 1. Verify your integration settings

• Go to Integrations > Google Ads.
• Confirm that your Ads Account and Conversion Name are both selected.
• Confirm that Include Value is checked. Checking this removes the configuration warning shown in Nimbata.

Step 2. Confirm number swapping is working on your website

• Append ?gclid=test to your website URL and visit the page.
• Verify that your Nimbata tracking number swaps in.
• If it does not, resolve the DNI issue first before troubleshooting the integration.

Step 3. Wait for your first conversion

If both checks above pass, no further action is needed.

The Inactive status updates automatically once Google Ads receives its first conversion from Nimbata.

The conversion action cannot be found

Nimbata shows a "conversion not found" error when the conversion action you want to use is not visible to Nimbata, even though the Google Ads account is connected.

This usually happens when conversion actions were created, renamed, or modified after the account was first connected, leaving Nimbata working from an outdated snapshot.

To fix it:

• Go to Integrations > Google Ads.
• Click Disconnect to remove the Google Ads account.
• Reconnect the same account following the setup guide.
• After reconnecting, open the conversion drop-down menu; the updated list will now appear.

If the conversion still does not appear after reconnecting, confirm that:

• The Google account used to connect has sufficient permissions in Google Ads.
• The conversion action is active and eligible for use (not removed or paused).

Conversions are not appearing in Google Ads

If the integration is active and calls are being logged in Nimbata, but conversions are not showing up in Google Ads:

Check 1. Confirm the workflow is enabled

• Go to Workflows.
• Locate the workflow linked to your Google Ads integration.
• Confirm its status is Running, not paused or disabled.

Check 2. Check workflow filters

• Open the workflow and review any filter conditions.
• Make sure qualifying calls are not being excluded by a filter (e.g. minimum call duration, specific tag, or specific tracking number).

Check 3. Confirm auto-tagging is on in Google Ads

Nimbata relies on Google's gclid parameter to attribute calls to campaigns.

If auto-tagging is disabled in Google Ads, no gclid is appended to ad clicks and Nimbata cannot make the attribution.

• In Google Ads, go to Admin > Account settings > Auto-tagging.
• Confirm the auto-tagging checkbox is enabled.

Check 4. Allow for the 24-hour delay

Nimbata sends conversions to Google Ads with a 24-hour delay.

Conversions from today will not appear in Google Ads until the following day.

The Google Ads account disconnects or loses access

If Nimbata loses access to your Google Ads account, e.g. after a password change or permission update, the integration will stop sending conversions.

• Go to Integrations > Google Ads.
• Disconnect and reconnect the Google account.
• Ensure the Google account used has Editor or Admin access to the Google Ads account.

Still not resolved?

Submit a request via ? > Submit a request in your Nimbata dashboard. Include:

• A description of the issue and when it started.
• The name of the Google Ads conversion action you are trying to use.
• A screenshot of your integration settings from Integrations > Google Ads.
• Whether ?gclid=test produces a number swap on your website.

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

Detailed Guide: How to set up your first workflow

Detailed Guide: Google Ads enhanced conversions: how Nimbata handles them

Detailed Guide: Google Ads call extensions and call ads: how to track calls with Nimbata

Updated on: 05/05/2026