The Olo Engage integration with Sparkfly's POS module enables brands to automatically supplement guests' order data with loyalty information from Sparkfly. This may include a number of valuable attributes such as a guest’s loyalty status and Sparkfly Member Identifier.
Once the integration is initiated a brand’s Sparkfly POS data is ingested on an ongoing basis via Engage API endpoints, making it available in Segments, Computed Properties, Automations, and more.
Table of Contents
Sparkfly POS Data in Engage
The below table reflects the scope of the Engage <> Sparkfly POS integration. The actual data passed may vary on a brand-by-brand basis.
| Product/Feature | Support | Behavior/Description |
|---|---|---|
| GDP Events | ✅ |
Identify Event Fields
Track Event
|
| Guest Profiles | ✅ |
View All Guest Profile Fields: No specific Custom Fields are set from this integration. However, any Computed Properties based on the Order Completed track event that are then used in a Segment will display in the Custom Fields section. Timeline: The Order Completed track event, along with its associated properties, will appear in the Guest Timeline. Guest Notes: No Sparkfly POS data currently populates here. Analytics: Identified Orders will populate the Total Olo Orders Completed metric. |
| Segments | ✅ |
The Order Completed track event can be used to create a Computed Property, which can then be used to create a Segment. |
| Computed Properties | ✅ |
The Order Completed track event, along with its associated properties, can be used by default to create Computed Properties. Example: Count of Order Completed events where Source equals Sparkfly in the Last 30 Days |
| Automations | ✅ |
Any track event can be used in an automation via the Segment Entered or Segment Exited Trigger. To do so:
The Sparkfly generated Order Completed track event can also be enabled as a “default trigger” on a program-by-program basis by configuring a Dynamic Trigger. |
| Host | ⚠️ |
Sparkfly data is not directly visible in or used by Host. However, a Segment can be created using a Smart Property and then turned into a Smart Tag, which is visible in Host. |
| Reporting | ✅ |
Sparkfly data is available in a number of additional locations including:
|
Activating the Sparkfly POS Integration
An Olo Implementation Specialist will guide you throughout the setup process. At a high-level, the process will contain the below steps:
- Reach out to your Sparkfly CSM to initiate the data share with Engage, making sure to cc your Olo Implementation Specialist.
- Your Sparkfly representative may ask a few follow up questions before enabling the integration.
- Sparkfly configures the automatic, recurring data share.
- Olo configures the integration within Engage and performs data validation in a test environment.
- Integration is turned on in your Engage production environment.
- Begin using Sparkfly data within the Engage Dashboard.
Example Use Cases
There are many ways you can leverage Sparkfly POS data within the Olo Engage ecosystem. Listed below are a couple of common use cases to consider.
Note: The exact names of fields/properties listed in the below examples may differ from what is available in your account.
Use Case: Target On-Premise Loyalty Guests
When a guest in your loyalty program completes an order on-premise using their loyalty credentials, that information is passed to Engage via Sparkfly. You can automate the sending of a post-visit email to these guests using the relevant Trigger and Pre-Entry Filter.
Example Automation: Trigger When a guest has Order Completed | Pre-Entry Filer Event by Source contains ‘sparkfly’
Use Case: Create Hyper-Personalized Campaigns
Combine data from Sparkfly and Engage to delivered tailored messaging that drives guest engagement. For example, target valuable loyalty guests who have previously ordered in-store but have a higher likelihood to churn.
Example Segment: Order Completed - Sparkfly in Last 365 Days and Six Month Churn Risk greater 60