Google Ads in Chile: separate city coverage from conversions

Translate coverage into an operational list

Santiago can refer to different geographic areas. Record the comunas your team actually serves instead of relying on a broad city label. Consult the official administrative map when defining boundaries.

For each area, list available services, conditions and the responsible team. Mark it as routinely served, subject to confirmation or outside coverage. Preserve the original comuna when combining several into a commercial reporting zone.

Sources: Santiago Metropolitan Regional Government: Political and administrative divisions

Choose targeting for the buying situation

Review the difference between presence-based targeting and options that also include interest in a location. Google uses multiple signals; geographic accuracy is not guaranteed.

A local service may start by evaluating presence, while a property owner booking remotely creates a different buying journey. Confirm which locations the platform supports. A radius around an office does not establish that every address within it is serviceable.

Sources: Google Ads Help: Advanced location options · Google Ads Help: Measuring geographic performance

Ask where the work will happen

Ask which comuna needs the service, adding city and region when necessary. Request the complete address only when it is needed to confirm coverage.

Keep the declared service location, assigned zone, requested service, known campaign origin and qualification status in the CRM. Do not infer the service location from the campaign name. Leave an explicit unknown-location status until it is confirmed.

Use geographic reports to review ad delivery

Targeted and matched-location reports help explain delivery, but do not prove where the requested job will take place. Matched locations may reflect physical location or interest.

Compare reports with verified inquiries and preserve unspecified records. Available geographic detail varies; do not distribute unexplained differences across cities to create precision the report does not support.

Sources: Google Ads Help: Measuring geographic performance

Separate inquiries, qualified leads and sales

Qualify using service fit, confirmed coverage and actual capacity. Record why requests are rejected, including duplication, unsupported services and out-of-area work.

Commercial-stage conversion imports require a compatible, validated integration and compliance with applicable customer-data policies. Verify campaign goals and primary or secondary actions before optimizing toward them. Do not present a form, its qualification and its eventual sale as three customers.

Sources: Google Ads Help: Qualified leads and converted leads · Google Ads Help: About enhanced conversions for leads · Google Ads Help: Customer data policies · Google Ads Help: Primary and secondary conversion actions

A hypothetical three-comuna example

Suppose a maintenance business serves Santiago, Providencia and Ñuñoa. Targeting the entire Metropolitan Region would exceed that stated coverage.

A person in Valparaíso may request work in Providencia and qualify. Someone physically in Providencia may request work in Puente Alto, outside this example’s coverage. These hypothetical cases show why user location and service destination must remain separate.

Review outcomes by confirmed service location

Group CRM inquiries by their confirmed service destination and acquisition period. Keep pending records visible and allow for the time needed to qualify them.

• Each commercial area has a documented coverage list and owner.
• Out-of-area rejections have recorded reasons.
• Duplicate inquiries are identified.
• Imported conversions and campaign goals match the intended stage.
• Pending cases remain visible rather than being counted as losses.