Squizzie connects to five Google services through a single account connection. You set up one Google Cloud project, connect once, and then configure each service individually. One login, multiple data sources.
Why One Connection?
Rather than asking you to set up separate credentials for each Google service, Squizzie uses a single OAuth connection that all five services share. This means you only authenticate once, and adding a new Google service later is just a matter of toggling it on and selecting a property — no new credentials, no new logins.
What Each Service Gives You
Here’s the quick overview of what each Google service brings into your Squizzie reports:
- Google Analytics 4 (GA4) — Website traffic and conversion data. Sessions, users, page views, bounce rate, conversion rate, traffic sources. This tells you how people find your site and what they do when they get there.
- Google Search Console — Organic search performance. The actual search terms people use to find you, how often you appear in search results, your click-through rate, and your average ranking position. This is data GA4 can’t give you.
- Google Business Profile — Local search visibility. Profile views on Maps and Search, phone calls, direction requests, website clicks, search keywords, and Google reviews. Essential if you have a physical location or serve a local area.
- PageSpeed Insights — Site performance and health. Performance scores, Core Web Vitals, and actionable recommendations split into things you can fix yourself, things that need a developer, and things that aren’t your fault (third-party scripts). Includes an adjusted score that accounts for external scripts dragging down your numbers.
- Google Sheets — Data export for deeper analysis. Export any report to a formatted spreadsheet, either on-demand or automatically on a schedule. Running logs build trend data over time. Great for sharing with your team or feeding into AI tools for analysis.
Before You Start
You’ll need a Google Cloud project with the right APIs enabled. This is a one-time setup that takes about 10 minutes. If you already have a Google Cloud project for other purposes, you can use the same one — just make sure you enable all the APIs listed below in that same project.
Important: All APIs must be enabled in the same Google Cloud project. If they’re spread across different projects, Squizzie won’t be able to use the same credentials for all services.
Setting Up Your Google Cloud Project
Step 1: Create a Project
- Go to the Google Cloud Console
- Click the project dropdown at the top of the page (it might say “Select a project” or show your current project name)
- Click New Project
- Give it a name — your business name works well (e.g., “Acme Store”)
- Click Create
- Wait a moment for the project to be created, then make sure it’s selected in the dropdown
Take note of the project number shown on the project dashboard. If you run into errors later, this number helps confirm you’re working in the right project.
Step 2: Enable the APIs
You need to enable each API individually. They’re all free to use within generous quotas, but Google requires you to explicitly switch each one on.
- In the Google Cloud Console, go to APIs & Services > Library (from the left sidebar, or use the search bar)
- Search for and enable each of the following APIs:
For Google Analytics:
- Search for Google Analytics Data API and click Enable
- Warning: Do NOT enable “Google Analytics API” (without “Data” in the name) — that’s the old Universal Analytics API and won’t work with GA4
For Search Console:
- Search for Google Search Console API and click Enable
For Business Profile:
- Search for My Business Account Management API and click Enable
- Search for My Business Business Information API and click Enable
- Search for Business Profile Performance API and click Enable
For Google Sheets:
- Search for Google Sheets API and click Enable
For PageSpeed Insights (optional):
- Search for PageSpeed Insights API and click Enable
- This is optional because PageSpeed works without it, but enabling it increases your daily quota from 25 requests to 25,000
Step 3: Configure the OAuth Consent Screen
Before you can create credentials, Google needs you to set up a consent screen. This is the screen your users (in this case, you) see when authorising the connection.
- Go to APIs & Services > OAuth consent screen
- Choose External as the user type (unless you have a Google Workspace organisation, in which case Internal works too)
- Click Create
- Fill in the required fields:
– App name — your business name
– User support email — your email address
– Developer contact information — your email address again
- Click Save and Continue
- On the Scopes screen, click Add or remove scopes and add the following:
– https://www.googleapis.com/auth/analytics.readonly
– https://www.googleapis.com/auth/webmasters.readonly
– https://www.googleapis.com/auth/business.manage
– https://www.googleapis.com/auth/spreadsheets
- Click Update, then Save and Continue
- On the Test users screen, add your own Google email address
- Click Save and Continue, then Back to Dashboard
Note: While your app is in “Testing” status, only the test users you’ve added can authorise the connection. This is fine for your own use. If you later want to allow other team members to connect, add their email addresses to the test users list.
Step 4: Create OAuth Credentials
- Go to APIs & Services > Credentials
- Click + Create Credentials at the top
- Select OAuth client ID
- For Application type, choose Web application
- Give it a name (e.g., “Squizzie”)
- Under Authorized redirect URIs, click + Add URI
- Enter your redirect URI. You’ll find this in Squizzie’s settings — it looks like:
https://yoursite.com/wp-admin/admin.php?page=tracksies-squizzie&tab=integrations&google_callback=1
(Replace yoursite.com with your actual domain)
- Click Create
- A dialog will show your Client ID and Client Secret — copy both of these. You can also download them as JSON for safekeeping.
Connecting Squizzie to Google
Now that your Google Cloud project is ready, connecting Squizzie takes about a minute.
- In your WordPress admin, go to Tracksies > Squizzie > Settings
- Click the Integrations tab
- Paste your Client ID and Client Secret into the fields provided
- Click Connect Google Account
- You’ll be redirected to Google’s authorisation page — sign in with the Google account that has access to your Analytics, Search Console, and Business Profile data
- Review the permissions and click Allow
- You’ll be redirected back to Squizzie with a success message
Once connected, you’ll see the status change to “Connected” and configuration options will appear for each individual service.
Configuring Individual Services
After connecting, you’ll need to tell each service which property or account to use:
- GA4: Enter your GA4 Property ID (the numeric ID, not the “G-” measurement ID). You can find this in your Google Analytics admin under Property Settings.
- Search Console: Select your site from the dropdown. Squizzie will list all sites verified in your Search Console account.
- Business Profile: Select your account, then your business location.
- PageSpeed: Your site URL is pre-filled. Optionally add a PageSpeed API key for higher quota.
- Sheets: No additional configuration needed — it’s ready to go once connected.
Google Analytics Integration
Once your Google account is connected and your GA4 property is configured, the squizzie.google_analytics feature gives you traffic, conversion, and ecommerce analytics pulled directly from GA4 into Squizzie.
What you get
GA4 data appears in two places:
- Dashboard tiles — Key metrics like sessions, users, conversion rate, and revenue attribution show up as tiles on your Squizzie dashboard alongside your WooCommerce data. This means you can see traffic numbers and order numbers in the same view without switching between tools.
- Cross-source insights — When GA4 data is available, the Business Insights panel can correlate traffic patterns with order data. For example, Squizzie might notice that a traffic spike from organic search coincided with a jump in orders, or that your paid traffic has a lower conversion rate than direct visitors.
GA4 data also feeds into the report builder, so you can include traffic and conversion tiles in your custom reports and scheduled PDFs.
Enabling it
- Make sure you’ve completed the Google connection steps above (Client ID, Client Secret, OAuth flow)
- Go to Tracksies > Settings > Features and enable
squizzie.google_analytics - In Tracksies > Squizzie > Settings > Integrations, enter your GA4 Property ID (the numeric ID from your Google Analytics admin, not the “G-” measurement ID)
Once configured, GA4 tiles will start appearing on the dashboard and become available in the report builder. Data is fetched on demand when you load the dashboard or generate a report — there’s no background sync to wait for.
If GA4 data isn’t showing
- Check the feature toggle —
squizzie.google_analyticsmust be enabled in Settings > Features - Verify the Property ID — it should be the numeric property ID, not the measurement ID (the one starting with “G-“)
- Confirm API access — make sure the “Google Analytics Data API” (not “Google Analytics API”) is enabled in your Google Cloud project
- Check the connection — if your Google token has expired or been revoked, reconnect in the Integrations tab
Disconnecting
If you need to remove the Google connection entirely, click Disconnect in the Integrations tab. This removes all stored tokens and credentials from your site.
When you disconnect, any Google-powered tiles in your existing reports will simply stop rendering. The reports themselves won’t break — those tiles will just be skipped. Reconnect later and they’ll pick right back up.
Common Setup Mistakes
“Google Analytics API” vs “Google Analytics Data API”
The most common mistake. “Google Analytics API” is the old Universal Analytics API and does not work with GA4. You need “Google Analytics Data API”. If you’re getting authentication errors on your GA4 tiles, this is the first thing to check.
APIs enabled in the wrong project
If you have multiple Google Cloud projects, it’s easy to accidentally enable APIs in one project while your credentials are in another. When you see error messages, check the project number — it should match the project where you created your OAuth credentials.
Forgot to add the redirect URI
If the OAuth flow fails immediately after you click “Allow” on Google’s screen, you probably haven’t added the correct redirect URI to your OAuth credentials. Go back to Google Cloud Console > Credentials > your OAuth client > Authorized redirect URIs, and add the URI shown in your Squizzie settings.
OAuth consent screen not configured
Google won’t let you authorise an app that doesn’t have a consent screen set up. If you see an error about “access denied” or “app not verified”, go to APIs & Services > OAuth consent screen and make sure it’s configured.
Test user not added
While your consent screen is in “Testing” mode, only email addresses listed as test users can authorise. If you’re signing in with a different Google account than the one listed as a test user, you’ll be blocked.
Common Questions
Do I need a paid Google Cloud account?
No. All the APIs Squizzie uses are available on the free tier. You won’t be charged anything for the API usage involved in pulling report data.
Can I use the same Google Cloud project for other tools?
Yes. There’s no conflict. Your project can have many OAuth clients and many APIs enabled simultaneously.
What happens if my token expires?
Squizzie automatically refreshes your access token behind the scenes. You shouldn’t need to reconnect unless you revoke access from your Google account settings or your refresh token becomes invalid (which is rare).
Can different team members connect different Google accounts?
No — Squizzie stores one Google connection per site. The connected account should have access to all the Google services you want to use. If your Analytics and Business Profile are on different Google accounts, you may need to grant access to a single account across all services.
I connected successfully but a specific service shows “not connected”
Each service checks for its specific OAuth scope. If you connected before a particular service was enabled, Squizzie may not have requested that service’s scope. Click Reconnect to re-authorise with the full set of scopes.