Data
Data is the foundational layer of Loyal Guru. It turns commerce activity into usable loyalty intelligence: the platform knows what the company sells, where each interaction happens, who the customer is, and which events should update loyalty, audiences, gamification, and analytics.
For retailers, this solves a common operational pain: campaigns cannot be targeted, measured, or automated if products, stores, customer profiles, and event history live in disconnected systems. Loyal Guru centralizes that data so commercial teams can build promotions and audiences on real purchase signals instead of manual exports.
Every promotional rule, audience filter, and gamification condition runs against the data stored here.
What you can manage in Data
| Area | What it covers | Why it matters |
|---|---|---|
| Customers | Customer profiles, cart history, loyalty balance, tier status, custom events, calculated attributes, consents, and behavioral history | Builds the unified customer view used by audiences, personalization, support, and loyalty operations |
| Company Data | Product catalog, store locations, product categories, store categories, and promotions master data | Defines the scope that campaigns can target: SKU, category, store, region, or channel |
Data flow overview
Use Cases
| Use Case |
|---|
| → Upload the full product catalog so discount and points campaigns can scope to specific SKUs, brands, or categories. |
| → Register store locations so promotions can be limited to specific regions, stores, store groups, or channels. |
| → View a customer's full transaction history, points balance, and tier progression from a single profile. |
| → Use calculated attributes (e.g. "average cart in last 90 days") as audience filter conditions. |
| → Track custom events (e.g. "app login", "product review submitted") to trigger points campaigns. |
| → Monitor customer data quality — identify profiles with missing fields before they affect segmentation. |
| → Export or push customer and loyalty events to CRM, ESP, BI, or fulfillment systems through Webhooks & Connectors. |
How It Works
Data is ingested in real time via the Streaming API and surfaced in the Owner App for review and management:
- Company Data is uploaded via bulk import or the Streaming API, then referenced automatically by every campaign rule.
- Customer profiles are created and enriched at each interaction — cart, custom event, loyalty action, consent update, or manual support action.
- Cart events update purchase history, trigger discount and points evaluation, feed challenge progress, and power ROI measurement.
- Custom events let external systems send non-purchase behavior, such as app activity, product registration, survey completion, or partner challenge progress.
- Calculated attributes are derived automatically from event history, stored on the customer profile, and reused in audiences, tiers, personalization, and reporting.
Configuration
| Sub-section | Owner App path |
|---|---|
| Customers | Customers |
| Company Data | Company Data |