Google Ads: Troubleshooting

I see a 2-step verification error message when fetching data from Google Ads

The Customer with ID [ID] has a policy to enforce 2-Step Verification, but the user is not enrolled error message appears when the user who has authorized the connection to Google Ads requires two-factor authentication.

To resolve this issue, the user who authorized the connection must log in to Google Ads and activate two-factor authentication for their account and any sub-accounts.

Accounts are missing from the data I have fetched from Google Ads

Adverity synchronizes accounts daily around midnight UTC. This sycnhronization has lower priority than manual and scheduled fetches. As a result, if you perform or schedule a high number of fetches, accounts will not be synchronized until after these fetches are complete. Additionally, if you add an account after the daily synchronization and then fetch data, the newly added account will not appear in the data. It will only be included after the next synchronization.

To resolve this issue, manually synchronize the metadata for the authorization you are using to fetch data. For more information, see Synchronizing metadata.

Customer statuses are missing in the authorization Customers

In the authorization Customers for Google Ads, customers have the status Active or Inactive. If a customer’s status is missing, this is due to Google Ads’s configuration and cannot be changed.

Fetches encounter CUSTOMER_NOT_ENABLED error in Google Ads

When fetching data from Google Ads, some customer accounts may return a CUSTOMER_NOT_ENABLED error, indicating that these accounts are disabled. Adverity now handles this by skipping the disabled accounts, logging a warning, and continuing to fetch data for the remaining enabled customer accounts. This ensures that the overall fetch operation does not fail due to a single disabled account.