📘

As of January 31, 2023 Foursquare changed the name of our existing Pilgrim SDK product to Movement SDK. This change comes as Foursquare looks to align our product names closer to their functionality and bring the Pilgrim SDK closer to our other family of products.

If you are already using the [Pilgrim SDK](https://docs.foursquare.com/developer/docs/pilgrim-sdk-overview), you may continue to do so or elect to upgrade to the Movement SDK documented within this section.

### **SDK Data Usage**

The data sent to Foursquare servers on every “stop” detected by the SDK.

- [View Data Usage](https://docs.foursquare.com/developer/docs/movement-sdk-data-usage)

### **Category Schema**

The Foursquare Venue Category Hierarchy used by the Movement SDK.

- [View Category Schema](https://docs.foursquare.com/developer/docs/movement-sdk-categories)

### **Chains Schema**

The list of the most common Foursquare Venue Chains in the United States.

- [View Chain Schema](https://docs.foursquare.com/developer/docs/movement-sdk-chains)

### **Visits Data Schema**

The visits data Foursquare sends via the Amazon S3 integration.

- [View Visits Data Schema](https://docs.foursquare.com/developer/docs/movement-sdk-visits-data-schema)

### **Geofence Data Schema**

The geofence data Foursquare sends via the Amazon S3 integration.

- [View Geofence Data Schema](https://docs.foursquare.com/developer/docs/movement-sdk-geofence-data-schema)