The Olo Engage integration with Spendgo enables brands to dynamically import guest data from Spendgo into Engage. This may include a number of impactful attributes such as a guest’s phone number, loyalty status, favorite store, and reward redemptions.
Once the integration is initiated a brand’s Spendgo member and events data is automatically ingested on an ongoing basis via Engage API endpoints, making it available in Segments, Computed Properties, Automations, and more.
Table of Contents
Spendgo Data in Engage
The below table reflects the scope of the Engage <> Spendgo integration. The actual data passed may vary on a brand-by-brand basis.
| Product/Feature | Support | Behavior |
| GDP Events | ✅ |
Identify Events
Track Events
*The three Reward track events contain the following properties:
|
| Guest Profiles | ✅ |
View All Guest Profile Fields: Properties from the Spendgo identify event such as Spendgo Favorite Store Name and Spendgo Loyalty Status will display in the Custom Fields section. Timeline: Spendgo track events such as Reward Issued and Reward Redeemed, along with their associated properties, will appear in the Guest Timeline. Guest Notes: No Spendgo data currently populates here. Analytics: Spendgo events data will populate the Loyalty Rewards Issued and Redeemed metrics. |
| Segments | ✅ |
Spendgo identify events are available by default under the Custom Properties section in the Select Property dropdown. Spendgo track events can be configured by first creating a Computed Property and then creating a Segment based on it. |
| Computed Properties | ✅ | Spendgo track events such as Reward Redeemed and Spendgo Member Order, along with their associated fields, can be used by default to create Computed Properties. |
| Automations | ✅ |
Spendgo track events can be used in an automation via the Segment Entered or Segment Exited Trigger. To do so:
|
| Host | ⚠️ | Spendgo 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 | ✅ | Spendgo will show up as a Guest Channel in the Guest Book Growth Report. |
Activating the Spendgo Integration
An Olo Implementation Specialist will guide you throughout the setup process. At a high-level, the process will contain the below steps:
- An Olo Implementation specialist will reach out to the Spendgo Integrations team to initiate the data share
- Spendgo configures the automatic, recurring data share
- Olo configures the integration within Engage and performs data validation
- Integration is turned on in Production
- Brand can begin using Spendgo data within the Engage Dashboard
Example Use Cases
There are many ways you can leverage Spendgo data within the Olo Engage ecosystem. Listed below are a few 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: Re-Engage Lapsed Loyalty Guests
Guests enrolled in your loyalty program may be some of your most valuable customers. With Spendgo + Engage, you can launch lapsed guest campaigns to bring your loyalty guests back to the table.
Example Segment: Spendgo Loyalty Status Equals Registered AND Time of Last Visit Date Not Within Last 30 Days
Use Case: Drive Additional Loyalty Sign Ups
Guest data can come from multiple sources and not all guests opted into your marketing channels are loyalty members.
Example Segment: Opted into Email Marketing Equals True AND Spendgo Loyalty Status Does Not Contain Registered
You can then send a one-time campaign or set up a recurring automation to this audience after an event such as a guest Visit.
Use Case: Deliver More Personalized Messaging
Delivering tailored messaging to guests is a great way to develop brand loyalty. One way to do this at scale is to create an automation that delivers specific content based on a guest or order attribute. For example, you could have different email creative sent to guests following an online order depending on whether or not they are a loyalty member.