The Power My Analytics Google Ads connector can export click-level data, including the Google Click ID (GCLID) recorded for each ad click, through the Click View (GCLID) report. This guide explains how to request access, what data is included, and how to put the export to work: matching Google Ads clicks to HubSpot contacts and estimating click-level cost with average CPC.

What Is the Click View (GCLID) Report?

When Google Ads auto-tagging is enabled, Google appends a unique Google Click ID (GCLID) to the landing page URL of every ad click. Analytics and CRM platforms (including HubSpot) capture and store that GCLID, which makes it the key for joining an individual ad click to the person who clicked.

The Click View (GCLID) report is built on the Google Ads API click_view resource and returns one row per ad click. This is much more granular than PMA's standard Google Ads reports, which aggregate performance by campaign, ad group, ad, or keyword.

Common uses include:

• Matching Google Ads clicks to CRM contacts (for example, HubSpot's Google ad click ID contact field) to see which campaigns produce leads, MQLs, SQLs, and customers
• Auditing individual clicks by date, campaign, ad group, device, and network
• Allocating advertising spend across CRM lifecycle stages using average CPC

Requesting Access

The Click View (GCLID) report is available on request and does not appear in the field selector by default. To enable it for your organization, please submit a ticket to our support team and ask for the Google Ads Click View (GCLID) report.

Available Fields

Click View rows include the following fields (some values are only populated when applicable, such as keyword details for Search clicks):

• GCLID (Google Click ID): The unique identifier Google assigns to the click
• Date: The day the click occurred
• Campaign ID and Campaign Name
• Ad Group ID and Ad Group Name
• Device: The device type where the click occurred
• Ad Network Type: The network that served the ad (for example, Search or Display)
• Keyword Text and Keyword Match Type: Populated when the click is associated with a keyword
• Clicks: The click count for the row

For the complete, current list of fields, refer to the Schema Explorer.

How the Report Works

The Click View (GCLID) report behaves differently from other PMA Google Ads reports, and the differences come from requirements Google enforces in its API:

• Live data only: Click View data is requested directly from Google each time your report runs. It is not stored in the PMA warehouse, it is not part of your nightly data sync, and it cannot be backfilled.
• One day per request: Google requires every Click View request to cover exactly one day. A date range is retrieved one day at a time, so longer ranges take longer to load.
• 90-day window: Google retains click-level data for the most recent 90 days only. Clicks older than 90 days cannot be retrieved by any tool, regardless of when you connected your account.

If you need click-level history beyond 90 days, export Click View data on a regular schedule (for example, weekly) and store it in your own destination, such as a spreadsheet or data warehouse. Once a click ages past 90 days, Google no longer provides it.

Worked Example: Match Google Ads Clicks to HubSpot Contacts

HubSpot automatically records the GCLID of the ad click that led to a form submission in the contact property Google ad click ID (internal name hs_google_click_id). Because the Click View report gives you the same GCLID from the Google Ads side, you can join the two datasets and connect ad clicks to real contacts.

1. Export Click View rows for each day you want to analyze (remember: one day per request, within the last 90 days).
2. Export your HubSpot contacts with the Google ad click ID property and their lifecycle stage. If you use the PMA HubSpot connector, include these contact fields in your report.
3. Join the two datasets on the GCLID value.
4. Roll the results up by campaign, ad group, or lifecycle stage.

For example, suppose your Click View export for July 1 contains this row:

And your HubSpot export contains this contact:

The matching GCLID tells you that Jane became an MQL from a mobile click on the Brand Exact ad group in the Brand Search campaign on July 1. Aggregated across all matches, this shows how your spend maps to lifecycle stages such as Pre Lead, Lead, MQL, SQL, and Customer.

Worked Example: Estimate Click-Level Cost with Average CPC

Google does not provide cost for individual clicks, so the Click View report has no cost field. The recommended fallback is to allocate spend using average CPC at the lowest granularity you have (ad group level works well):

1. Pull your standard Google Ads report with Cost and Clicks by ad group and day.
2. Compute average CPC: Cost ÷ Clicks.
3. Assign that average CPC to every Click View row from the same ad group and day.

For example, on July 1 the Brand Exact ad group spent $150.00 across 100 clicks, so the average CPC is $1.50. Each of the 100 GCLID rows from that ad group on July 1 is allocated $1.50. If 3 of those GCLIDs match HubSpot contacts who became customers, you can attribute $4.50 of that day's spend to the Customer stage.

Allocated cost is an estimate. Real per-click prices vary within an ad group, so treat the results as directional rather than exact.

Caveats and Common Mix-Ups

• Auto-tagging is required. GCLIDs only exist when auto-tagging is enabled in your Google Ads account (Settings > Account settings > Auto-tagging). Without it, Click View rows will not be usable for matching, and HubSpot will not capture click IDs either.
• gbraid and wbraid are not available. Google does not expose these privacy-centric identifiers (used for iOS app-to-web measurement) through the click_view resource, in PMA or in any other reporting tool. Clicks measured with gbraid or wbraid cannot be matched by GCLID, so expect some contacts to have no match.
• No click-level cost. This is a Google API limitation, not a missing PMA field. Use the average CPC allocation method described above.
• The 90-day window is a Google retention limit. It is separate from Google's 37-month data retention policy for aggregated reports, and it cannot be extended by backfilling.
• HubSpot may not capture every GCLID. HubSpot records the click ID when a visitor submits a form under its tracking conditions. Contacts created through imports, offline sources, or untracked pages may have an empty Google ad click ID property.
• Expect high row volume. One row per click means busy accounts can produce tens of thousands of rows per day. Filter to the campaigns or dates you need.

Related Resources

• Google Ads Data Connector User Guide
• Submit a Ticket
• Google Ads Help: About auto-tagging
• HubSpot Knowledge Base: Default contact properties (Google ad click ID)
• Schema Explorer (Google Ads)