FAQs

Q: What are flagged venues? Are those venues participating in the visits counting or ranking process?

A: There are several reasons why a POI is being flagged (for example, lack of foot traffic information, dense area, etc.). This causes unreliable visits data, which Placer prefers not to consider. Therefore, flagged entities’ traffic is not counted in visit aggregations.

Q: What are the storage size requirements for Feeds deliverables?

A: For you to plan and prepare the storage for the delivery of the feed, please find the following folder sizes estimations for each of the feeds:

Feed Name	Additional information	Estimated size
Chain/venue metrics The size varies based on the amount of data configured in the feed (i.e. Number of chains/venues analyzed). Following are few sample estimations	Avg. daily chain level metrics zipped feed	approx. 26.6 MB
	All premium chains - chain level / daily granularity	folder size approx. 20 GB
	All premium chains - venue level / weekly granularity	folder size approx. 14 GB
Brand Dominance	Zipped	approx. 1.6GB
	UnZipped	approx. 17GB
Migration Trends	Zipped	approx. 150MB
	UnZipped	approx. 1.1GB
Industry Trends	Zipped	approx. 50MB
	UnZipped	approx. 275MB

Q: When configuring a different week aggregation than Mon-Sun, when will the feed be delivered?

A: The weekly feeds are being delivered on Wednesdays. The week's aggregation considers the configured day as the week's starting day.

Q: Which of the Placer feeds supports custom weeks aggregation?

A: The Chain/Venue multi-metrics feed enables custom week aggregation. You can specify the preferred starting day of the week for the weekly aggregation during the feed's configuration.

Q: When are the monthly deliveries of Multi-metrics/Premium export feeds scheduled?

Monthly Multi-metrics and Premium export feeds are being delivered on the 6th of each month.

Q: How is an entity uniquely identified in the feeds and metadata files

A: The unique identification of an entity in the feeds consists of both the entity ID and the entity type. Therefore an ID can appear, for example, once as a venue and once as a complex.
Please note that an entity (venue/complex) included in multiple chains (i.e. parent chain and additional combined chains) will appear multiple times in the feeds and metadata files. In those cases, the unique identifier will be reached by combining the entity ID + entity type + chain ID metadata attributes.

Q: Can there be schema changes?

A: Occasionally, Placer may need to modify the schema of the files, for example, by adding extra attributes included in the metadata file. These additional attributes will be appended as extra columns, and you will receive a sample file along with a 30-day advance notice.