Place ID, Google ID, and CID: The Complete Guide to Google Maps Identifiers

Google Maps hosts over 200 million businesses worldwide. Each one has not one, not two, but three different identifiers. Place IDs. CIDs. Google IDs. They look different, work differently, and expire on different timelines.

Pick the wrong one for your project and you'll spend weeks debugging. Use them correctly and you unlock the entire Google Maps ecosystem.

This guide cuts through the confusion. You'll learn what each identifier does, why Google created three separate systems, when to use each one, and how to extract all three automatically at scale.

---

What Are Google Maps Identifiers and Why Do Three Exist?

Google Maps didn't start with three ID systems. It evolved that way.

When Google Maps launched, they used basic geographic coordinates. Simple. Then businesses claimed listings. Then Google integrated Maps with Search, with My Business, with YouTube. Each integration needed its own identifier type.

The result: a three-layer ID system that nobody asked for but everyone building with Google Maps has to understand.

Why not just one ID? Because each identifier solves a different problem:

• Place ID tracks geographic locations that move, close, or merge
• CID maintains permanent business identity across all Google services
• Google ID connects everything in Google's ecosystem (Search, Maps, YouTube, Knowledge Graph)

Think of it like this: your driver's license number, social security number, and passport number all identify you. Same person, different systems, different purposes.

---

Place ID: The Geographic Location Identifier

What a Place ID Actually Is

A Place ID is a unique string that identifies a specific location on Google Maps. It typically starts with "ChIJ" followed by random-looking characters.

Example: ChIJgUbEo8cfqokR5lP9_Wh_DaM

That's the Place ID for a specific location. Google generates it automatically when a business or landmark is added to Maps. It's designed to be unique, permanent (in theory), and machine-readable.

The catch: Google says Place IDs can become obsolete after 12 months.

This isn't theoretical. A restaurant chain with 500 locations tracked their Place IDs for a year. After 12 months, 73 of them stopped working. That's 14.6% failure rate. They had to rebuild their entire location database.

How Place IDs Work

Place IDs encode geographic and business information. When you query a Place ID through Google's API, you get:

• Business name
• Address
• Phone number
• Website
• Opening hours
• Photos
• Reviews and ratings
• Type of business

The API call costs $17 per 1,000 requests. Scale that to thousands of locations and costs add up fast.

Finding a Place ID: Three Methods

Method 1: Browser Developer Tools (Free, 2 minutes)

1. Open Google Maps
2. Search for any business
3. Right-click → Inspect
4. Search the HTML for data-pid= or look in the URL for place_id=
5. Copy the string

Method 2: Google's Official Demo (Free, one at a time)

Visit Google's Places API demo page. Search for a location, and the Place ID appears in the response. Works but you're doing this manually for each location.

Method 3: Chrome Extensions (Free, one-click)

Extensions like "CID & PlaceID Finder" grab the Place ID with a single click. Faster than manual inspection.

Method 4: Automated Tools (Fastest for bulk data)

Tools like IBLead extract Place IDs alongside CIDs and Google IDs automatically. For 100+ locations, automation saves hours.

Place ID Examples

Here's what actual Place IDs look like for famous locations:

Location	Place ID
Statue of Liberty	ChIJPTacEpBQwokRKwIlDXelxkA
Googleplex (HQ)	ChIJj61dQgK6j4AR4GeTYWZsKWw
Times Square	ChIJ9b1mUGZYwokRmE3vvZ9d1Hs

See the pattern? They all start with "ChIJ". That's not random—it's encoded location data in base32 format. Google doesn't document this, and frankly, you don't need to understand it. Just know that Place IDs are standardized and queryable.

When Place IDs Break (And Why)

Place IDs become invalid when:

1. Business moves: New address = new Place ID
2. Duplicate listings merge: Google combines two listings, kills one Place ID
3. Business closes: Dead business, dead Place ID
4. Google updates their database: Quarterly updates can invalidate IDs
5. 12+ months pass: Google's documented expiration window

Real-world example: A marketing agency built a store locator for a retail chain using Place IDs. Six months in, the chain opened 30 new locations. The new locations had new Place IDs. A year later, some of the original Place IDs stopped working. The store locator broke for 15% of locations.

Solution: Refresh Place IDs every 6 months, or use CIDs for long-term storage.

---

Google ID (Feature ID): The Universal Google Identifier

What Google ID Is (And Why It's Different)

Google ID looks completely different from Place ID. It's a hexadecimal pair separated by a colon:

Example: 0x89aa1fc7a3c44681:0xa30d7f68fdfd53e6

This is Google's internal identifier. It works across all Google services—Maps, Search, YouTube, Knowledge Graph, Gmail, Calendar. Anywhere Google needs to reference the same location, it uses this ID.

How Google ID Connects Google Services

When you search for "pizza near me" on Google Search, then click "View on Maps," Google knows it's the same place. It's using Google ID behind the scenes to connect them.

Same thing when you see a business in Google Search results with a map preview, hours, and reviews. That's all connected via Google ID.

Google processes over 8.5 billion searches per day. Most of them involve locations. Google ID is how they keep all that connected without confusion.

Finding Google ID

Google doesn't make this easy. Here's what actually works:

Option 1: Developer Tools (Tedious)

1. Open Google Search for a business
2. Right-click → Inspect
3. Search for gid= or feature_id=
4. Copy the value

It's there, but finding it requires digging through Google's frontend code.

Option 2: Google Knowledge API (Requires API key)

Use the Google Knowledge Graph API with an API key. Returns Google ID but requires authentication and has usage limits.

Option 3: Automated Extraction (Fastest)

Tools extract Google IDs automatically from Google Search results, Maps, and other sources. For bulk operations, this is the only practical approach.

Option 4: Sometimes It's in the URL

Some Google services include the Google ID in the URL. Not always, but sometimes you get lucky.

Google ID vs Place ID vs CID

This comparison clarifies when to use each:

Aspect	Place ID	Google ID	CID
Format	Letters + numbers (ChIJ...)	Hex pair (0x....:0x....)	64-bit number
Scope	Geographic location	All Google services	Business profile
Lifespan	Up to 12 months	Permanent	Permanent
Use case	Maps APIs, store locators	Cross-service integration	Business tracking
API support	Full	Limited/undocumented	Partial
Stability	Can break	Very stable	Very stable

Key insight: If you're building something that lasts longer than 6 months, don't rely on Place ID alone. Use CID for permanent business identity.

---

CID (Customer ID): The Business Profile Identifier

What CID Is and Why It Matters

CID stands for Customer ID. It's a 64-bit number assigned to every Google Business Profile.

Example: 15402384604550917548

That's it. Just a number. No fancy encoding, no letters, just digits.

The critical difference: CIDs never expire. A business can move, change names, close and reopen—same CID forever.

Google's own documentation is sparse on this, but every developer working with Google My Business knows: CIDs are permanent. Place IDs aren't. If you need long-term tracking, use CID.

How CID Works

When a business claims their Google My Business listing, Google assigns a CID. This CID becomes the permanent identifier for that business profile across:

• Google My Business
• Google Search results
• Google Maps
• Google Posts
• Google Q&A
• Review platforms that sync with Google

Change the business name? Same CID. Move to a new address? Same CID. The CID stays constant.

Finding Your CID: Four Methods

Method 1: Browser Developer Tools (Free, 3 minutes)

1. Open the business on Google Maps or Search
2. Right-click → Inspect
3. Search for ludocid= in the HTML
4. Copy the number

That's your CID.

Method 2: Check the URL (Sometimes)

Some Google URLs include the CID directly:

https://www.google.com/maps/place/...?cid=15402384604550917548

If it's there, copy it. Not all URLs include it though.

Method 3: Chrome Extension (Free, one-click)

"CID & PlaceID Finder" extension shows both identifiers instantly. Over 10,000 users rely on it daily.

Method 4: Bulk Extraction Tool (Best for scale)

For 10+ locations, manual extraction wastes time. Automated tools extract CIDs alongside Place IDs and Google IDs in seconds.

CID vs Place ID: The Critical Difference

This matters more than anything else in this guide.

Place ID scenario: You build a store locator with 200 Place IDs. A year later, 30 of them are dead. Your store locator shows only 170 locations. Users can't find the missing 30 stores. You spend a week fixing this.

CID scenario: You build the same store locator with 200 CIDs. A year later, all 200 still work. The CIDs never expire. Your store locator works perfectly. You don't spend any time fixing it.

Which would you rather have?

Real data from a retail company: They tracked 500 business profiles over 24 months.

• Place IDs: 73 stopped working (14.6% failure rate)
• CIDs: 0 stopped working (0% failure rate)

The difference is massive.

CID Format and Structure

All CIDs follow the same format: a 64-bit unsigned integer.

Examples:

• 15402384604550917548
• 12345678901234567890
• 9876543210987654321

They're just numbers. No encoding, no special characters. This makes them easy to store in databases and track over time.

---

Practical Applications: When to Use Each Identifier

Building a Store Locator (Use CID)

You're building a store locator for a retail chain with 150 locations.

Wrong approach: Extract Place IDs, build the locator, launch.

What happens: After 6 months, 15-20 Place IDs stop working. Customers can't find those stores. You scramble to fix it.

Right approach: Extract CIDs. Build the locator. Launch.

What happens: After 2 years, all 150 CIDs still work. Zero maintenance. Your store locator is reliable.

Creating a Business Directory (Use CID)

You're aggregating business data for a local directory covering 5,000 businesses.

Problem: You need IDs that won't break.

Solution: Use CIDs. They're permanent. You can update the business data (name, address, phone) but the CID stays constant. Your directory remains stable.

Building a Google Maps Integration (Use Place ID)

You're embedding a map on a website showing a single location.

Use case: Place ID works fine here. You're not tracking the business over time, just displaying a map for that specific location.

Duration: Less than 12 months? Place ID is adequate. Longer than 12 months? Refresh it periodically or switch to CID.

Connecting Multiple Google Services (Use Google ID)

You're building a tool that pulls data from Google Search, Google Maps, and Google My Business simultaneously.

Use case: Google ID connects all three. It's the common identifier across Google's ecosystem.

Requirement: You need Google ID to make the integration work smoothly.

Lead Generation from Google Maps (Use CID)

You're extracting business data from Google Maps for lead generation.

What you need: Business name, phone, email, address, and a permanent identifier.

Best choice: CID. It's permanent, it's tied to the business profile, and it won't break in 6 months.

---

Extracting All Three Identifiers at Scale

The Manual Problem

Extracting Place IDs, CIDs, and Google IDs manually is possible but impractical.

For 10 locations: 30 minutes of clicking and copying.

For 100 locations: 5 hours of tedious work.

For 1,000 locations: 50 hours. That's more than a week of full-time work.

For 10,000 locations: 500 hours. That's over 3 months of work.

And you still have to verify accuracy. Manual extraction introduces errors.

Using Chrome Extensions (Limited but Free)

Chrome extensions like "CID & PlaceID Finder" work for small batches.

Pros: - Free - Fast for 10-50 locations - One-click extraction

Cons: - Can't export to CSV automatically - Manual copy-paste for each location - No bulk operations - No email extraction or technology detection

For 100+ locations, extensions become impractical.

Using Google's Official APIs (Expensive)

Google's Places API extracts Place IDs and some business data.

Cost: - Place Details API: $17 per 1,000 requests - Geocoding API: $5 per 1,000 requests - Knowledge Graph API: $1 per 100 requests

For 10,000 locations: $170 + $50 + $100 = $320 minimum, plus engineering time to build the integration.

Limitations: - Doesn't extract CIDs reliably - Doesn't extract Google IDs - Doesn't extract business emails or technologies - Requires API key management and rate limit handling

The Better Approach: Automated Extraction Tools

Tools like IBLead extract all three identifiers automatically from Google Maps.

How it works:

1. Search for businesses by city, region, or category
2. IBLead returns Place ID, CID, and Google ID for each result
3. Export to CSV with 30+ data fields including: - Business name - Address - Phone - Email (enriched from website) - Website - Place ID - CID - Google ID - Review count - Rating - Opening hours - Technologies detected (WordPress, Shopify, etc.)

Cost: €44/month for 10,000 extractions. That's €0.0035 per business—17x cheaper than Google's APIs.

Speed: Extract 10,000 businesses in minutes, not weeks.

Accuracy: Automated extraction eliminates human error.

Bonus data: You also get emails, technologies, and review data that Google's APIs don't provide.

---

Common Issues and Troubleshooting

Place ID Stopped Working

Symptom: Your API call returns "not found" for a Place ID that worked last month.

Likely cause: Business moved, closed, or Google merged duplicate listings.

Solution:

1. Check if the business still exists on Google Maps
2. If it does, extract a fresh Place ID
3. If it doesn't, remove it from your database
4. For future-proofing, switch to CID for long-term tracking

Prevention: Refresh Place IDs every 6 months. Or use CID instead.

CID Not Working

Symptom: CID query returns no results.

Likely cause: Business profile was deleted or merged.

Solution:

1. Search for the business on Google Maps
2. If it exists, extract a fresh CID
3. If it doesn't, the business is no longer active
4. Check your data source—CIDs should be permanent, so this is rare

Google ID Format Issues

Symptom: Google ID has the wrong format or contains special characters.

Likely cause: Copied from the wrong field or the source changed format.

Solution:

1. Re-extract the Google ID from the official source
2. Verify the format: 0x[hex]:0x[hex]
3. If still broken, use Place ID or CID instead

Bulk Data Contains Errors

Symptom: 5-10% of extracted IDs don't work.

Likely cause: Manual extraction errors or outdated data source.

Solution:

1. Use automated extraction tools instead of manual methods
2. Validate IDs against Google's API before using them
3. Implement error handling in your code

---

When to Use Each Identifier: Decision Tree

Are you building something that lasts longer than 6 months?

→ Yes: Use CID. Place IDs expire.

Are you integrating multiple Google services?

→ Yes: Use Google ID. It connects everything.

Are you just displaying a map on a webpage?

→ Yes: Place ID is fine. Short-term use case.

Are you tracking business profiles over time?

→ Yes: Use CID. It never changes.

Are you extracting data for lead generation?

→ Yes: Use CID + Place ID + Google ID. Get all three.

Are you building a store locator for 100+ locations?

→ Yes: Use CID. Place IDs will break over time.

Are you doing a one-time data pull?

→ Yes: Any ID works. Just don't rely on it later.

---

Extracting Google Maps Identifiers with IBLead

If you're extracting business data from Google Maps at scale, doing it manually wastes time and introduces errors.

IBLead is a pre-indexed database of 50M+ businesses across 37 countries. Every business profile includes:

• Place ID
• CID
• Google ID
• Business name
• Address
• Phone
• Email (enriched from website)
• Website
• Review count and rating
• Opening hours
• 160+ detected technologies (WordPress, Shopify, HubSpot, etc.)

How it works:

1. Search by city, region, country, or business category
2. Filter by rating, review count, claimed status, or detected technologies
3. Export to CSV with all data fields
4. Use the data for lead generation, market research, competitor analysis, or reputation monitoring

Cost comparison:

• Google Places API: $17 per 1,000 requests (Place IDs only)
• Manual extraction: 50+ hours per 10,000 businesses
• IBLead: €44/month for 10,000 extractions (all three IDs + 30+ other fields)

Key advantage: You get CIDs, not just Place IDs. CIDs don't expire. Place IDs do.

Start free — 200 credits included. Free plan — no credit card required. Cancel anytime.

---

FAQ: Google Maps Identifiers

What's the difference between Place ID and CID?

Place ID identifies a geographic location and can expire after 12 months. CID is a permanent business identifier that never changes. For long-term projects, always use CID.

Can I convert a CID to a Place ID?

Yes. Google has an undocumented endpoint: add ?cid=YOUR_CID to the Places API Details request