Identifiers

What is a Google Maps Place ID?

A Place ID is Google’s canonical string for a business listing. Outbound, SEO, and CRM teams store it so renamed or relocated listings stay one record—not three near-duplicates.

Updated September 21, 2026

Also called: Place Id · placeId · place_id · ChIJ ID

What a Place ID looks like

Most Place IDs begin with `ChIJ` followed by a long base64-like string. Length varies; treat the whole token as opaque—do not truncate or “clean” it.

  • Valid: a full string such as `ChIJN1t_tDeuEmsRUsoyG83frY4`
  • Invalid: a business name, a search URL, or only part of a ChIJ token
  • Also invalid as a Place ID: decimal CID or a hex pair like `0x…:0x…`

Where Place ID appears

SurfaceHow you see it
Maps place / share URLOften as `place_id=`, `query_place_id=`, or nested `!19sChIJ…`
Lead CSV / Online exportColumn Place Id
Photos jobs & Agent APIAccepted as a `place` input alongside URL and business_id
Writereview links`placeid=` on search.google.com local review URLs

Reviews jobs primarily accept a Maps URL or business_id / Fid. Photos jobs also accept Place ID. See Place ID vs CID when a client sends the “wrong” format.

How to get a Place ID

  1. Open the listing on Google Maps and copy the place URL or share link (not a generic search results page).
  2. Paste it into the free Place ID & CID Converter.
  3. Copy the Place ID field into your CRM, API call, or review workflow.

For bulk discovery, scrape leads first with the Online extractor—Place Id ships on each row—then convert only when a review or Places API step needs a paste-time lookup.

How Place ID helps lead workflows

  • Dedupe lists when two keywords return the same shop under slightly different names
  • Re-enrich or re-scrape the same listing without guessing from address strings
  • Start photos jobs from a stored ChIJ when you already keep Place IDs in a CRM
  • Build writereview URLs that survive minor Maps URL redesigns

Common mistakes

  • Pasting a search results URL instead of a place URL into a converter
  • Storing only name + address and rediscovering the same lead every quarter
  • Treating CID or Fid as interchangeable with Place ID in Places API calls
  • Truncating the ChIJ string when copying from a long URL

FAQ