Proximity Set Format/Upload

Foursquare's Proximity Designer provides complete access to our Global Places Data to create geofences based on millions of businesses and points of interest around the world. However, many customers have campaigns that require custom data that may not be easily accessible in Foursquare's global places data.

Foursquare currently supports uploads of two different types of files: (1) geocoded points (latitude, longitude) and (2) custom polygons. Note that polygon uploads are now supported in both Audience Designer and Proximity Designer.

Additionally, Foursquare does not accept lists of addresses without geocoded latitude and longitude coordinates. Please contact Partner Services if you need geocoding services.

To upload custom location data for use in Proximity or Audience, follow the instructions below.

Point Upload (lat/long) Skip link to Point Upload (lat/long)

Uploaded files must contain valid latitude and longitude coordinates for each location. Acceptable file formats include CSV, TSV, and Excel. The easiest way to start is to download one of our sample templates and modify those.

Download Sample Templates here: CSV, TSV, or Excel

latitude longitude name
34.073011 -118.376097 The Coffee Bean and Tea Leaf
34.098155 -118.329646 Groundwork Coffee Company
34.003545 -118.484834 Peet’s Coffee and Tea
34.008187 -118.491283 Cora’s Coffee Shop

File Format Checklist Skip link to File Format Checklist

Post-Upload Guidelines Skip link to Post-Upload Guidelines

Polygon Upload Skip link to Polygon Upload

Note: Polygon upload now works in both Audience Designer and Proximity Designer. To get access to this feature, please contact Partner Services.

Uploaded files must contain valid polygon data, formatted as WKTs or GeoJSON objects. The easiest way to start is to download one of our sample templates and modify those.

Download Sample Templates here: WKT, GeoJSON

WKT File Format Checklist Skip link to WKT File Format Checklist

We recommend using WKTs in your polygon file uploads.

name (optional) polygon
polygon 1 POLYGON((lng1 lat1, lng2 lat2, lng3 lat3, lng4 lat4, …))
polygon 2 POLYGON((lng1 lat1, lng2 lat2, lng3 lat3, lng4 lat4, …))

GeoJSON File Format Checklist Skip link to GeoJSON File Format Checklist

Polygon upload also supports GeoJSON data. Valid GeoJSON must represents a FeatureCollection where each feature is a Polygon with: