Integrations & data.
Retrics connects to Shopify read-only, reads your order and customer history to compute retention, and keeps it in sync. Here is exactly what it touches, how often, and how to take your data and leave.
How the connection works
Retrics installs from the Shopify App Store as a standard embedded app. When you approve the install, Shopify issues an access token scoped to your store — you never paste API keys or hand us a password, and you can revoke the token from your Shopify admin at any time.
The connection is read-only. Retrics requests read scopes for orders, customers, and products so it can compute retention, cohort, and lifecycle analytics. It does not request write access to your storefront, your theme, your checkout, or your customers, and it cannot place, edit, or refund an order.
Because Retrics reads customer records, the connection operates under Shopify's protected customer data requirements. We access only the fields the analytics need, apply data-minimization and retention limits, and honor Shopify's mandatory customer-redaction and shop-redaction webhooks.
What syncs
Orders: order and line-item history, timestamps, totals, discounts, and fulfillment status — the backbone of cohort, repeat-rate, and lifetime-value math.
Customers: the customer record tied to each order, so Retrics can build a per-customer purchase timeline and score lapse probability. Email addresses are hashed for matching and internal identifiers; we do not read payment credentials or card data.
Products: product and variant records, used to compute cross-sell and reorder signals and to give drafts real product context.
Retrics does not read your theme, your app settings for other apps, your staff accounts, or anything outside the read scopes listed above.
How often it syncs
On connect, Retrics runs a one-time historical backfill so your cohorts and lifetime-value curves are complete from day one rather than starting empty.
After that, new and changed orders and customers flow in continuously through Shopify webhooks, so the dashboard reflects your store in near-real-time. A scheduled reconciliation sweep runs regularly to catch anything a webhook may have missed and to keep the two systems in agreement.
Model scores — drift detection and lapse probability — recompute on a rolling schedule against your store's own history, so risk flags stay current as behavior shifts.
Export & CSV
Your data is portable. You can export cohorts, the recovered-revenue ledger, and customer-level retention scores to CSV from the dashboard, so the numbers can live in your own spreadsheets, BI tool, or warehouse.
Exports reflect what Retrics computed from your store; they are yours to keep and use, and they persist even if you later disconnect.
ESP & Klaviyo handoff
Today, Retrics drafts win-backs, reorder nudges, and cross-sells and holds them for your one-click approval — it does not send on its own, and it does not yet push to your email platform.
Direct handoff to your existing stack is on the roadmap: a Klaviyo and general ESP integration that lets you route an approved draft — and the audience behind it — straight into the tool you already send from. It is planned for the Scale tier and marked "soon" on the pricing page; it becomes available the day it ships, at no change to the tier price.
Webhooks & API roadmap
Retrics already consumes Shopify's inbound webhooks to stay in sync and to honor mandatory data-redaction events.
Outbound webhooks and a public API — to pipe retention scores, risk flags, and ledger entries into your own systems — are on the roadmap for the Scale tier, alongside the ESP integrations, and are marked "soon." The Concierge tier adds custom integrations built for your specific stack.
We will document scopes, payloads, and rate limits before these ship. Until then, CSV export is the supported path for getting Retrics data into other tools.
Disconnecting
You can disconnect Retrics at any time by uninstalling the app from your Shopify admin, which immediately revokes our access token — Retrics can no longer read your store the moment you do.
On disconnect we stop syncing and begin removing your store's data from production systems. Shopify's shop-redaction webhook triggers erasure on Shopify's schedule, and in the ordinary course we remove your store's data within 30 days. Anything you exported to CSV beforehand remains yours.
Questions
Anything about scopes, sync, or exports: hello@retrics.ai.