What ludocid looks like
In a URL you will see ludocid= followed by a long decimal. That decimal is the CID in most lead-tooling contexts.
- Valid snippet: …?ludocid=5797000863177578206
- Same value family as cid= on other URLs
- Not interchangeable with ChIJ Place ID or 0x…:0x… Fid
Where ludocid appears
| Surface | Role |
|---|---|
| Search / local URLs | Identifies the place in query string |
| Review-related links | Often paired with other local params |
| Converters & parsers | Treated like cid when extracting decimal CID |
| Lead CSV | Exported as Cid (not a separate ludocid column) |
How to work with ludocid
- If a client sends a link containing ludocid=, copy the decimal—it is usually the CID.
- Prefer resolving a full place URL through the Place ID & CID Converter so you also get Place ID and Fid.
- Store Place Id as the CRM primary key; keep the decimal under Cid.
Lead workflow notes
- Accept ludocid links from clients without panicking—map them to Cid
- Still fetch Place ID before CRM merge when possible
- Use review extractors with a clean place URL or business_id rather than raw Search URLs when jobs fail
Common mistakes
- Creating a separate “ludocid” CRM field that duplicates Cid
- Assuming ludocid is a Place ID
- Pasting a Search URL with ludocid into tools that require a /maps/place/ URL