AI Process Audit
Map out your process
ServicesAI agentsAutomationCustom softwareIntegrationsGrowth & marketingAll servicesHow we workSectorsAboutAI Process AuditMap out your process

Google Ads integration

The Diginesso Google Ads integration

The Diginesso Google Ads integration will work with the Google Ads API for four things: reporting on an account’s results, making the campaign changes the account holder asks for, keyword research, and reporting enquiries from this website to Diginesso’s own Google Ads account. Below, each use is explained with the data it needs and the reason.

See what it does Privacy policy for Google data

Status: being set up. No account is connected yet, and this page describes what the integration will do.

Diginesso · Google Ads APIOne permission
  1. Reportingcost, clicks, impressions, conversions
    Reads
  2. Campaign managementonly the changes you ask for
    Writes
  3. Keyword researchideas and search volumes
    Reads
  4. Conversion uploadenquiries from this site, to Diginesso’s own account
    Writes

Scope https://www.googleapis.com/auth/adwords

When you connect your account

What it does in your Google Ads account.

Three of the four uses work in a Google Ads account that its holder connects. There Diginesso acts for the account holder and for nobody else. Conversion upload works on other data and has its own section further down.

Go to conversion upload

Reporting

Reads

Reads the results of the Google Ads accounts you connect: cost, clicks, impressions and conversions, per campaign, ad group, keyword and ad, in the account’s own currency and time zone. It turns them into a report for you.

Why it needs the data: A report on your advertising has to start from your own account’s figures, and Google Ads only hands those to an app you have authorised.

Data it uses

  • customer ID and account name
  • the account’s currency and time zone
  • how campaigns, ad groups, keywords and ads fit together
  • campaigns and their settings
  • ad groups
  • keywords, negative keywords included
  • ads
  • budgets
  • cost, clicks and impressions
  • conversion actions, with their counts and values

Campaign management

WritesOnly when you ask for it

Creates and changes campaigns, budgets, ad groups, keywords and ads in your account, such as raising a budget or adding negative keywords. Every change is one you asked for.

Why it needs the data: To make a change it first reads how the account is set up, so it changes the right campaign. Then it writes the change through the Google Ads API. Both steps need access to your account.

Data it uses

  • customer ID and account name
  • the account’s currency and time zone
  • how campaigns, ad groups, keywords and ads fit together
  • campaigns and their settings
  • ad groups
  • keywords, negative keywords included
  • ads
  • budgets

Keyword research

Reads

Asks Google’s Keyword Planner for keyword ideas and monthly search volumes, for the languages and locations you choose, with bid ranges in your account’s currency. You use them to plan new campaigns and keywords.

Why it needs the data: Google offers Keyword Planner data only through a Google Ads account, so the request runs under your authorisation. What comes back is Google’s aggregated search data. It says nothing about you or your customers.

Data it uses

  • customer ID and account name
  • the account’s currency and time zone
  • keyword ideas and search volumes from Keyword Planner

Changes only on your instruction. The integration never changes anything in your account on its own initiative. It makes a change only when you have asked for that change, and it reads what it is about to change first.

Read and write

What it reads, and what it changes.

This is all the Google Ads data the three account uses touch, fetched through the accounts you connect and through nothing else.

Reads

To report and to research

  • customer ID and account name
  • the account’s currency and time zone
  • how campaigns, ad groups, keywords and ads fit together
  • campaigns and their settings
  • ad groups
  • keywords, negative keywords included
  • ads
  • budgets
  • cost, clicks and impressions
  • conversion actions, with their counts and values
  • keyword ideas and search volumes from Keyword Planner
Changes

Only when you ask for it

  • campaigns and their settings
  • ad groups
  • keywords, negative keywords included
  • ads
  • budgets

What it does not touch

The integration asks Google for one permission, https://www.googleapis.com/auth/adwords, and for nothing else. It has no access to:

  • Gmail
  • Google Drive
  • Google Calendar
  • Google Contacts
  • your Google Account name, email address and photo, because there is no Sign in with Google
  • any other Google service or data
Access

How you give access, and how you take it back.

Nothing is connected unless you start it, and you can end it whenever you want.

You connect it

The connection starts on Google’s own sign-in page, not on this site. Google shows the name Diginesso and the one permission it asks for, access to your Google Ads accounts. You approve or refuse it there. Diginesso never sees your Google password.

While it is connected

Diginesso keeps the access Google grants for as long as the connection is active, and uses it only for the features you use. How that access is stored and protected is set out in the privacy policy.

You take it back

Remove Diginesso in your Google Account at any time, and the access stops working at once. Or write to info@diginesso.com and I revoke it at Google for you, which I also do when our work together ends. Either way, what Diginesso still holds from your account is deleted within 30 days. The one exception is copies in database backups, which disappear as those backups are replaced, after 90 days at the latest.

myaccount.google.com/linkedapps
Google user data

What happens to your Google Ads data.

Diginesso’s use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In practice:

  • It is used only to provide the features you use in your own account.
  • It is passed on only where a feature you use needs that or where the law requires it. A merger or sale of the business is the one other case, and then only with your explicit consent beforehand.
  • Nobody reads it, except with your explicit consent, for security purposes, to comply with the law, or in aggregated and anonymised form for internal operations.
  • It is never used to serve or target ads, for Diginesso or for anyone else, remarketing and interest-based ads included. Managing your own campaigns on your instruction is the feature itself.
  • It is not sold.
  • It is not used to train or improve general AI or machine learning models.
Read the Google user data section Full privacy policy
The fourth use works differently

Conversion upload: about visitors of this site.

When someone reaches diginesso.com through a Google ad and later sends the contact form, the integration will report that enquiry to Diginesso’s own Google Ads account as a conversion. It will show me which ads lead to real enquiries. A site without cookies has no other way of knowing.

This use does not touch anyone’s connected account. Once the Google Ads connection is set up and active, it will send data about visitors of diginesso.com to Diginesso’s own Google Ads account, and Diginesso is the controller of that data. It will run on the same single permission, granted by Diginesso for its own account.

Where the click ID comes fromWhen your visit starts with a click on a Google ad, Google adds a click ID, the gclid, to the link. Whichever page of this site you land on, the site keeps it in your browser’s session storage under diginesso.first-touch until you close the tab. It sets no cookie and loads no Google ad tag.
When it leaves your deviceOnly when you send the contact form yourself. The click ID then travels with your enquiry to Diginesso and is stored with it.
Who receives itGoogle, a US company, which may process it outside the EU. That starts only once the Google Ads connection is set up and active. Until then the click ID stays with your enquiry in my own records. Only an enquiry that arrived with a click ID can be reported, and the integration will send it from Diginesso’s server.
Legal basisLegitimate interest under Article 6(1)(f) GDPR: knowing which ads bring real enquiries. You can object at any time by writing to info@diginesso.com, and your enquiry is then left out of the upload.
Sent

What goes to Google

  • the click ID (gclid) your visit arrived with gclid
  • which conversion it counts as, such as an enquiry conversion_action
  • the date and time of the conversion conversion_date_time
  • a value for the conversion, only if I set one conversion_value
Never sent

What never goes to Google

  • the record number of your enquiry
  • your name
  • your email address
  • your company
  • your message
  • my notes on your enquiry
  • the language you read the site in
  • the page you sent the form from
  • the page your visit started on
  • the site that referred you
  • utm_source
  • utm_medium
  • utm_campaign
  • your conversation with Digi, if you had one
  • hashed contact details (enhanced conversions stay off)
  • your IP address

Whether an enquiry counts as a conversion, and when, follows from its stage and dates in my own records. Only the resulting conversion action and time will go to Google.

The privacy policy describes this in its part about this website. The cookie page describes the entry in your browser.

Privacy policyCookie page
Technical detail

Every API call, per use.

For anyone who wants to check: these are the Google Ads API methods the integration will call. All of them run on the one scope, https://www.googleapis.com/auth/adwords.

Reporting

  • CustomerService.ListAccessibleCustomers
  • GoogleAdsService.Search
  • GoogleAdsService.SearchStream

Campaign management

  • GoogleAdsService.Search
  • CampaignBudgetService.MutateCampaignBudgets
  • CampaignService.MutateCampaigns
  • CampaignCriterionService.MutateCampaignCriteria
  • AdGroupService.MutateAdGroups
  • AdGroupCriterionService.MutateAdGroupCriteria
  • AdGroupAdService.MutateAdGroupAds
  • AdService.MutateAds

Keyword research

  • KeywordPlanIdeaService.GenerateKeywordIdeas
  • KeywordPlanIdeaService.GenerateKeywordHistoricalMetrics

Conversion upload

  • GoogleAdsService.Search
  • ConversionUploadService.UploadClickConversions
Questions

Questions you may have.

Is the integration running yet?
Not yet. It is being set up, and no Google Ads account has been connected so far. This page describes what it will do. If that ever changes, this page and the privacy policy are updated before the change goes in.
Can Diginesso read my email or my files?
No. The integration asks Google for one permission, https://www.googleapis.com/auth/adwords, which covers Google Ads and nothing else. Gmail, Drive, Calendar and Contacts are out of its reach.
Will it change my campaigns by itself?
No. It changes something only when you have asked for that change. Reporting and keyword research only read.
Is my Google Ads data used to train AI?
No. It is not used to train or improve general AI or machine learning models. It is not sold either, and it is never used to show or target advertising, for me or for anyone else. Changing your own campaigns, when you ask, is the feature itself.
Do I have to give you my Google password?
No. You sign in on Google’s own page, and Google gives Diginesso limited access. You withdraw it in your Google Account whenever you want.

Questions about the integration?

Diginesso is a one-person AI and automation studio in Tuscany, Italy, run by Wesley Beerendonk. I am building this integration myself, and questions about it come straight to me.

Write to info@diginesso.com

The same address is the support contact on Google’s consent screen.