DatriseAI-first ETL

Pinterest Ads Holistics

AI-first ETL from Pinterest Ads into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Pinterest Ads into Holistics

Datrise syncs Pinterest Ads's records, events, and configuration objects into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Pinterest Ads: SaaS or API data source for analytics and warehouse sync.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Pinterest Ads entities map to Holistics

Pinterest Ads entityHolistics objectNotes
recordspinterest_ads_recordsid PK · custom fields → flattened columns for the modeling layer
eventspinterest_ads_eventsdate/time dimensions events
configuration objectspinterest_ads_configuration_objectsid PK · linked to pinterest_ads_records

FAQ

How does Datrise handle Pinterest Ads's custom fields in Holistics?

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

How does the Pinterest Ads to Holistics sync stay up to date?

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

Related pipelines

Early access

Connect Pinterest Ads to Holistics 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.