One of the best ways to help us improve the accuracy of the Pilgrim SDK and where we think devices are located is by providing feedback about a user’s visit. The more feedback we get, the smarter, faster and more accurate visits from the Pilgrim SDK become. We provide the following methods to provide feedback.
Confirm/Deny a Visit
You can easily confirm whether a visit is accurate or not (and why). All you need is the visit id from the original visit.
The available feedback options are:
|FSQPVisitFeedback.confirm||The visit was at the correct venue.|
|FSQPVisitFeedback.falseStop||The user did not stop anywhere. If you are unsure, use
|FSQPVisitFeedback.wrongVenue||The wrong venue was detected. A Foursquare venue id can optionally be included to identify the correct venue.|
|FSQPVisitFeedback.deny||Generic feedback that something was incorrect. If your feedback interface doesn’t allow for
|VisitFeedback.CONFIRM||The visit was at the correct venue.|
|VisitFeedback.FALSE_STOP||The user did not stop anywhere. If you are unsure, use
|VisitFeedback.WRONG_VENUE||The wrong venue was detected. A Foursquare venue id can optionally be included to identify the correct venue.|
|VisitFeedback.DENY||Generic feedback that something was incorrect. If your feedback UX doesn’t allow for
An example providing
wrongVenue feedback with the correct venueId:
A more robust example of how you might add a feedback drawer to easily allow users to confirm or deny the accuracy of their visit on iOS can be found here.
Check-in at a (Foursquare) Venue
If you know a device is at a specific Foursquare venue, irrespective of receiving a Pilgrim Visit, you can also inform Pilgrim by providing the Foursquare venue ID:
Check-in at a (Partner) Venue
For partners that have already harmonized their venues with Foursquare, irrespective of receiving a Pilgrim Visit, you can also inform Pilgrim that a device is at a venue by providing the partner’s harmonized venue ID: