Skip to main content

Pinterest Ads — Data Mapping

B
Written by Ben Keeling

The objects we sync from your Pinterest ad account, the exact fields we read for each, and how they map into Medialake.


Medialake syncs your account's delivery hierarchy (campaigns → ad groups → ads), the Pins behind your ads, and their performance metrics — all read-only, via Pinterest API v5. We only read the fields listed on this page, nothing else.


Objects at a glance

Pinterest object

What it is

Why we sync it

The container for all your advertising

Captures the hierarchy of metrics and creatives within the ad accounts you give access to, and supplies the billing currency

Top level of the hierarchy

Captures the hierarchy, so metrics and creatives roll up the same way as in Ads Manager

Targeting, schedule, and budget grouping

Captures the hierarchy and the flight dates each ad runs to

The individual ad

The object metrics relate to — performance is captured per ad

The Pin an ad promotes

Links each ad to its actual Medialake media file, and is the source of the image or video we ingest

Performance data for each ad

Become Medialake metrics — powering Performance dashboards and reports (see Metrics Reference)


Ad Account

The starting point. We can only see the ad accounts the connecting Pinterest account is assigned to — that access boundary, not the selection, is what ultimately limits our reach.

Fields we read:id, name, currency

The currency field is the ad account's billing currency, and it's what every monetary metric is recorded in before conversion to USD. See Metrics Reference.


Campaigns & Ad Groups

We read the delivery tree for each synced ad account, preserving the same hierarchy you see in Ads Manager. Campaigns and ad groups are read at ACTIVE, PAUSED and ARCHIVED status, so a paused or finished campaign keeps reporting rather than disappearing.

Campaign fields we read:id, name

Ad group fields we read:id, name, campaign_id, start_time, end_time

The ad group's start and end times become the flight dates on each ad beneath it. Pinterest reports these as epoch timestamps, and Medialake stores them as dates.

An ad group appears as the ad set level in Medialake, which is the common name used across every advertising connector.


Ads

Fields we read:id, name, ad_group_id, ad_account_id, creative_type, pin_id, status, created_time, is_pin_deleted

creative_type is stored as the ad type and also decides how the creative is handled — a carousel is split, everything else maps one-to-one. status is stored as the ad's remote status.


Ads we skip

Two kinds of ad are deliberately not synced:

  • Ads whose Pin has been deleted (is_pin_deleted) — there is no media left to ingest.

  • Ads with a THIRD_PARTY, PARTNERSHIP or IDEA creative type — these don't resolve to a Pin whose media we can bring in.

Everything else in the account syncs, including paused and archived ads.


Pins, creatives and media

The Pin is what becomes a file in Medialake: each image and video appears as a browsable asset with a thumbnail, connected to the ads that use it. We fetch each Pin in the context of the ad account that runs it.

Fields we read:id, title, created_at, and from media: media_type, duration, images (all available sizes), items (carousel slides, each with item_type and images), and video_url

How the media resolves depends on the Pin type:

Pin media type

What Medialake creates

Image

One image file, from the largest available image size

Video

One video file, with a thumbnail from the Pin's image sizes

Carousel (multiple_images, multiple_mixed, multiple_videos)

One file per slide, each with its own thumbnail and its own creative record

For carousels, each slide is identified by the Pin ID and its position in the carousel, so slides stay distinct and stable across syncs. A slide's title is the Pin's title with its position appended; where a Pin has no title, the identifier is used.

A file's name comes from the ad's name where there is one, falling back to the Pin's title and then the Pin's identifier.


Ads Analytics (performance metrics)

Metrics are read per ad in daily buckets, then rolled up into weekly, monthly, yearly and lifetime totals inside Medialake. Pinterest's analytics reach back roughly 90 days, so daily coverage builds forward from the point the account was connected. The full list of metrics and how each maps to Pinterest's analytics columns is in the Metrics Reference.


How it maps into Medialake

Ad Account
 └─ Campaign
     └─ Ad Group
         └─ Ad ──── metrics (per ad, per day)
             └─ Creative (Pin, or one per carousel slide)
                 └─ Media file (image / video + thumbnail)

Everything on this page is read-only — see Authentication for the permissions behind it.


Further reading (Pinterest documentation)


Questions about a specific field? Contact [email protected].

Did this answer your question?