> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Did My Google Ads Call or Signal Conversion Stop Ingesting Data?

> Renaming a conversion action in Google Ads breaks the match to Invoca's naming convention — revert the name to fix it.

**Applies to:** Google Ads

## Symptoms

* The Invoca call conversion action was previously ingesting data.
* A name change was made to the conversion action.
* Data stopped flowing after that update.

## Cause

The Google Ads integration looks for a specific naming convention, and once the conversion name changes, it no longer finds a match — so data stops being sent.

## Resolution

Change the conversion name back to Invoca's naming convention in Google Ads, then re-save the configuration in Invoca to ensure everything is synced properly.

Invoca's naming convention is `<Signal Name> (call extensions)` for Google Call Extensions Signal conversions, and `<Signal Name> (web page calls)` for pooling calls.

## Where to go next

* [Google Ads: Troubleshooting & FAQs](/s/article/google-ads-troubleshooting-faqs)
* [Google Ads: Data Mapping](/s/article/google-ads-data-mapping)