Placer.ai: what it returns, and whether it works in Clay

Placer.ai is not available in Clay. It is best for Diligence, Content demo. Pricing: Sales call. Access: Enterprise subscription; API key with account quota; data feeds through Snowflake and SNS; pricing not public (unknown); free limited tools on placer.ai. Data is aggregated and extrapolated; no device-level data is delivered..

Data domains: Foot traffic, Locations, Local business, Signals, Competition.

What does Placer.ai return?

Official fields: visits (one visit per person per POI per day); visitors (extrapolated from unique mobile devices in the panel); visit duration bins from 0 to 150 or more minutes; visits by hour and day of week; visits by census block group (origins, Census 2020 boundaries); true trade area and drive-time trade area; trade area demographics (US Census ACS 2023, STI Popstats 2024); rankings index (top-ranked and closely ranked); favorite places and favorite chains; same-store visits; chain visit forecast; migration trends; retail sales trends, transaction trends and average ticket size; entity metadata (chain, complex, tag, venue category).

What can you derive from it?

1. Store health: year-over-year visit trend per location and per chain. 2. Expansion and contraction: the Brand Sourcing feed flags rapidly growing or shrinking retail brands. 3. Competitive set: favorite chains and trade-area overlap show which brands share customers. 4. Site potential: trade area demographics and captured market for a new location. 5. Portfolio ranking: locations ranked against category peers.

How would a GTM team use it?

1. PE screen: list consumer brands with rising same-store visits over 12 months and private ownership. 2. Revenue trigger: when a chain opens in a client's trade area, start outreach to that chain's regional management. 3. Competitive watch: weekly visit index for a client's locations versus named competitors. 4. Diligence: compare a retail target's claimed store performance with visit trends per site. 5. Market map: rank all centres and chains in a metro by visits for a retail-services client.

What are the caveats?

Not a native Clay integration as of 2026-10-17 (checked against Clay's integrations catalog). Can be called through Clay's HTTP API column where an API exists. Foot traffic is modelled from a mobile device panel (tens of millions of devices from partner apps) and extrapolated to population; visits are estimates, not transactions. Partners strip device identifiers before data reaches Placer; locations with fewer than 50 unique devices are not shown (k-anonymity of 50); sensitive places such as schools, places of worship and health facilities are excluded. Indoor and multi-tenant attribution can be wrong. Retail sales exclude online. Google Maps in Clay provides place details, not visit counts.