Skip to main content
Use the @bijection/connectors/pinterest-ads entrypoint to declare Pinterest Ads resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Ad analytics

​
daily: Daily account or campaign analytics within Pinterest’s 90-day reach

The following example matches configuration account.

​
Configuration: account

Case: pinterest-ads/analytics/daily/account. Connection and resource configuration are declared by this exact case. Credential kind: pinterest-ads. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: analytics
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: campaigns

Case: pinterest-ads/analytics/daily/campaigns. Connection and resource configuration are declared by this exact case. Credential kind: pinterest-ads. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: analytics
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
async: Daily account or campaign history through asynchronous reports

The following example matches configuration account.

​
Configuration: account

Case: pinterest-ads/analytics/async/account. Connection and resource configuration are declared by this exact case. Credential kind: pinterest-ads. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: reports
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: campaigns

Case: pinterest-ads/analytics/async/campaigns. Connection and resource configuration are declared by this exact case. Credential kind: pinterest-ads. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: reports
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Daily ad account (or listed campaign) analytics from Pinterest API v5’s synchronous GET /v5/ad_accounts/{id}/analytics (or /campaigns/analytics with up to 250 campaignIds), granularity=DAY over 30-day requests, read as restated report observations. Rows are keyed by (account or campaign id, DATE). Only integer columns are offered and each is exact; spend and checkout value are micro-dollars. Synchronous analytics reach back 90 days. Older days are not read by analytics.daily: every pass begins no earlier than 89 days before the UTC day it runs, whatever start says. analytics.async reads up to 914 days back through Pinterest’s asynchronous report, one report per pass over windowDays (default 93; Pinterest allows 186): POST /v5/ad_accounts/{id}/reports (JSON body, granularity: DAY, level ADVERTISER or CAMPAIGN with its id column, report_format: JSON), then GET .../reports?token=... every pollSeconds (default 60) until report_status is FINISHED; DOES_NOT_EXIST, EXPIRED, FAILED and CANCELLED end the pass with a typed gap. The report file is a five-minute storage link read without a credential. Pinterest’s reference does not document the file’s layout; this mode reads it as open-source connectors do, one JSON object keyed by entity whose members are arrays of rows naming the id column and DATE, and reads ids as the digit strings Pinterest’s synchronous schema types them as. A file laid out otherwise fails the pass. Campaign rows cover every campaign, or the listed campaignIds (at most 500). Keys, exact columns, carried windows and settled are those of analytics.daily, so a day read by both modes is one row. Conversions follow the declared windows (clickWindowDays, viewWindowDays, engagementWindowDays; Pinterest’s defaults 30, 1 and 30) and conversionReportTime. Reported at the time of the ad action, a later conversion changes an earlier day, so restatementDays defaults to the longest window plus two days; at the time of conversion, three days. Pinterest states no per-row finality and documents no restatement bound, so settled is that declared window’s basis. The connection holds a pinterest-ads OAuth credential (pinterestAds.credential, scope ads:read); setup names adAccountId. Nothing here has run against Pinterest or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.