Overview

The Origins feed groups visitation to properties of interest by the Census Block Groups where visitors live.

This feed's data enables businesses to integrate data based on regions for extended location analysis.

To learn more about the latest update in this feed, click here.

Configuration

Configuration aspect	Available options descriptions
Data granularity	Monthly
File formats	CSV
Metrics selection	Visits
Regions	The Census Block Group(CBG) is currently available as the visitors' home region (Based on Census CBGs 2020 geography New!).
Feeds time frame	The feed's timeframe can be configured to commence from January 2022 or any later date.
Visit duration segmentation	The following visit duration segments are available for data calculation selection in the feed: Only visits that lasted less than 10 minutes Only visits that lasted 10 minutes or longer All visits The default segmentation will be considered if no other segment is specified. (Click here For more information on visit duration segmentation)
Delivery methods	Please refer to the following Delivery Details for all supported Origins feed delivery options.
Delivery Schedule	The feed is delivered on the 6th of each month.
Control files	Not supported
Success file	Not supported
Amazon SNS notification	Not supported

Deliverables and Schemas

Metrics

Please refer to the definition and structure of the metrics file:

Column	Description	Type	Example
publication_date	Data publication date	ISO-8601 date	2023-01-01
id	Placer's entity ID	string	'5965fca0173f564b883c222e'
type	Entity type. Supported entity types: venue, complex, chain, and billboard.	string	'venue'
start_date	Data start date.	ISO-8601 date	2022-04-15
end_date	Data end date (inclusive)	ISO-8601 date	2022-04-15
region_code	The code of the region where visitors to the POI were located. For the CBG type of region, the FIPS code is presented.	string	'360470163003'
region_type	The type of region where visitors to the POI were located.	string	'cbg'
origin_type	The type of origin - Home/Work. I.e. List of CBGs that are considered as the home location of visitors to the POI As of now supporting home type of origin only.	string	Home
visit_duration_segmentation	Displays the visit duration segmentation used for the generation of the raw reported data. The values within this column may fall into one of the following categories: 'under_10_min' '10_min_or_longer' 'all_visits'	string	'under_10_min'
visits	The estimated foottraffic measured from the specific region to the POI for the date range. Total of: 1 column	int	5000000

Deprecated Columns

The complete removal of those columns will take place on 2024-09-22.

Column	Description	Type	Example
mainType	Originating entity type. Supported values: 'venue', 'complex', 'chain', and 'billboard'.	string	'venue'
mainId	Originating entity Placer ID.	string	'5965fca0173f564b883c222e'

These deprecated fields provided additional context as to why a line was included in the report. If a venue was explicitly included, its ID and type will be noted. If the venue was included as part of a chain, the chain details will be included.

Important: These fields should not be used for any new integration, and are only provided to assist during a transition period and will be removed in future versions.

POI Metadata

Please refer to the following page for the POI metadata schema.

Regions metadata

Please refer to the following attributes provided as part of the regions' metadata file.

Column	Description	Type	Sample value
publication_date	Data publication date	ISO-8601 date	2023-01-01
region_code	The code of the region where visitors to the POI were located. For the CBG type of region, the FIPS code is presented.	string	'360470163003'
region_type	The type of region where visitors to the POI were located.	string	'cbg'
population	The population within the CBG, based on Census 2022 (New!).	long	4536288

Metadata for Tags

Customers that request a metadata file for feeds that contain tags (i.e. the feed’s entity list is defined using tags) will receive a tags_entities_mapping.csv file to supplement your analysis.

The tag entities mapping file helps to bridge the relationship between tags and the entities they contain, offering a clear data structure that enhances the traceability and usability of the delivered tag-based data.
The metadata file includes the following schema:

Column	Description	Type	Example
tag_id	The identifier of the tag.	string	'636371ee42a729232a6b755e'
tag_name	The name of the tag.	string	'My Tag'
entity_id	The identifier of the entity associated with the tag.	string	'5965fca0173f564b883c222e'
entity_type	The type of entity (i.e. venue, complex, chain or billboard) associated with the tag.	string	'venue'

This file helps you easily correlate feed entities with the originating tags, enabling streamlined data validation, filtering, and analysis.

Sample files

Origins feed sample

📘
Grow and expand
Follow our announcements regarding additional attributes (metadata) and metrics.
New metadata attributes will be announced and delivered to you once released.
Please contact your customer support manager to receive new/additional metrics as part of your feed.

🚧
Columns order
Please be aware that the order of columns may change slightly due to the continuous addition of data to the export and its associated metadata.

👍
Privacy comes first
Placer is a privacy-first company, and like all our product this feed conforms to our privacy policy as is described in our Trust Center. In situations where the content of this feed conflicts with our privacy policy, the conflicting data points will be redacted from the files. Sparsely populated CBGs may not be included in the feed to align with Placer’s privacy policy.