← All connectors

Misc · Source connector

Pinterest ELT Connector

Extract brings Pinterest misc data into data warehouses and databases for analysis with the rest of your business data. Teams use it to build recurring reporting, investigate changes, and support operational decisions. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.

View setup guide
Pinterest logo

What teams use this connector for

Business performance reporting

Use Pinterest data to monitor recurring activity and investigate meaningful changes over time.

Cross-system analysis

Combine Pinterest data with customer, finance, and operational metrics for consistent reporting.

Data quality monitoring

Compare Pinterest record totals and reporting periods to identify incomplete or unexpected data.

Flexible reporting cadence

Refresh Pinterest reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.

Warehouse and database analysis

Use Extract to make Pinterest misc data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.

Available streams

StreamDescriptionSync mode
ad_targeting_analytics_genderFields include ad_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
adFields include id, ad_account_id, ad_group_id, campaign_id.Incremental
pin_on_boardFields include board_id, id, _singular_extract_timestamp, alt_text.Full refresh
product_group_promotion_analyticsFields include product_group_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_account_targeting_analytics_age_bucketFields include ad_account_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_account_targeting_analytics_genderFields include ad_account_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
campaign_targeting_analytics_placementFields include campaign_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_targeting_analytics_age_bucketFields include ad_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
pin_analyticsFields include pin_id, _singular_extract_timestamp, date, impression.Incremental
ad_targeting_analytics_countryFields include ad_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
campaign_analyticsFields include campaign_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_targeting_analytics_keywordFields include ad_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_analyticsFields include ad_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
campaign_targeting_analytics_keywordFields include campaign_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
campaign_targeting_analytics_countryFields include campaign_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_group_analyticsFields include ad_group_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_group_targeting_analytics_genderFields include ad_group_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
pin_on_board_sectionFields include board_id, board_section_id, id, _singular_extract_timestamp.Full refresh
ad_group_targeting_analytics_countryFields include ad_group_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_targeting_analytics_quiz_resultFields include ad_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
customer_listFields include ad_account_id, id, _singular_extract_timestamp, created_time.Incremental
ad_group_targeting_analytics_keywordFields include ad_group_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
audienceFields include ad_account_id, id, _singular_extract_timestamp, audience_type.Incremental
campaignFields include id, ad_account_id, _singular_extract_timestamp, bookmark.Incremental
keywordFields include ad_account_id, id, _singular_extract_timestamp, archived.Full refresh
catalogFields include ad_account_id, id, _singular_extract_timestamp, catalog_type.Full refresh
ad_account_targeting_analytics_keywordFields include ad_account_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
pinFields include ad_account_id, id, _singular_extract_timestamp, alt_text.Full refresh
ad_account_targeting_analytics_countryFields include ad_account_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_account_analyticsFields include ad_account_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
product_group_promotionFields include ad_group_id, id, _singular_extract_timestamp, bid_in_micro_currency.Full refresh
ad_accountFields include id, _singular_extract_timestamp, country, created_time.Incremental
ad_group_targeting_analytics_age_bucketFields include ad_group_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_targeting_analytics_placementFields include ad_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
campaign_targeting_analytics_creative_typeFields include campaign_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
boardFields include ad_account_id, id, _singular_extract_timestamp, board_pins_modified_at.Full refresh
ad_account_targeting_analytics_placementFields include ad_account_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
feedFields include ad_account_id, id, _singular_extract_timestamp, catalog_type.Incremental
board_sectionFields include board_id, id, _singular_extract_timestamp, name.Full refresh
campaign_targeting_analytics_age_bucketFields include campaign_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
campaign_targeting_analytics_genderFields include campaign_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
ad_group_targeting_analytics_placementFields include ad_group_id, _singular_extract_timestamp, advertiser_id, checkout_roas.Incremental
product_groupFields include ad_account_id, id, catalog_id, feed_id.Incremental
ad_groupFields include id, ad_account_id, campaign_id, _singular_extract_timestamp.Incremental

Data model at a glance

Preview the exported entities and fields for Pinterest.

Open full ERD

ad_targeting_analytics_gender

  • ad_idstring
  • _singular_extract_timestampstring
  • advertiser_idinteger
  • checkout_roasnumber
  • clickthrough_1integer
  • clickthrough_1_grossinteger
  • clickthrough_2integer
  • cost_per_outbound_click_in_dollarnumber

ad

  • idstring
  • ad_account_idstring
  • ad_group_idstring
  • campaign_idstring
  • pin_idstring
  • _singular_extract_timestampstring
  • android_deep_linkstring
  • carousel_android_deep_linksarray

pin_on_board

  • board_idstring
  • idstring
  • _singular_extract_timestampstring
  • alt_textstring
  • board_owner.usernamestring
  • board_section_idstring
  • created_atstring
  • creative_typestring

product_group_promotion_analytics

  • product_group_idstring
  • _singular_extract_timestampstring
  • advertiser_idinteger
  • checkout_roasnumber
  • clickthrough_1integer
  • clickthrough_1_grossinteger
  • clickthrough_2integer
  • cost_per_outbound_click_in_dollarnumber

ad_account_targeting_analytics_age_bucket

  • ad_account_idstring
  • _singular_extract_timestampstring
  • advertiser_idinteger
  • checkout_roasnumber
  • clickthrough_1integer
  • clickthrough_1_grossinteger
  • clickthrough_2integer
  • cost_per_outbound_click_in_dollarnumber

ad_account_targeting_analytics_gender

  • ad_account_idstring
  • _singular_extract_timestampstring
  • advertiser_idinteger
  • checkout_roasnumber
  • clickthrough_1integer
  • clickthrough_1_grossinteger
  • clickthrough_2integer
  • cost_per_outbound_click_in_dollarnumber
+2 more

No verified relationships are available in this schema preview.

Popular destinations

Commonly paired with Pinterest in Extract workflows.

Why Extract for Pinterest

  • Rust-native performanceUse Rust-native data movement to refresh Pinterest reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
  • Full run transparencyInspect Pinterest API activity, execution steps, and timing in Extract's run-level logs when data needs review.
  • ELT + Reverse ETL in oneCombine Pinterest data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.

Frequently asked questions

How does Extract handle incremental and full Pinterest syncs?

An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Stream schemas define full refresh, incremental changes, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.

Can I backfill historical Pinterest data with Extract?

Historical coverage for Pinterest: Initial Backfill (DAYS) (backfill): On the very first load of a stream, that has no set cursor, how far back do we want to pull records. Use the setup guide and run details to confirm the available source records and selected settings.

How can teams monitor Pinterest data quality and freshness?

Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Pinterest API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.

How often can Extract sync data from Pinterest?

Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.

What does the Pinterest data model look like in the destination?

The Available streams table describes the datasets Extract can read from Pinterest. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.