Multi-city leads with campaign deduplication

A 20-city workflow

1. Choose one industry and 20 supported city codes in the workspace or API.
2. Preview the campaign to confirm cities, search depth and estimated maximum records.
3. Set maxLeads to cap the unique businesses delivered across the campaign.
4. Run the campaign, review the combined results and export after completion.

Depth is per location, not a promise of that many businesses. Select 1–100 location codes; states, provinces and territories can expand into many cities, so inspect the preview. The total cap helps keep a large region selection within your intended volume.

Repeated record versus separate branch

CID is the first deduplication key, followed by Place ID and then normalized name plus address. If the same Maps business appears in Austin and a neighboring city's search, it becomes one campaign record and one billable business. If one chain has two addresses and distinct identifiers, both branches remain separate, even when they share a website.

An illustrative 24 returned records with four repeated business records gives 20 unique delivered businesses and 20 search credits. This is a calculation example, not a real coverage measurement. A later independent campaign may charge those businesses again. Root-domain company merging and CRM-wide exclusion/upsert are not current features.

Pause, resume and stop

Pause prevents later cities from starting; an active city can finish. Resume continues the plan. Stop also prevents later cities; the active child is cancelled and its unused reserved credits released when the worker observes the stop. A supplier request already in flight may still have a provider cost. These controls do not reverse previously delivered results.

See API requests, billing units and review rules. Open the workspace.