Use Cases Technical Customization
This technical documentation details the internal data logic and customization patterns for the TRIFFT Standalone ecosystem, focusing on how the system manages loyalty cycles without external third-party orchestration.
Document Details
| Integration | TRIFFT Loyalty |
|---|---|
| Audience | Technical implementer / Solutions engineer / Marketing ops |
| Goal | Document internal data flow, state management, and native customization patterns |
Architecture
In a standalone configuration, TRIFFT manages the entire loop from interaction to reward. Member actions on native touchpoints (Mobile App, Web Portal, or Onsite Widgets) trigger internal events in the loyalty engine. The engine updates the member’s profile, processes segment membership, and recalculates point ledgers. Finally, the updated state is rendered back to the member via native push notifications or dynamic UI updates in the app and web portal.
Identifiers and Consent
- Primary identifier: The Email address serves as the unique login key, while a system-generated UUID or Support ID is used for internal database referencing and customer support lookups.
- Consent mapping: TRIFFT is the primary source of truth for all consent types, including mandatory Legal Consents (T&Cs) and optional Marketing Consents (Push/SMS/Email).
- Data ownership: TRIFFT is the authoritative owner of all member attributes, transaction history, and loyalty states.
Data Mapping Table
| Concept | TRIFFT (Backend) | TRIFFT Surfaces (App/Web) | Notes |
|---|---|---|---|
| Customer identifier | support_id / member_id | Email / support_id | Displayed in member settings for support. |
| Tier | tier_name | Tier Badge | Visual indicator updated in real-time. |
| Points balance | points_balance | Wallet View | Integer value synced across all native views. |
| Coupon state | member_coupon_id | Coupon | Tracks "Available," "Claimed," or "Used" status. |
| Custom Data | member_attributes | Personalized Feed | Powers logic for "Favorite Store" content. |
Standard Patterns
- Internal Event Sync: Triggering native push notifications or onsite pop-up widgets immediately after a member completes a specific action, such as reaching a point milestone.
- Attribute-Driven Personalization: Updating Member Attributes via API or CSV import to immediately change the visibility of News or Deals for specific segments.
- Referral Loop: The system generates a unique referral URL for a member, tracks its usage by new sign-ups, and automatically issues bonus points to the original referrer.
Webhook/API Checklist
- Security: Use Secret API Keys for any external data injections into the member attribute table and ensure all traffic is encrypted.
- Reliability: Utilize the internal Points Ledger to audit and reconcile any points issued through manual adjustments or bulk imports.
- Observability: Monitor the Support Center and Compliance Logs to verify the success of data updates and privacy requests.
- Testing: Use "Test Members" within the Cockpit to preview how dynamic segments and deals will appear in the app before going live.
Customization Examples
- Tier-Based Discovery: Configure News articles to only be visible to "VIP" segments, ensuring exclusive content is protected.
- Hyper-Local Onsite Targeting: Use the
favorite_locationattribute to trigger a specific Web Pop-up when a member visits the website, promoting a store-specific event. - Automated Member Enrichment: Push data from an external POS (via API) into Custom Parameters to trigger a "Complete Your Profile" push notification.
Updated 4 days ago
Did this page help you?