Skip to main content

How to Fix Google Ads Integration After Multiple Accounts Update (CRM)

Overview: After Dazos updated the Google Ads integration to support multiple accounts, existing connections need re-authentication to sync with the new system. This guide will help you resolve persistent mapping errors and reauthorization loops.

Before You Begin

This issue specifically affects Google Ads integrations that were working before the Multiple Ads Account update. You may see a "Missing or Invalid Data Mapping" error or experience reauthorization loops, even when seeing a green checkmark.


Steps to Re-authenticate

  1. Manually revoke existing Dazos permissions: Log into your Google Ads account and navigate to Security > Third-party apps with account access. Find Dazos in the list and select Remove Access or Revoke.

  2. Return to Dazos CRM: Navigate to your Google Ads integration settings within Dazos.
    2.1. Click "Settings"
    ​

    2.2. Click "CRM Settings"
    ​

    2.3. Click "Integrations"
    ​

    2.4. Click "Google Ads Settings"
    ​

  3. Add your account using the new process: Click the "Enter a name to identify this Google Ads account" field, type a name, and then click Add.

  4. Complete Google authorization: Click Continue with Google and follow the standard authorization prompts.

  5. Verify the connection: Ensure the green checkmark appears and persists without prompting you for reauthorization again.

πŸ’‘ Tip: The new system supports multiple Google Ads accounts connected to a single Dazos instance simultaneously. If you have multiple accounts, each one needs to go through this re-authentication process once after the update.


Verification / Expected Result

Your Google Ads integration should now work properly with the new multiple accounts system. The mapping errors will clear, and you will not see repeated authorization prompts.


Troubleshooting / Common Errors

If you continue to experience mapping errors or reauthorization loops after following these steps, contact Dazos support for specialized technical assistance. Provide them with screenshots of the error, as the development team may need to review your specific account configuration on the backend.

Did this answer your question?