List of Use Cases

Native Reward Redemption Drive: Uses in-app touchpoints and push notifications to encourage members to use their points for rewards, increasing benefit usage.
Onsite Guest-to-Member Conversion: Leverages web widgets to capture anonymous traffic and convert visitors into loyalty members using immediate sign-up incentives.

Use Case 1: Native Reward Redemption Drive

Summary: This use case focuses on boosting the redemption of loyalty benefits by alerting members through native app channels when they have reached a reward threshold.

Trigger and Eligibility

Trigger Event: Tier Upgraded or a specific point threshold reached in TRIFFT.
Eligibility: Active members with sufficient points to claim at least one reward. Exclude members who have recently redeemed a voucher to avoid over-communication.
Timing: Immediate push notification upon the event, followed by a persistent in-app message in the Member Portal.

Execution Flow

Event Fires: A member completes a purchase, and their status is updated to reflect new points or a tier change in TRIFFT.
TRIFFT Selects Audience: The system identifies members who qualify for a new reward based on current member state and segment rules.
Loyalty Context: TRIFFT pulls the member's specific reward eligibility and point balance from internal properties.
Message Delivered: A native push notification is sent, and a "Recommended Reward" is highlighted within the TRIFFT App or Web Portal.
Customer Action: The member taps the notification, views the reward, and clicks "Redeem" directly in the app.
Measure Impact: Track the redemption rate of the specific coupons and the increase in app engagement sessions.

What You Need

Data: Member loyalty events, points earned, current tier and point properties, and communication consent.
Content: Personalized push copy, reward creative, and a CTA destination pointing to the app's Reward Gallery.
Rules: Frequency caps for push notifications and suppression of members with pending unused vouchers.

Measurement

Primary KPI: Redemption rate of loyalty benefits.
Secondary: App engagement frequency and push notification click-through rate.
Testing: A/B test push notification copy and different point-value reward highlights.

Use Case 2: Onsite Guest-to-Member Conversion

Summary: Converts web store visitors into loyalty members by surfacing the benefits of the program through native web touchpoints at critical moments of the customer journey.

Trigger and Eligibility

Trigger Event: Onsite automation based on session duration or exit intent within the TRIFFT Web Widget.
Eligibility: Anonymous visitors or logged-out users. Exclude existing members who are already logged in.
Timing: Displayed after a 30-second delay or upon detection of exit intent.

Execution Flow

Event Fires: A guest visitor meets the onsite messaging trigger criteria on the brand's website.
TRIFFT Selects Audience: The Web Widget identifies the visitor as a non-member who has not yet opted into the program.
Loyalty Context: The system selects a welcome reward or incentive, such as "Sign up for 500 bonus points."
Experience Delivered: A native pop-up or web widget is personalized with the sign-up offer and displayed on the current page.
Customer Action: The visitor enters their details, joins the program, and is immediately redirected to the TRIFFT Web Portal.
Measure Impact: Evaluate the conversion rate from guest to member and the initial purchase rate of new members.

What You Need

Data: Anonymous session events and basic profile properties for the sign-up form.
Content: Welcome offer copy, brand creative, and a CTA leading to the registration page.
Rules: Frequency cap of one display per 24 hours to prevent a disruptive browsing experience.

Measurement

Primary KPI: Repeat purchase rate, specifically the first-to-second purchase conversion for new members.
Secondary: Opt-out rates and website session engagement.
Testing: A/B test different sign-up incentives, such as an instant discount versus bonus points.

Use Case 3: Geolocation: digital wallet passes vs mobile apps

Geolocation can be used to surface a digital wallet pass or trigger an action in a mobile app when a customer is near a venue. However, the timing and delivery are controlled largely by the customer's device and operating system. Geolocation should therefore be treated as an optional engagement channel, not as a reliable check-in mechanism or a time-critical trigger.

Practical takeaway: Do not design a customer journey that depends on an immediate geolocation trigger. Treat it as an eventual, best-effort action that may happen within a few minutes when the required permissions and device conditions are in place.

Digital wallet passes

Venue locations can be added to Apple Wallet and Google Wallet passes. When a customer is near one of those locations, the operating system may surface the relevant pass on the lock screen.

What is possible

Associate venue locations with a wallet pass.
Surface the pass when the customer remains close to a configured venue.
On Apple Wallet, include up to 10 relevant locations in the pass when it is issued.

Limitations

We cannot configure or guarantee the activation radius or timing.
The result varies by platform, device, battery level, connectivity, enabled services and customer permissions.
For loyalty cards and coupons, Apple Wallet typically requires the customer to remain within close proximity—often less than 100 metres—for several minutes. This is indicative, not guaranteed.
Google Wallet does not publish its exact distance or time thresholds. Its proximity behaviour should be treated as a black box.
Approximate or restricted location access may prevent a Google Wallet proximity notification from appearing.
The content shown to the customer is controlled by Apple or Google. Apple generally surfaces the pass itself, while Google may display limited contextual information from the pass.
A proximity activation does not send an event to TRIFFT. We do not know that the customer is at the venue until they perform an observable action, such as scanning the pass.

Mobile apps

A mobile app provides more flexibility than a wallet pass. If the operating system detects a configured geofence, it may wake the app briefly. The app can then perform a programmed action—for example, display a local notification or call the backend so that a push notification or another workflow can be initiated.

What is possible

Detect that an eligible app user has entered a configured venue area.
Call the backend when the geofence is triggered.
Add the customer to a location-based segment or workflow.
Send a relevant message or offer, subject to the customer's permissions and successful notification delivery.

Limitations

The customer must have the app installed and grant the required location permissions. Background or Always access, and in some cases precise location, may be required.
The operating system may suspend, deprioritise or offload an app that has not been used recently. There is no universal inactivity period: it may range from a few weeks to several months depending on the device and usage.
Low battery, disabled Wi-Fi, GPS or Bluetooth, restricted background activity and notification settings can delay or prevent the trigger.
Geofence detection and push delivery are not guaranteed, even when the message has been accepted by Apple or Google.
This is expected to reach only a subset of the active app audience. As a practical planning assumption, approximately 10–20% of active users may have the necessary permissions and device conditions.

Recommended approach

Use geolocation to add contextual, location-based engagement to an existing customer journey, but do not make it the only way to complete an important action.

For reliable venue check-ins, redemptions or other actions that must happen immediately and be recorded by TRIFFT, use an explicit customer action such as scanning a QR code or a digital wallet pass. QR codes are generally the simplest and most dependable option because the trigger happens at the venue and does not depend on background location detection.