Why scrape Bing Maps at all?

Coverage differs by market and category, and Bing surfaces listings Google either buries or never had. The source column keeps that contribution measurable.

Do rows from different sources have the same columns?

Yes. Every row carries the full field catalog; fields the source does not publish are left empty rather than dropped.

Provenance field

Source

Which map the row came from — Google Maps or Bing Maps — so a merged export stays auditable.

Column name: source
Group: Provenance
Availability: Every plan, free included

What this column contains

A short identifier naming the origin of the row.

Where the value comes from

Set by the extractor that produced the row and carried through every merge and export.

Example value

google_maps

What people use it for

01Split a merged export back into its sources when the two disagree.
02Measure incremental coverage: how many businesses Bing adds that Google missed.
03Trace a data quality issue back to the extractor that produced it.
04Filter to a single source when a downstream contract requires it.

What it will not tell you

Deduplication runs across sources on Place ID, so a business present on both maps appears once, tagged with the source that produced the surviving row.

Questions about this field

Why scrape Bing Maps at all?: Coverage differs by market and category, and Bing surfaces listings Google either buries or never had. The source column keeps that contribution measurable.
Do rows from different sources have the same columns?: Yes. Every row carries the full field catalog; fields the source does not publish are left empty rather than dropped.

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