Some of the relevant terms used in this section of our GDP technical documentation are listed below with brief definitions.
- Source: The originating platform capturing guest interactions, for example: POS, Mobile, or Loyalty Provider
- Destination: The downstream channel receiving guest Identity and Track event data
- Integration: The routing between GDP and source data platforms
- API: Application Programming Interface, or web service
- Source Token: The vendor specific token provided by Olo for usage in the Authentication process
- JWT: JSON Web Token, a secure method to transmit information between parties as a JSON object
- Semantic Events: Off-the-shelf Webhook events available for brand usage
Data ingestion to GDP can be accomplished through Integrations with Sources that brands already utilize. These off-the-shelf configurations allow brands to seamlessly aggregate guest data points and route them to appropriate Destinations.
Data Sources and Destinations
GDP integrates guest data Sources, resolves Identities, then stores and sends data to Destinations for brands to take action.
Diagram 3: Source and Destination routing through the GDP
You can find examples of Olo Partners and integrations here, and we develop new integrations on a regular basis. For additional details, please connect with a member of Olo’s Solutions Consulting or Technical Specialists teams.
GDP API’s
Adding data to GDP and viewing stored guest data can be completed through leveraging off-the-shelf API calls. Primarily, customers can add or modify guest identifiers and interactions via Identify and Track API calls. Customers can view this information for segments of guests using Search and Events API calls. Additionally, Webhooks are supported as a means for customers to be notified when certain interactions pass through GDP.
| Use Case: Adding Guest Data | |
|---|---|
| Background |
A brand is seeking to add guest data to the GDP, including Name, Email, Loyalty Tier, and Subscriber Status. Additionally, the brand is looking to track interactions such as Order Completed, Survey Completed, and Reward Redeemed. |
| Considerations |
Each guest data point is considered an Identifier or Custom Property to GDP. Interactions can be tracked and associated with individual Identifiers. |
| Solution |
Call the Identify API to add relevant guest data, and call the Track API to store brand interactions per guest. |
| Use Case: Viewing Guest Data | |
|---|---|
| Background |
A brand is seeking to view data stored in GDP, including general guest information, such as Name, Email, and Loyalty ID. Additionally, they would like to view guest data associated with Order Completed Track events such as Data Source (POS, WiFi, etc.) and Timestamp for completed transaction. |
| Considerations |
The brand has previously leveraged the Identify and Track APIs in order to store relevant guest data. |
| Solution |
Call the Search API to view relevant guest profile information, and call the Events API to view previous guest interactions and associated transaction data. |
More documentation about Global Configuration Settings, Authentication, OAuth 2.0, Webhooks, and our Identify, Track, Search, and Events APIs is coming soon. If you have specific questions about them, please reach out to your Olo representative and they will put you in contact with the appropriate party.