Skip to main content

Do I need Google Ads access as well as Local Services Ads?

Yes. This data source draws on two sources of data at once. Account-level totals such as leads, spend, and cost come from Local Services Ads, while individual lead records come through the connected Google Ads account. The Google Ads account must be linked to the Local Services Ads profile and reachable during connection, or lead-level breakdowns will return no rows even when account totals load. If the account sits under a manager account, the manager (login) account is resolved at connection time and reused for reporting.

Why are my lead numbers different from what I see in Google Ads?

Local Services Ads counts a lead as a billable phone call, message, or booking, which is a different unit from the clicks, impressions, or conversions reported for standard Google Ads campaigns. The two should not be expected to line up. Lead status also changes over time: a lead can be booked, archived, or marked for a credit request, and those changes are reflected on the next sync rather than instantly. For standard Search, Display, Performance Max, and Video reporting, use the separate Google Ads data reference instead.

Why does my dashboard show fewer leads than my Local Services Ads app?

The Local Services Ads app shows every inbound contact, including ones that are not billable leads. Adriel reports the leads returned for the selected date range, so counts differ when contacts fall outside that range or are not classified as billable leads. Widening the widget date range and removing restrictive filters usually closes most of the gap. A lead is attributed to the date it was created, so a contact near the edge of a range can land in an adjacent period.

How is cost per lead calculated?

Cost per lead is spend divided by the number of billable leads for the selected period, computed by Adriel rather than returned directly by Local Services Ads. Because the denominator is the billable-lead count, the value moves whenever spend or the billable-lead count changes. Leads that are later credited stop being billable, so cost per lead can rise slightly for a past period once credits are applied.

Why did the lead count or cost change for a period I already reported?

Local Services Ads allows advertisers to request credits for leads that were not genuine, and those requests are reviewed after the fact. When a credit is approved, the lead is no longer counted as billable, and both the lead total and the spend for that period are restated. Numbers for a recent period can therefore keep settling for a short time after the period closes, which is expected behavior rather than a reporting error.

A new lead hasn’t shown up yet — where is it?

Newly received leads and recent status changes appear after the next sync, not the moment they happen in Local Services Ads. Account-level totals and individual lead records are imported through separate paths, so a total can update slightly before the matching lead detail row is available. If a lead still does not appear after a full refresh cycle, confirm it falls inside the widget date range and is a billable phone call, message, or booking. For the refresh schedule, see the data reference.

Data reference

Metrics, breakdowns, refresh cadence, and limits for this data source.

How to connect

Connect a Local Services Ads account and its Google Ads access to Adriel.

Google Ads data reference

Standard Google Ads Search, Display, Performance Max, and Video reporting.

Refresh strategies

How Adriel caches and refreshes connected data sources.