Foursquare Visits for Offline Conversions combines the best of two legacy products - Foursquare Offline Conversions Data (OLC) and Factual Measurement Data (MD). This new and improved integrated product offers more scale and precision when measuring visits associated with a campaign in partner platforms such as DSPs, campaign management systems, and marketing intelligence platforms. These platforms in turn use that data in their attribution methodology and provide reporting on store visit conversions. Visits are sent daily with a 2-3 day lag.
Our methodology is designed to ensure accuracy, sound decision-making, and actionability. Our goal is to provide you with the context to understand, interpret, and activate your data.
This document describes the file format details of Offline Conversions for any platforms receiving this data whether through an API integration or s3.
For s3 integration partners, Foursquare delivers Offline Conversions on a daily cadence as a CSV compressed file (partitioned by day) containing all store visit data that was processed on that day.
|Device ID||Device ID||24f4dc96-3a90-4950-858c-60410f436da|
|Timestamp||Date and timestamp in UTC, granular to the hour. Format: yyyy-mm-ddThh:mm:ss.000Z||2020-10-20T15:00:00.000Z|
|Venue ID||Either the supplied location ID or the Foursquare ID of this venue (store)||556f7a12bd6a75a9903bddb2|
|Dwell||Dwell time (aka duration) in minutes||20|
|Postcode||Postcode or equivalent (zipcode in US)||10003|
|City||City, town, or equivalent||New York|
|State||State, province, territory, or equivalent||New York|
Updated 11 months ago