DatriseAI-first ETL

Recharge Looker

AI-first ETL from Recharge into Looker. Governed entities, incremental sync, typed landing tables.

How Datrise loads Recharge into Looker

Datrise syncs Recharge's subscriptions, charges, customers, plans, and churn events into Looker as governed warehouse tables with LookML-ready naming. Flexible or custom fields land in flattened columns (nested fields expanded for modeling), and timestamps such as created, updated, and status changes are typed as date/time dimension columns.

Sync is incremental: Datrise uses incremental refresh of the underlying warehouse tables Looker explores, so re-runs update only what changed. Date-partitioned fact tables for PDT performance. Looker models live in LookML on top of SQL, so Datrise lands clean, stable column names rather than churn that would break your views.

Ideal for governed, version-controlled BI on a warehouse.

Endpoints

Recharge: Subscription commerce for Shopify and recurring billing.

Looker: Google Cloud BI with LookML semantic models and governed dashboards.

How Recharge entities map to Looker

Recharge entityLooker objectNotes
subscriptionsrecharge_subscriptionsid PK · custom fields → flattened columns (nested fields expanded for modeling)
chargesrecharge_chargesid PK · linked to recharge_subscriptions
customersrecharge_customersid PK · linked to recharge_subscriptions
plansrecharge_plansid PK · linked to recharge_subscriptions

FAQ

How does Datrise handle Recharge's custom fields in Looker?

Flexible values are stored as flattened columns (nested fields expanded for modeling), so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Looker types.

How does the Recharge to Looker sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the underlying warehouse tables Looker explores.

Related pipelines

Early access

Connect Recharge to Looker the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.