Google Ads integration

picoask uses the Google Ads API for reporting only. It issues read requests and nothing else. picoask does not create, edit, pause, remove or otherwise manage campaigns, ad groups, ads, keywords, budgets or bids, and the product exposes no control that would let a user do so.

1What it is for

Advertisers run their spend in Google Ads while their revenue, orders and customer records sit in their own database. picoask brings the two together so you can ask, in plain English, questions that need both — for example “which campaigns produced revenue last month rather than just clicks?” — and get an answer with the underlying figures shown.

picoask downloads your data through the Google Ads API using a Google Ads manager account link, and stores it in a warehouse schema belonging to your account.

2What picoask reads

Performance reporting, at account, campaign, ad group and ad level, for the date ranges you have connected:

picoask reports at account, campaign, ad group and ad level. picoask does not offer keyword-level performance reporting.

3Two further read-only requests

Besides the performance figures above, picoask makes two other read requests. Both are read-only and neither is aggregated into a performance report.

• Tracking configuration. picoask reads each ad's final URLs and tracking URL template (ad_group_ad.ad.final_urls, ad_group_ad.ad.tracking_url_template) so it can tell you when campaign tagging is inconsistent — for example a campaign whose UTM parameters do not match the rest of the account, which would otherwise silently break attribution.
• Click attribution. picoask reads click identifiers (click_view.gclid, click_view.gbraid, click_view.wbraid) together with the keyword that matched each click, so a conversion recorded in your own database can be traced back to the click that produced it. This is stored only on that click-to-conversion map. picoask does not aggregate, rank or report keyword performance.

4How it refreshes

• Google Ads data refreshes every 12 hours, so figures in picoask are never more than 24 hours behind Google Ads.
• The first sync backfills up to four years of history, subject to what your account holds.
• picoask does not present Google Ads data as real-time.

5Reported separately

picoask is a cross-channel tool, so it can show Google Ads alongside Meta Ads, Google Analytics 4 and your own data. Every figure stays attributable to the platform it came from, and Google Ads performance can always be viewed on its own — in the dashboard, in any answer, and in the underlying warehouse tables, which carry the source platform on every row.

6Connecting and disconnecting

• Connecting. You give picoask your 10-digit Google Ads Customer ID. picoask sends a manager-account link request; you approve it inside your own Google Ads account under Tools & Settings → Access and security → Managers. You never share a password, a developer token or an OAuth credential with picoask. Full setup guide →
• Disconnecting. Remove the connector in picoask, or remove picoask as a manager in your Google Ads account. Either stops all further reads immediately, and you retain sole control of the account. On request we delete the synced data within three business days.

7How your data is held

• Data is stored in a warehouse schema belonging to your account, never pooled with another customer's.
• All API traffic and all warehouse connections are encrypted in transit with TLS.
• Google Ads data is used only to answer your own questions inside your own account. It is never sold, shared with other customers, or used to train models.
• See the privacy policy for how picoask accesses, uses, stores and shares this data.