Customer Data Platform (CDP): one customer, every channel

It is Qurable's CDP and the data module of its platform: one profile per member with their identity, consents, purchases and audiences, ready at checkout for rules, journeys and the reward decision. Its AI agents automate decisions you set up in natural language, with human approval when required.

A CRM stores who the customer is and builds campaigns for later. A CDP like Agentic Data Platform recognizes the member at checkout, decides their reward in ~150 ms and records every point in a hash-chained ledger. They work together: Qurable connects to the CRM by member ID and sends back every purchase and redemption.

No. It integrates with them by member ID and sends them every program event. It adds what they lack: the profile ready at checkout, and the balance and tier recorded in a ledger.

Through the API, and it's already live at clients with Salesforce, Microsoft Dynamics, Braze, Klaviyo, Insider One, Shopify, VTEX, Tiendanube, Oracle, Napse, Pomelo, MODO, Mercado Pago, Stripe, Flexibility, Wibond, WhatsApp and Twilio. Every event goes out through a signed webhook and in a daily export to your data warehouse. Email and WhatsApp are sent from Qurable or from your messaging platform. Implementation takes 1 to 3 months.

Three: the anonymous customer at checkout, every system with its own version of the member, and audiences that arrive after the purchase is over. With one profile ready at checkout, everyone sees the same data and the reward is personalized in the moment.

It means recognizing the same person in your stores, ecommerce and app, and across every brand in a group, with one profile. On Qurable, each member has one record with all their identifiers (phone, email, member ID and QR code), their consents and their full purchase and redemption history. Without it, every channel treats the same customer as a stranger.

In store, members identify with a QR code that changes every 30 seconds or with an Apple Wallet or Google Wallet pass, in under 50 ms (p95, server-side). Online, they sign in to their account. Both paths lead to the same profile, so an in-store purchase adds to the same balance as an online one and the reward is decided with their full history. Your team can look them up by phone, email, ID or QR code in Qurable Manager.

Yes. In-store (POS) and online purchases reach the same member profile, so journeys, offers, tiers and the reward at payment are decided with the member's full history, not just one channel's.

Yes. A group can run one program with one customer base for all its brands, in store and online. TRIBU, by Grupo Dabra, brings together Dexter, Moov and Stock Center and passed 1 million members in its first year. If each brand prefers to keep its own program, the programs connect as a coalition with Engagement Ecosystem.

Profile audiences trigger AI Engagement Journeys: you describe the goal, the AI builds the campaign and simulates it on real data from the last 7 days, and nothing is sent without your approval. Campaigns go out by email or WhatsApp.

Qurable identifies the member in under 50 ms (p95, measured server-side) and decides the reward in ~150 ms, within checkout. The purchase reaches the profile in under 1 s.

What the program needs: identifiers, per-channel consent, attributes, purchases, redemptions, tier changes and audiences. Web browsing and other external data are linked by ID, not copied.

Yes. With name, ID number, email and phone pseudonymized with a hash, campaigns, segmentation, rules, tiers and analytics keep working. Messages go out through your own providers.