How to Connect Google Ads, BigQuery and Search Console to GA4

Most GA4 properties are set up as standalone tools — the tracking code goes on the site, events start flowing in, and that's where the configuration stops. The integrations covered in this guide are often treated as optional extras, but they're not. They're what transforms GA4 from a page view counter into the connective tissue between your paid activity, your organic visibility, and your raw data infrastructure.

Each integration is independent — you can set up any one of them without the others — and each requires a specific set of permissions to configure. We'll cover the permissions required, the setup steps, and the practical impact of each connection before you decide which to prioritise.

---

What each integration unlocks

The three integrations address different parts of the analytics picture. Google Ads covers paid acquisition. Search Console covers organic acquisition. BigQuery covers data infrastructure and depth of analysis. Together they give you a complete view of how users find your site and what they do when they get there — across both paid and organic channels — with the raw data available for any custom analysis that GA4's UI can't provide.

---

Integration 1 — Connecting Google Ads to GA4

What the link does

Linking Google Ads to GA4 creates a bidirectional connection between the two platforms. Data flows in both directions:

• From GA4 to Google Ads: GA4 conversion events and audiences are made available inside Google Ads. You can import GA4 conversions as the primary conversion action for campaign optimisation, and use GA4 audience segments for remarketing targeting.
• From Google Ads to GA4: Campaign, ad group, and keyword data appear in GA4's acquisition reports. You can see sessions, conversions, and engagement metrics broken down by your paid campaign structure — not just by source/medium.

Permissions required

Both access levels must be held by the same Google account performing the link. If you have GA4 Editor access but only Standard access on the Google Ads account, the link will fail at the final step.

How to link Google Ads to GA4

1. 1
   Go to GA4 Admin → Product Links → Google Ads Links In your GA4 property's Admin panel, scroll to the Product Links section and click Google Ads Links. Click the blue Link button in the top right.
2. 2
   Select the Google Ads account to link Click Choose Google Ads accounts. GA4 will display all Google Ads accounts accessible to your Google account. Select the account you want to link and click Confirm. If you manage multiple Ads accounts under a manager account (MCC), you can link individual accounts or the entire MCC.
3. 3
   Configure link settings On the next screen, you'll see two toggles. Enable Personalised Advertising allows GA4 audiences to be used for remarketing in Google Ads — leave this on unless you have a specific legal reason not to. Enable Auto-Tagging ensures Google Ads appends gclid parameters to destination URLs so GA4 can correctly attribute sessions to specific ads — this should always be enabled.
4. 4
   Review and submit Review the configuration summary and click Submit. The link is created immediately and will appear in the Google Ads Links table. Data flow between the two platforms begins within 24 hours.

After linking: importing GA4 conversions into Google Ads

Creating the link doesn't automatically make GA4 conversions available in Google Ads — you need to import them explicitly. In Google Ads, go to Goals → Conversions → Summary → New Conversion Action → Import → Google Analytics 4 Properties. Select the GA4 property and choose which conversion events to import.

Once imported, you can set these GA4 conversions as your primary conversion actions for Smart Bidding — replacing any existing Google Ads conversion tags that track the same actions. Running both simultaneously will cause double-counting in Google Ads reports, so remove redundant Ads conversion tags once the GA4 import is live and verified.

---

Integration 2 — Connecting BigQuery to GA4

What the link does

The BigQuery link exports a copy of every GA4 event to a BigQuery dataset in your Google Cloud project. Two table types are written: a permanent daily table (events_YYYYMMDD) created once per day, and an intraday table (events_intraday_YYYYMMDD) refreshed continuously throughout the day with the current day's events.

This export is what gives you access to GA4's raw, unaggregated, unsampled data. Everything GA4 collects — every event, every parameter, every user property — is in BigQuery. You can write SQL queries against it, join it to other datasets, export it to Data Studio, or feed it into custom machine learning models.

Permissions required

How to link BigQuery to GA4

1. 1
   Create a Google Cloud project with billing enabled If you don't already have a GCP project, go to console.cloud.google.com, create a new project, and attach a billing account. The BigQuery export itself is free — you pay only for the storage your data occupies and the queries you run against it. A typical GA4 export for a medium-traffic site costs a few dollars per month in storage.
2. 2
   Go to GA4 Admin → Product Links → BigQuery Links In your GA4 property's Admin panel, click BigQuery Links under Product Links. Click Link.
3. 3
   Choose your Google Cloud project Click Choose a BigQuery project. GA4 will list all GCP projects your Google account has access to. Select the project you want to export data into. If your project doesn't appear, confirm that your account has the required IAM permissions on that project.
4. 4
   Select data location Choose the BigQuery region where your dataset will be created. Pick the region closest to your primary user base — EU (multi-region) for European businesses, US (multi-region) for North American ones. This affects both query performance and data residency compliance. The region cannot be changed after the link is created.
5. 5
   Configure export options Choose between Daily export only, or Daily and Streaming (which enables the intraday tables). Also select which data streams to export — if you have both web and app streams in the same GA4 property, you can choose to export all of them or a subset. Enable Include advertising identifiers only if you need mobile advertising IDs and have the appropriate consent framework in place.
6. 6
   Review and submit Review the summary — project ID, dataset location, export frequency, data streams — and click Submit. GA4 creates a dataset named analytics_XXXXXXXXX (where X is your GA4 property ID) in the specified BigQuery project. The first daily export runs the following day.

Verifying the export

The first daily table (events_YYYYMMDD) will appear in BigQuery on the day after you create the link. To verify it's working, open BigQuery Studio, navigate to your project and the analytics_XXXXXXXXX dataset, and run a simple query:

BigQuery SQL — Verify the export is working

SELECT
  event_date,
  COUNT(*) AS total_events,
  COUNT(DISTINCT user_pseudo_id) AS unique_users
FROM
  `your-project.analytics_XXXXXXXXX.events_*`
WHERE
  _TABLE_SUFFIX = FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 1 DAY))
GROUP BY
  event_date

Compare the unique_users figure against yesterday's user count in GA4's standard reports. The numbers won't match exactly — GA4's UI applies some processing that BigQuery raw data doesn't — but they should be in the same ballpark. A large discrepancy warrants investigation into whether the correct data stream is being exported.

---

Integration 3 — Connecting Search Console to GA4

What the link does

The Search Console integration surfaces organic search performance data — queries, impressions, clicks, click-through rate, and average position — inside GA4's reporting interface. Once linked, GA4 adds a Search Console collection to your Reports section containing two pre-built reports: Google organic search queries and Google organic search traffic.

The query report shows which search terms are driving clicks to your site alongside GA4 engagement metrics for those sessions — average engagement time, conversion rate, and key events — for sessions that arrived via that query. The traffic report shows landing page performance for organic search traffic, combining Search Console's impression and click data with GA4's on-site behaviour data.

Permissions required

How to link Search Console to GA4

1. 1
   Go to GA4 Admin → Product Links → Search Console Links In your GA4 property's Admin panel, click Search Console Links under Product Links. Click the Link button.
2. 2
   Choose your Search Console property Click Choose accounts. GA4 will display all Search Console properties your Google account has access to. Select the property matching your website. If you don't see the expected property, either your account doesn't have Owner or Full User access, or the Search Console property hasn't been verified yet.
3. 3
   Select the web stream to associate GA4 will ask which data stream to associate with this Search Console property. Select the web stream that tracks the same domain as the Search Console property. If your GA4 property has multiple data streams, ensure you're picking the right one.
4. 4
   Review and submit Review the link configuration — GA4 property, Search Console property, and associated data stream — and click Submit. The link activates immediately. The Search Console reports appear in GA4's Reports section within 24 hours, though data population may take a day or two to become visible.

Understanding the data in the Search Console reports

Once linked, the Search Console data in GA4 has a few characteristics worth understanding before you build reporting around it:

• There is a 2–3 day data delay. Search Console data is not available in real-time — Google typically finalises search data with a 48–72 hour lag. The Search Console reports in GA4 reflect this same delay, so you won't see yesterday's queries in today's report.
• Query data is sampled for privacy. Search Console applies query-level anonymisation — queries with very few impressions are grouped or omitted to protect user privacy. This is a Search Console limitation, not a GA4 one, and affects both platforms equally.
• The join between search data and GA4 sessions is approximate. Search Console data is matched to GA4 sessions by landing page and date. It's a best-effort join — not every Search Console click will be perfectly matched to a GA4 session, particularly on sites with complex URL structures or heavy JavaScript rendering.
• Impressions and clicks come from Search Console; engagement metrics come from GA4. The two datasets are displayed together but have different sources. Impressions and average position are from Search Console; engagement time and conversions are from GA4. Treat them as complementary signals rather than a single unified data model.

---

Managing and troubleshooting your links

All three integrations are managed from the same Product Links section in GA4 Admin. A few things worth knowing once your links are in place:

Checking link status

Each product links table shows the link status — Active, Pending, or Error. If a link shows Error, it usually means the account permissions on the linked platform have changed. Re-verify that the Google account managing the GA4 property still has the required access on the linked platform, then recreate the link if necessary.

One GA4 property, multiple linked accounts

A single GA4 property can be linked to multiple Google Ads accounts — useful if you run campaigns across separate Ads accounts for different brands or markets. Similarly, you can have multiple BigQuery links if you want to export to more than one GCP project. Search Console links are limited to one property per GA4 data stream.

Unlinking

Any link can be removed from the Product Links table. Removing the Google Ads link stops the flow of GA4 audiences and conversion data to Ads, and removes campaign-level data from GA4's acquisition reports — but doesn't delete historical data already in GA4. Removing the BigQuery link stops future exports but does not delete the data already written to BigQuery. Removing the Search Console link removes the Search Console reports from GA4's Reports section.

---

Which integration to set up first

If you're setting up all three from scratch and need to prioritise, the order matters for one important reason: the BigQuery export is not retroactive. Every day you wait to enable it is a day of raw event data you'll never be able to recover. The other two integrations don't have this constraint — you can link Google Ads or Search Console at any point and the historical data those platforms hold is still accessible.

---

GA4's product integrations are some of the highest-leverage configurations in your analytics setup — each one unlocks a category of insight that no amount of event tracking or custom reporting can substitute for. Setting them up takes less than an hour in total. The data they provide compounds in value the longer they've been active.