Advertising
Pinterest Ads schema
SightShark syncs Pinterest Ads into a data warehouse you own. It creates 41 tables holding 348 fields, refreshed daily. Advertiser, campaign, ad group and promoted pin history, reports at every level, keyword and product group reports, plus catalogues, audiences and conversion tags.
41 tables / 348 fields / Tables from the production sync
Tables and fields
Every table this connector creates. Field lists come from the production sync where we publish it, and otherwise from the documented schema, marked on the table.
campaign_report
16 fields
- account_id
- advertiser_id
- campaign_id
- date
- spend_in_dollar
- impression_1
- clickthrough_1
- outbound_click_1
- ctr
- cpc_in_micro_dollar
- ecpm_in_micro_dollar
- engagement_1
- engagement_rate
- total_conversions
- total_video_mrc_views
- total_video_p100_complete
keyword_report
8 fields
- keyword_id
- ad_group_id
- pin_promotion_id
- date
- spend_in_dollar
- impression_1
- clickthrough_1
- total_conversions
campaign_history
9 fields
- id
- name
- objective_type
- status
- summary_status
- daily_spend_cap
- lifetime_spend_cap
- is_campaign_budget_optimization
- start_time
pin_promotion_history
9 fields
- id
- pin_id
- ad_group_id
- name
- creative_type
- review_status
- destination_url
- click_tracking_url
- is_pin_deleted
advertiser_history
9 fields, documented schema
- id
- updated_time
- account_permissions
- country
- created_time
- currency
- name
- owner_user_id
- owner_username
ad_group_history
23 fields, documented schema
- id
- updated_time
- ad_account_id
- campaign_id
- auto_targeting_enabled
- bid_in_micro_currency
- bid_strategy_type
- billable_event
- budget_in_micro_currency
- budget_type
- conversion_learning_mode_type
- created_time
- end_time
- feed_profile_id
- lifetime_frequency_cap
- name
- optimization_goal_metadata
- pacing_delivery_type
- placement_group
- start_time
- status
- summary_status
- upgrade_status
advertiser_report
10 fields, documented schema
- advertiser_id
- clickthrough_1
- clickthrough_2
- date
- impression_1
- impression_2
- spend_in_micro_dollar
- total_conversions
- total_conversions_quantity
- total_conversions_value_in_micro_dollar
ad_group_report
14 fields, documented schema
- ad_group_id
- ad_group_name
- ad_group_status
- advertiser_id
- campaign_id
- clickthrough_1
- clickthrough_2
- date
- impression_1
- impression_2
- spend_in_micro_dollar
- total_conversions
- total_conversions_quantity
- total_conversions_value_in_micro_dollar
pin_promotion_report
13 fields, documented schema
- ad_group_id
- advertiser_id
- campaign_id
- clickthrough_1
- clickthrough_2
- date
- impression_1
- impression_2
- pin_promotion_id
- spend_in_micro_dollar
- total_conversions
- total_conversions_quantity
- total_conversions_value_in_micro_dollar
pin_promotion_targeting_report
15 fields, documented schema
- date
- targeting_type
- targeting_value
- ad_group_id
- advertiser_id
- campaign_id
- pin_promotion_id
- clickthrough_1
- clickthrough_2
- impression_1
- impression_2
- spend_in_micro_dollar
- total_conversions
- total_conversions_quantity
- total_conversions_value_in_micro_dollar
product_group_targeting_report
5 fields, documented schema
- date
- targeting_type
- targeting_value
- advertiser_id
- product_group_id
product_item_report
6 fields, documented schema
- date
- product_item_id
- ad_group_id
- advertiser_id
- campaign_id
- pin_id
product_group_report
5 fields, documented schema
- date
- ad_group_id
- advertiser_id
- campaign_id
- product_group_id
pin_app_type_report
4 fields, documented schema
- app_type
- date
- pin_id
- advertiser_id
mmm_ad_group_targeting_daily_report
24 fields, documented schema
- app_type
- date
- gender
- location_code
- ad_group_id
- advertiser_id
- country
- cpc
- creative_type
- ctr
- earned_impressions
- earned_pin_clicks
- ecpm
- engagement_rate
- engagements
- impressions
- location
- paid_impressions
- paid_pin_clicks
- pin_clicks
- spend
- spend_in_account_currency
- spend_order_line_id
- spend_order_line_paid_type
mmm_campaign_targeting_daily_report
24 fields, documented schema
- app_type
- date
- gender
- location_code
- advertiser_id
- campaign_id
- country
- cpc
- creative_type
- ctr
- earned_impressions
- earned_pin_clicks
- ecpm
- engagement_rate
- engagements
- impressions
- location
- paid_impressions
- paid_pin_clicks
- pin_clicks
- spend
- spend_in_account_currency
- spend_order_line_id
- spend_order_line_paid_type
keyword_history
9 fields, documented schema
- ad_group_id
- advertiser_id
- campaign_id
- archived
- bid
- id
- match_type
- parent_type
- value
targeting_gender
2 fields, documented schema
- id
- name
targeting_age_bucket
2 fields, documented schema
- id
- name
targeting_app_type
2 fields, documented schema
- id
- name
targeting_locale
2 fields, documented schema
- id
- name
targeting_location
2 fields, documented schema
- id
- name
targeting_interest
4 fields, documented schema
- id
- level
- name
- parent_id
targeting_geo
2 fields, documented schema
- country_id
- country_name
targeting_geo_region
3 fields, documented schema
- region_id
- country_id
- region_name
targeting_geo_metro
3 fields, documented schema
- metro_id
- country_id
- metro_name
pin_history
14 fields, documented schema
- board_id
- board_section_id
- parent_pin_id
- ad_creative_type
- alt_text
- board_owner_username
- created_at
- description
- dominant_color
- id
- is_standard
- link
- media_type
- title
pin_media
8 fields, documented schema
- cover_image_url
- description
- duration
- height
- item_type
- link
- title
- width
pin_media_image
4 fields, documented schema
- property_name
- height
- url
- width
board_history
11 fields, documented schema
- board_pins_modified_at
- collaborator_count
- created_at
- description
- follower_count
- id
- media_image_cover_url
- name
- owner_username
- pin_count
- privacy
board_section
3 fields, documented schema
- board_id
- id
- name
board_pin_thumbnail_url
2 fields, documented schema
- url
- board_id
catalog_feed_history
13 fields, documented schema
- id
- updated_at
- created_at
- default_availability
- default_country
- default_currency
- default_locale
- format
- location
- name
- preferred_processing_schedule_time
- preferred_processing_schedule_timezone
- status
catalog_product_groups_history
10 fields, documented schema
- id
- last_update
- feed_profile_id
- created_at
- description
- filters
- is_featured
- name
- status
- type
product_group_history
16 fields, documented schema
- ad_group_id
- catalog_product_group_id
- parent_id
- bid_in_micro_currency
- collections_hero_destination_url
- collections_hero_pin_id
- creative_type
- definition
- id
- included
- is_mdl
- relative_definition
- slideshow_collections_description
- slideshow_collections_title
- status
- tracking_url
conversion_tag_history
8 fields, documented schema
- advertiser_id
- code_snippet
- enhanced_match_status
- id
- last_fired_time_ms
- name
- status
- version
conversion_tag_config
7 fields, documented schema
- aem_db_enabled
- aem_enabled
- aem_fnln_enabled
- aem_ge_enabled
- aem_loc_enabled
- aem_ph_enabled
- md_frequency
customer_list_history
10 fields, documented schema
- id
- updated_time
- advertiser_id
- created_time
- exceptions
- name
- num_batches
- num_removed_user_records
- num_uploaded_user_records
- status
audience_history
10 fields, documented schema
- audience_type
- id
- updated_time
- advertiser_id
- created_time
- description
- name
- rule
- size
- status
ad_rejected_label_history
3 fields, documented schema
- label
- pin_promotion_id
- updated_time
rejected_reason_history
4 fields, documented schema
- index
- pin_promotion_id
- updated_time
- reason
Where it lands
Into a warehouse you already own, in a region you pick. The modelling runs inside that project, so nothing leaves your cloud to be transformed and we keep no copy of your history.
- Google BigQuery
- Snowflake
- Databricks
- AWS Redshift
- Azure Synapse
Every ad platform names the same number differently and reports it in its own currency and its own time zone. Put two of them in one report without reconciling that and the totals disagree.
Questions people ask
What tables does SightShark create from Pinterest Ads?
41 tables, including campaign_report, keyword_report, campaign_history. campaign_report is one row per campaign, per day. Every one is listed on this page, with its fields.
Which Pinterest Ads fields can I get?
The 348 fields on this page, table by table. Lists marked documented schema follow the published schema for Pinterest Ads, and your own warehouse may carry a few more or fewer.
How often does Pinterest Ads data refresh?
Daily. A sync adds to the tables rather than replacing them, so when a platform restates a figure for a day that has already closed, both the original number and the correction stay on record.
Can I join Pinterest Ads data to my other platforms?
Yes. Every metric is modelled to one name, one type, one grain and one currency, so a query across Pinterest Ads and another source needs no reconciling of field names first.
Related connectors
Reporting on this data
- 7 min read
Why ad platform numbers never match on the same campaign.
They are not measuring the same thing. Once you know what each one counts, the gap stops being a mystery.
Read it - 6 min read
Server-side vs client-side tracking, and what changes in client reports.
More conversions, a break in your trend line, and a new way to count one sale twice.
Read it - 6 min read
How to set up alerts across client accounts, and keep them worth reading.
An alert that fires every day becomes a filter rule. Four things are worth interrupting somebody for.
Read it
Get started
Want Pinterest Ads in your own warehouse?
A call with someone who can answer the schema questions.