Connect Google Ads
Connecting Google Ads takes about two minutes and no keys. You sign in with Google and approve access, and SnowAnalytics starts reading your campaigns, ad groups and ads so their spend sits next to the revenue they brought in.
You connect Google Ads per site, so each site reads its own account.
Only workspace owners and admins can connect an ad account. Members and viewers can read the Ads pages but can't connect one. See Members.
Open the connect dialog
Open Integrations in the sidebar, find Google Ads in the Ads group and click Connect. Until an account is linked, the Ads pages show a connect screen with the same Connect button.
Check what SnowAnalytics can do
The dialog lists what SnowAnalytics can do (See campaigns and ads, See spend and conversions) and what it will never do (Create or edit ads, Change budgets or bids). Click Continue to Google.
Sign in and approve
Sign in with a Google account that can open the Google Ads account you want, and allow access. Google shows the Google Ads permission in its own words, which can sound broader than what SnowAnalytics does. SnowAnalytics only runs read-only report queries. Leave the Google Ads permission ticked: without it SnowAnalytics can read nothing, stores nothing and says permission to read the ad account wasn't granted.
Google may ask you to confirm with a passkey. It can also show Google hasn't verified this app while Google reviews SnowAnalytics. Choose Advanced, then continue to SnowAnalytics.
Choose the account
Google sends you back to Integrations. If your sign-in reaches exactly one ad account, SnowAnalytics picks it and the Google Ads card shows Connected. If it reaches several, a dialog lists them with their ID, currency and the manager account they come through. Click Choose next to the one this site should read.
Wait for the first read
SnowAnalytics reads your account on its next pass, so the first numbers can take up to an hour. Until then the sync chip on the Ads overview reads Google importing.
What SnowAnalytics reads
For every campaign, ad group and ad, SnowAnalytics reads each day's:
- Spend, impressions and clicks.
- Conversions and conversion value, as Google reports them.
- Status, so paused campaigns show as paused.
Meta's ad sets show as ad groups too, so Google and Meta read the same way.
SnowAnalytics also reads the click ID (gclid) of each ad click from the last 90 days,
up to seven days of them per pass. It uses them to match a visit to the ad group
and ad that brought it, so the full 90 days take about two days to arrive.
How often
SnowAnalytics reads every connected Google Ads account every three hours, which keeps it within Google's daily limit on API calls. The first pass reads the last 90 days. Each pass after that reads the last 30 days again, so changes Google makes to recent days show up in SnowAnalytics too. Days follow your Google Ads account's time zone.
The sync line at the right of the row under the title, on every Ads page, shows when each platform was last read, for example Google synced 12 min ago. It reads Google needs reconnecting when Google stopped accepting SnowAnalytics' access.
One ad account per site
SnowAnalytics reads one Google Ads account per site. If you sign in with a manager account, SnowAnalytics reads the client accounts under it.
Manager accounts can't be read on their own, so they aren't offered. To read another account later, click Manage on the Google Ads card and choose it. If the list says No Google Ads accounts reachable with this Google login, sign in again with a Google login that can open the account.
How visits are matched
For a visit to count for a campaign, SnowAnalytics has to know it came from an ad, and which campaign. It reads that from the address of the first page a visitor opens. The tracker records these parts of it:
| In the address | What SnowAnalytics does with it |
|---|---|
gclid, gbraid, wbraid | Marks a Google Ads visit. A gclid also names the campaign, ad group and ad, because SnowAnalytics reads click IDs from Google Ads. |
fbclid | Marks a Meta Ads visit. |
utm_source | Marks a Google Ads visit when it is google-ads, google_ads, googleads or adwords, or google with utm_medium set to cpc, ppc, paid or sem. Marks a Meta Ads visit when it is facebook, fb, instagram, ig, meta, meta-ads, meta_ads or facebook-ads. |
utm_campaign | Names the campaign when it holds the campaign's ID or its name. Capital letters don't matter. |
To find the campaign, SnowAnalytics tries the gclid first, then utm_campaign as an ID,
then utm_campaign as a name. Keep auto-tagging on in Google Ads: Google adds a
gclid to every ad link, and SnowAnalytics matches it to the click IDs it reads from
Google. Google reports a day's clicks the next day, so today's visits find their
campaign tomorrow.
gbraid and wbraid mark a visit as Google Ads, but SnowAnalytics can't read their
campaign from Google. Add utm_campaign to those links. For Meta, add
utm_campaign={{campaign.id}} to the ads' URL parameters. A link for a Meta campaign
looks like this:
https://example.com/pricing?utm_source=facebook&utm_medium=paid&utm_campaign=spring-saleVisits from ads that couldn't be tied to a campaign still count in the account's totals. What to do next flags it when they are a fifth or more of a platform's visits.
Reconnect or stop sharing
If Google stops accepting SnowAnalytics' access, for example because you revoked it, the Google Ads card on Integrations shows Reconnect needed and the sync chip on the Ads overview reads Google needs reconnecting. The Ads overview also shows a banner, Google Ads access expired, with the date and a Reconnect button. Spend after that date is missing. Click Reconnect and sign in again.
To stop SnowAnalytics reading your account, click Manage on the Google Ads card, then Disconnect. SnowAnalytics deletes its access tokens and revokes its access at Google too. The figures SnowAnalytics already read stay in your reports. You can also remove SnowAnalytics from your Google Account's third-party connections.
If Google says the account can't be read, the card shows why in place of the expiry date: for example that the login needs 2-Step Verification, that the account is cancelled or suspended, or that it can't be opened through its manager. Fix that in Google, then Reconnect or choose the account again.