What business_id / Fid looks like
Always a pair: left hex, colon, right hex. Both sides usually start with 0x. Never drop the colon or keep only the trailing hex from a review hash.
- Valid: 0x89c25a31c4a7d4d3:0x6a0e8c8f2b1a9e7c
- Same entity names: Fid (CSV), business_id (API/MCP), feature hex pair (converter UI)
- Not the same: ChIJ Place ID, or a lone decimal CID
Where Fid / business_id appears
| Surface | Name you see |
|---|---|
| Lead CSV / Online export | Column Fid |
| Reviews & photos jobs | business_id accepted as place input (with Maps URL) |
| Agent HTTP / MCP | place field may be a Maps URL or business_id pair |
| Maps URL internals | Often as !1s0x…:0x…, ftid=, or #lrd=0x…:0x… |
The right-hand hex often converts to the decimal CID. The full pair is still what APIs label business_id.
How to get a business_id / Fid
- Copy a Google Maps place URL (or a review deep link that includes the full pair).
- Paste into the Place ID & CID Converter and copy Feature hex pair.
- Or export leads—the Fid column is already filled for each row.
For reviews and photos, paste either the Maps URL or the 0x…:0x… business_id—one place per job.
How Fid helps lead workflows
- Queue review or photo scrapes without reopening Maps when you already stored Fid
- Match rows across tools that speak business_id instead of Place ID
- Debug broken review links that embed #lrd= hex pairs
- Keep a secondary key next to Place Id for partners who only send hex IDs
Common mistakes
- Calling Fid a Place ID in Places API requests
- Saving only one half of the pair from a #lrd= fragment
- Creating separate glossary or CRM fields for “Fid” and “business_id” as if they differed
- Confusing the converter’s “CID (hex)” (single hex) with the full feature hex pair