Data Collection
Data Collection defines how the Company sends operational data to Loyal Guru. It is the setup layer for customer profiles, product and store catalogs, carts, custom events, and files used by campaigns.
Use Cases
| Use Case |
|---|
| -> Configure API access so the POS or e-commerce system can send carts to the Streaming API. |
| -> Upload product or store files during onboarding. |
| -> Import external segment attributes used by Audiences and campaign conditions. |
| -> Review which ingestion channel should be used for each type of data. |
Collection methods
| Method | Best for | Notes |
|---|---|---|
| Streaming API | Real-time carts, customers, products, stores, custom events | Preferred for operational integrations that need up-to-date evaluation. |
| File Management | Bulk imports and scheduled file-based processes | Useful during onboarding or when the source system cannot integrate through API. |
| Connectors | External platforms and data tools | Depends on connector availability and Company setup. |
| Manual Owner App updates | Small operational corrections | Not recommended as the primary sync method for high-volume data. |
Source-of-truth rule
Choose one operating model per dataset. If products, stores, or Customer attributes are updated from multiple sources without governance, campaigns can evaluate against inconsistent data.
Configuration
Data collection setup is usually defined during technical onboarding. Product and store catalog operations are documented under Company Data, and Customer data operations are documented under Customers.