DatriseAI-first ETL

Appfollow to Metabase Integration

AI-first ETL from Appfollow into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Appfollow into Metabase

Datrise syncs Appfollow's reviews, ratings, app rankings, keywords, replies, and store listings into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Appfollow: App store review and rankings monitoring.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Appfollow entities map to Metabase

Appfollow entityMetabase objectNotes
reviewsappfollow_reviewsid PK · custom fields → flattened columns for the question builder
ratingsappfollow_ratingsid PK · linked to appfollow_reviews
app rankingsappfollow_app_rankingsid PK · linked to appfollow_reviews
keywordsappfollow_keywordsid PK · linked to appfollow_reviews

FAQ

How does Datrise handle Appfollow's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Appfollow to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Appfollow to Metabase 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.