How Advertisers Use POI Data for Campaign Planning
Advertisers use POI data to define where customers and competitors operate, build venue-based audiences, choose geographic media, exclude sensitive locations, tailor creative to local context, and prepare store-visit measurement. Effective planning starts with accurate coordinates, polygons, brand hierarchy, category labels, and operating status, then keeps those venue definitions consistent through activation and reporting.
How to use this article
Read the checklist here, then use the linked hub and product pages for procurement citations.
First define the campaign objective: reach visitors to a category, support a store opening, defend a trade area, conquest a competitor, or measure media around selected venues. Translate that objective into a venue list with required categories, brands, geography, operating status, and geometry. POI data supplies the place records and hierarchy, while POI and geofencing data supports polygon-based activation and measurement workflows.
Next, audit a sample that reflects the campaign. Include urban, suburban, rural, mall, shared-parcel, recently opened, and recently closed locations where relevant. Check coordinates, polygon boundaries, parent and banner brands, category assignments, duplicate records, and status dates. The purpose is not to find a flawless database. It is to understand which errors would change media decisions and how the provider handles them.
POI fields used in campaign planning
Planning task
POI inputs
Decision
Trade-area definition
Coordinates, polygons, venue type
Where media should run
Audience design
Category, brand, visit context
Who enters an eligible cohort
Competitive conquesting
Parent and banner hierarchy
Which rivals are included
Creative localization
Venue and neighborhood context
Which message fits the place
Measurement setup
Stable venue IDs and geometry
How visits reconcile later
From Venue Lists to Audiences and Media
A venue list can define geographic targeting, contextual inventory, or an audience based on permitted visit signals. These are different activation methods and should not be blended in reporting. Geographic targeting reaches devices in an area during a campaign. A historical venue audience depends on a separate mobility observation and eligibility process. Contextual planning can use the place or neighborhood without creating a person-level audience.
Document which method the campaign uses, the approved locations, lookback logic if applicable, exclusions, and destination platforms. Audience targeting can connect the venue plan to activation, while global mobility data is the separate observation layer when the approved use requires visits rather than place context alone.
Quality, Exclusions, and Governance
The most important quality dimensions depend on the plan. A national category campaign may care most about completeness and consistent taxonomy. A store-visit study may be more sensitive to polygon precision, entrances, co-location, and status. Use the POI accuracy evaluation guide and record acceptance rules before comparing vendors.
Remove sensitive places and prohibited categories before creating audiences or sending venue lists downstream. Retain the exclusion version used for the campaign. The FTC privacy and security guidance and Network Advertising Initiative guidance provide useful diligence context. Contract terms and applicable law still control the actual program.
The Venue List Is the Plan, and It Is Usually Built Carelessly
Campaign quality is decided when the venue list is assembled, well before any audience is built, and that step is routinely rushed. A list pulled by brand name or category label inherits every classification error in the underlying file: closed locations, businesses trading under a different name, and venues whose category is technically correct and commercially wrong. Everything downstream inherits those errors, and none of it is visible in a performance report.
Review the list as a list before it becomes an audience. Sample it, check that sample against reality, and look specifically for locations that no longer trade and for venue types the category label swept in that nobody would have chosen deliberately. Then set exclusions explicitly rather than by default, since venues you would not want the campaign associated with will not exclude themselves and are far more expensive to remove after a flight than before one.
Plan and Measure Against the Same List, Recorded
A common and entirely avoidable failure is planning on one version of a venue list and measuring against another. POI files change between the planning cycle and the post-campaign read, so a list rebuilt for measurement differs from the one that shaped the buy, and the difference surfaces as unexplained variance nobody can trace.
Freeze the list used for planning, store it alongside the campaign record, and measure against that frozen version rather than a fresh pull. Where a refresh is genuinely necessary, report both and say what changed. This costs almost nothing at the time and is the difference between a measurement that can be defended and one that cannot be reconstructed.
One more habit pays for itself across a year of campaigns: keep a short written record of why each exclusion exists. Exclusion lists accumulate entries added for reasons nobody documented, and a list that cannot be explained is one no team is willing to prune. Recording the reason and the date makes the list reviewable, which is what stops it either ossifying or being quietly abandoned when it becomes inconvenient.
Where a campaign runs repeatedly, keep the venue list under version control alongside the creative and the buy, so each flight can be traced to exactly what it targeted.
Keep Planning and Measurement on the Same Map
Planning and measurement should share stable venue IDs, brand hierarchy, geometry versions, and opening or closure decisions. Otherwise a campaign can target one definition of a chain and report outcomes against another. Preserve the launch file, record approved corrections, and make the measurement team acknowledge the same venue universe.
For campaigns that need visit outcomes, use the OOH store-visit attribution guide and cross-channel measurement. A useful pilot tests the buyer's venue list, produces reviewable geometry, and shows how changes propagate before the first media flight.
Frequently Asked Questions
What POI fields matter most for advertising planning?
Coordinates, polygons, stable venue IDs, brand hierarchy, category, address, operating status, and update provenance are common essentials. The priority depends on the campaign decision.
Can POI data be used without building an audience?
Yes. Advertisers can use POI for trade areas, contextual planning, media geography, creative localization, and measurement setup without creating a historical visitor audience.
Why should planning and measurement share venue IDs?
Shared IDs and geometry keep the campaign's targeted locations aligned with the locations used in outcome reporting, preventing taxonomy or boundary changes from appearing as performance differences.
How should advertisers test a POI provider?
Use a representative venue sample, define acceptance rules, review geometry and hierarchy, test sensitive-place exclusions, and verify how corrections reach activation and measurement files.
What is the most common cause of poor POI campaign targeting?
A venue list assembled from brand or category labels without review. It inherits closed locations, misnamed businesses, and venue types the label swept in. Sample it against reality and set exclusions deliberately before it becomes an audience.
Why freeze the venue list used for planning?
Because POI files change between planning and the post-campaign read, so a rebuilt list differs from the one that shaped the buy and produces variance nobody can trace. Store the frozen list with the campaign record and measure against it.
✓ Opt-Out Request Honored via Global Privacy Control
We use cookies and similar technologies to improve your experience. No marketing cookies are pre-selected. Learn more in our Privacy Policy. Your Privacy Choices.