CID or Place ID — which should I store?

Store both, key on Place ID. CID costs one integer column and saves you an API call every time you want a direct link.

Why is CID empty on some rows?

Not every listing surface exposes it. The column stays empty instead of being derived from something that only resembles a CID.

Identity field

CID

The numeric customer ID behind a Google Maps listing, useful for building direct links and for joining against older datasets.

Column name: cid
Group: Identity
Availability: Every plan, free included

What this column contains

A long integer that identifies the listing in Google's own systems. It predates Place ID and still appears in Maps URLs.

Where the value comes from

Extracted from the listing's Maps URL. When a listing exposes no CID the cell is left empty rather than filled with a guess.

Example value

17925385792314657000

What people use it for

01Build a direct listing link of the form maps.google.com/?cid= without an API call.
02Join against lead lists exported from tools that only recorded a CID.
03Keep a second identifier alongside Place ID so a reissued ID does not orphan the record.
04Hand a support or agency partner a link that opens the exact listing you mean.

What it will not tell you

CID is not documented as a stable public identifier the way Place ID is, so use it as a convenience key and a link builder rather than as your primary key.

Questions about this field

CID or Place ID — which should I store?: Store both, key on Place ID. CID costs one integer column and saves you an API call every time you want a direct link.
Why is CID empty on some rows?: Not every listing surface exposes it. The column stays empty instead of being derived from something that only resembles a CID.

This is one of 41 columns on every row, on every plan. See the full field reference or check pricing.

CID