Digitanalytics Ads Insights
An internal Digitanalytics tool that connects an AI assistant to the Google Ads accounts you already have access to — so campaign analysis and account audits happen in conversation, with no manual exports.
What connects to what
AI assistant
Claude, by Anthropic — where you ask the questions.
MCP server, running locally
Google's open-source Model Context Protocol server for the Google Ads API, on your own computer.
Google Ads API
Signed in with your Google account. Only the accounts that address already has access to.
What Digitanalytics Ads Insights is
A bridge between an AI assistant and the Google Ads API — nothing more. No dashboard to log into, no account of ours holding your data.
An internal consulting tool
Digitanalytics consultants use it on their own Google Ads accounts, and on client accounts those clients have given them access to. It is not a product sold or distributed to the public.
Built on Google's open-source MCP server
The connection to Google Ads goes through the open-source Model Context Protocol (MCP) server that Google publishes for the Google Ads API. The server runs locally, on the user’s own computer.
Read-only by design
The tool reads account data. It cannot create, modify or delete anything in Google Ads — no campaigns, no budgets, no bids, no settings.
What it is used for
Campaign performance analysis and Google Ads account audits, asked as questions instead of assembled from manual exports.
Spend breakdown
Where the budget actually goes across campaigns, ad groups and networks, and how that split has moved over time.
Search terms
The queries that triggered the ads, read at scale — including the ones that should never have matched.
Products
Shopping and product-level performance, so the catalogue can be read against the spend it attracts.
Impression share
How much of the available auction volume the account is capturing, and what it is losing to budget or rank.
Bidding strategies
Which strategy each campaign runs, with its targets, so mismatches between strategy and goal surface quickly.
Conversion setup
How conversion actions are configured — what counts, what is primary, and what the bidding is optimising towards.
How it works
Four steps, all of them on the user's own machine and under their own Google identity.
The MCP server runs locally
The consultant starts Google's open-source MCP server for the Google Ads API on their own computer. There is no Digitanalytics server in the path.
They sign in with their Google account
Authentication goes through Google OAuth. The consent screen shows exactly which permissions are requested before anything is granted.
Only their own accounts become visible
The tool sees the Google Ads accounts that Google address already has access to — and nothing else. It grants no new access.
The assistant answers from live account data
When a question is asked, the assistant requests the figures it needs through the local server, reads them, and answers. Each request is driven by the user.
Permissions requested
Two OAuth scopes, shown on the Google consent screen before you approve anything. You can withdraw them at any time.
Google Ads API
Reads the structure and performance data of the Google Ads accounts your Google address can already access — campaigns, ad groups, keywords, search terms, products, conversions and budgets. Read access only: the tool cannot create, change or delete anything in Google Ads.
https://www.googleapis.com/auth/adwordsGoogle Cloud
Used for authentication and for the Google Cloud project the Google Ads API access is attached to. It is not used to read, change or store anything else in your Google Cloud environment.
https://www.googleapis.com/auth/cloud-platformRevoking access
You can remove Digitanalytics Ads Insights's access to your Google account at any time from Google Account permissions. Once revoked, the tool can no longer read any account data.
Who it is for
Digitanalytics consultants
The people who run the audits. They use the tool on the Google Ads accounts they own or manage directly.
Client accounts, with access granted
Accounts belonging to clients who have given a Digitanalytics consultant access in Google Ads. The tool adds no access of its own — it only reads what the consultant could already open in the Google Ads interface.
How data is handled
The short version is below. The privacy policy is the full one.
Read on request
Google Ads data is read when the user asks a question, and passed to the AI assistant they are using so it can answer. Nothing is pulled on a schedule.
Not stored on our servers
Digitanalytics does not store your Google Ads data on its servers. OAuth credentials stay on the user’s own computer.
Never sold
The data is not sold, not used for advertising, and not shared with third parties beyond the AI provider the user has chosen.
Google API Services User Data Policy
Digitanalytics Ads Insights' use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Read the policy →Policies and contact
Privacy policy
What Google data the tool accesses, how it is used, where it is stored, and who it is shared with.
Read the privacy policy →Terms of service
The conditions the tool is provided under, and what is expected of the people who use it.
Read the terms →Contact
Questions about the tool, the permissions it requests, or a data deletion request.
amine.s@digitanalytics.ioDigitanalytics Ads Insights is an independent tool built by Digitanalytics. It is not affiliated with, endorsed by, or sponsored by Google. Google Ads, Google Cloud and Google are trademarks of Google LLC.
Frequently asked questions
Want this run on your account?
Our consultants use Digitanalytics Ads Insights as part of a Google Ads audit. Ask for one.