Google Ads holds your paid-search campaigns and their spend, clicks, and conversions. Connecting it as a data source through the Connectors library syncs that performance data into your Alta workspace, where it becomes training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure spend efficiency, CPA, and ROAS — and tie ad performance to pipeline. Google Ads connects with credentials.

Who this is for: Marketing and demand-gen teams who want Google Ads performance measured alongside the rest of the funnel in Alta.

Before you start

Have your Google Ads Customer ID ready and access to an account that can read it (a manager/MCC account works too).
Connect a source only once per workspace. If Google Ads already shows Connected, edit the existing connection.

Connect Google Ads

Open Connectors from the sidebar.
Find Google Ads via the Data tab or the Search data sources box.
Click the Google Ads card to open the Create connector screen.
Fill in the connection fields shown (such as your Customer ID and credentials), then click Create.
Alta runs a connect test. If it fails you'll see The connect test has failed with Google's error — fix the field and retry.
The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

Open the connection. Google Ads brings in campaigns, ad groups, ads, and performance report tables.
Use the Synced toggle in the Google Ads tables section to control what's pulled in.
Turn off Show only synced tables to see everything available.

Key tables and fields synced

campaigns — id, name, status, advertising_channel_type, start_date
ad_groups — id, name, campaign_id, status
campaign performance (report) — date, impressions, clicks, cost_micros, conversions, conversions_value
ads — id, ad_group_id, type, status

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

"What did we spend by campaign last month?" — sums cost_micros (÷ 1,000,000) grouped by campaign.
"What's our cost per conversion?" — divides spend by conversions.
"Which campaigns drive the most conversions?" — ranks the performance report by conversions.
"How is click-through rate trending?" — trends clicks ÷ impressions over date.

Build your first metric (worked example)

Confirm the campaign performance table shows Last sync — Succeeded.
In Metrics, create a metric measuring spend as sum(cost_micros) / 1,000,000, with date as the date field.
Group by campaign and set the period to weekly.
Save, add to a dashboard, then ask Luna "what did we spend by campaign last week?" to confirm.

Example use cases

Paid-media dashboard. Spend, clicks, conversions, CPA, and ROAS by campaign over time.
Channel efficiency. Compare cost per conversion across campaigns and channel types.
Ads-to-pipeline. Combine with CRM data to connect ad conversions to real pipeline and revenue.
Budget pacing. Track spend vs. target through the month.

Keep it in sync

Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.
Click Sync now to refresh immediately; it's disabled while a sync runs.
Use the overflow menu (⋯) to Disable, Enable, or Delete.

Tips and common pitfalls

Cost is in micros. Divide cost_micros by 1,000,000 to get currency.
Use the right Customer ID. If you use a manager (MCC) account, point at the child account whose data you want.
Recent days shift. Conversions can be attributed after the click, so very recent numbers may still rise.
Deleting is permanent. Disable instead to pause.