> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/destinations/destinations-catalog/google/migration-to-data-manager-api.md). # Migration to Data Manager API {% hint style="info" %} We will progressively update all of our existing Google destinations to use this new API, including: * Google Enhanced Conversions * Google Customer Match * Google Conversion Adjustments * Google Enhanced Conversions for Leads Some new destinations (e.g. Google Store Sales) require this API from the start. {% endhint %} ## Why this migration? * **Get ahead of the change**: Google will progressively restrict access to the legacy API. The current version of the Google Customer Match destination is expected to be deprecated in 2027. * **Enhanced security**: the Data Manager API supports data encryption, * **More complete measurement**: sending IP addresses and session attributes is available to all users of the new API * **Greater stability**: quotas are now managed per project rather than per developer token, reducing the risk of blocking. * **Access to new Google features**: upcoming destinations, such as *Google Store Sales* will be reserved for this new API. ## Connect your Google account to the Data Manager API {% hint style="danger" icon="triangle-exclamation" %} **Do not remove your existing Google Ads permissions or credential.** Only add the new permissions requested below, as removing your current access will break your existing connections. {% endhint %} Google is replacing the Google Ads API with the Data Manager API. To keep your Google connections running smoothly, add a new Google credential in Commanders Act. {% hint style="info" %} **This updates your existing credential: it is never removed.** Your current connections stay active throughout the process. Estimated time: less than 2 minutes. {% endhint %} ## Steps for migration 1. Go to Connector Credentials 2. Select Google Ads 3. Sign in with Google 4. Select your Google Ad account(s) ## Before you start: check your access rights You'll need two levels of access to complete this: * **In Commanders Act**: access to `Administration > Connector Credentials`. If you don't see this menu, ask your Commanders Act administrator to grant you access or to perform this update on your behalf. * **In Google**: sufficient rights on the Google Ads account to grant API access (typically Admin access on the Google Ads account, or on the Google Workspace/Google account used to sign in). If you're not sure who manages this on your side, check with whoever originally set up your Google Ads connection. {% hint style="warning" %} If you sign in with a Google account that doesn't have the right permissions, the consent screen may not show all the expected permissions, or the connection may fail. In that case, ask your Google Ads administrator to complete this step instead. {% endhint %} ## Step-by-step tutorial ### Step 1 — Go to Connector Credentials In Commanders Act, go to `Administration > Connector Credentials`, then click **Update connector credentials** in the top right corner. ### Step 2 — Select Google Ads In the connector list, select **GoogleAds**. ### Step 3 — Sign in with Google A Google window opens asking you to sign in and grant access to CommandersAct. Review the summary, then click **Continue**. Google may then show the detailed list of permissions requested. {% hint style="warning" %} **Accept all the permissions shown**, even if some look broader than what you expect to use. Do not uncheck or skip any permission on this screen as declining one can break part of your Google connection later. {% endhint %}
### Step 4 — Select your Google Ads account Once access is granted, select the Google Ads account(s) you want to link, then click **Save**. If several Google Ads accounts are already connected to your Commanders Act account, select all the accounts you want to update: this will update the scope for all the accounts you select.
### Step 5 — You're done Your Google credential is now updated for the Data Manager API. Your existing connections and destinations continue to run without any further action on your side. ## FAQ **Will this delete my current Google connection?** No. This action updates your existing credential in place. Nothing is deleted, and your current connections keep running during the update. **What happens if I don't do this?** Google is phasing out the Google Ads API in favor of the Data Manager API. Without this update, your Google Ads connections may stop working once Google fully retires the old API. In addition, some future Google destinations will require the Data Manager API to run — you won't be able to use them until you complete this upgrade. **Why do I keep both my Google Ads and Data Manager permissions?** Google hasn't migrated every feature to the Data Manager API yet — some parts of the Google Ads connection still rely on the older API. Keeping both active ensures nothing breaks while Google completes this transition on their end. **I only see some permissions, not "Data Manager" by name. Is that normal?** Yes. Google's consent screen may not always list a permission named exactly "Data Manager". What matters is that you accept every permission shown on the screen, without unchecking any of them. **Can several people in my company do this?** Yes, this update can be repeated per user/account. See Before you start for the access rights required on both sides. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.commandersact.com/features/destinations/destinations-catalog/google/migration-to-data-manager-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.