DatriseAI-first ETL

Smaily to Spotfire Integration

AI-first ETL from Smaily into Spotfire. Governed entities, incremental sync, typed landing tables.

How Datrise loads Smaily into Spotfire

Datrise syncs Smaily's subscribers, campaigns, lists, autoresponders, email events, and segments into Spotfire as warehouse tables or in-memory data for Spotfire analyses. Flexible or custom fields land in flattened columns for visualizations, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables or in-memory data, so re-runs update only what changed. Date-partitioned facts. Spotfire can load data in-memory, so Datrise keeps the backing tables incremental so analyses refresh without full reloads.

Ideal for interactive analytical visualization and data science.

Endpoints

Smaily: Email and SMS campaigns with subscriber segments.

Spotfire: Visual analytics platform for interactive dashboards and data science workflows.

How Smaily entities map to Spotfire

Smaily entitySpotfire objectNotes
subscriberssmaily_subscribersid PK · custom fields → flattened columns for visualizations
campaignssmaily_campaignsid PK · linked to smaily_subscribers
listssmaily_listsid PK · linked to smaily_subscribers
autoresponderssmaily_autorespondersid PK · linked to smaily_subscribers

FAQ

How does Datrise handle Smaily's custom fields in Spotfire?

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

How does the Smaily to Spotfire sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables or in-memory data.

Related pipelines

Early access

Connect Smaily to Spotfire 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.