Pinterest is a visual discovery platform where people find ideas through Pins and boards, and where businesses publish content, run ads and list their product catalogs. The Pinterest API connector reads the user account, boards, sections, Pins, ad accounts, campaigns, ad groups, ads, audiences, customer lists, keywords, catalogs, organic and ads analytics, and asynchronous ads reports, and can create, update and delete boards, sections, Pins, ads objects, audiences and catalog data.
Power end-to-end data operations for your Pinterest API API with Nexla. Our bi-directional Pinterest API connector is purpose-built for Pinterest API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Pinterest API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pinterest API workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to the Pinterest API v5 (https://api.pinterest.com/v5) as a Pinterest user, through a Pinterest developer app that you register. Complete the following steps before creating a credential in Nexla.
Make sure you have a Pinterest business account. The ads templates also need access to at least one ad account, and the catalog templates need a catalog in the business account. Nexla can only read and change what the authorizing user can access.
Sign in to developers.pinterest.com/apps with the business account, and connect (create) an app. Pinterest reviews new apps before it grants them API access.
In the app's settings, add https://dataops.nexla.io/nexla-api/oauth/callback as a Redirect URI (or /nexla-api/oauth/callback on the Nexla host you sign in to). The redirect URI must match exactly.
Copy the app's App ID and App secret key. You will enter them as the Client ID and Client Secret of the Nexla credential. Store the secret securely.
To use the destination templates that create or change ads objects (ad accounts, conversion tags and events, campaigns, ad groups, ads, audiences, customer lists, targeting templates and keywords), or catalogs, the app needs Pinterest's approval for the ads:write or catalogs:write scope. Request it from Pinterest for your app. Once it is approved, add the scope to the Access Scope field of the credential.
Pinterest grants the scopes listed in Access Scope when you authorize the credential. If you change the scopes later, for example to add ads:write or catalogs:write, click Authorize again so that Pinterest issues a token with the new scopes. Until then, templates that need the new scope fail with an authorization error.
Some destinations publish content, spend money or delete data
Destination templates that create or change boards, sections, Pins and catalog items publish to the user's Pinterest profile; these are marked Publishes content below. Templates that create or change campaigns, ad groups, ads and keywords act on live advertising, and can start delivering ads and spending the ad account's budget; these are marked Spends budget. Templates that delete boards, sections, Pins, feeds, product groups, items or customer list members are marked Deletes data; deleted objects cannot be restored from Nexla. To create ads objects without spending, set status to PAUSED in the record.
Access Scope is a comma-separated list of Pinterest OAuth scopes. It defaults to ads:read,boards:read,boards:read_secret,boards:write,catalogs:read,pins:read,pins:read_secret,pins:write,user_accounts:read, which covers every source template and the board, section and Pin destination templates. The ads:write and catalogs:write scopes are not included, because Pinterest must approve them for your app first; add them once they are approved (see Prerequisites). The *_secret scopes let Nexla read secret boards and the Pins on them; remove them if Nexla should only see public content.
Pinterest requires the Client Secret to issue tokens. Nexla sends the Client ID and Client Secret to Pinterest's token endpoint in an HTTP Basic Authorization header, as Pinterest requires.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Pinterest API
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter the App ID of your Pinterest app in the Client ID field, and its App secret key in the Client Secret field.
Review the Access Scope field. Keep the default, or add ads:write and catalogs:write if Pinterest has approved them for your app and you plan to use the ads or catalog destination templates.
Click the Authorize button. Sign in to Pinterest as the user that Nexla should act as, and approve access. Nexla stores the refresh token and gets new access tokens automatically.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by reading the authorized user's account.
Keep the Client Secret confidential. If it is compromised, reset the app secret key in the Pinterest developer portal, update the credential, and authorize it again.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Pinterest API connector tile, then select the credential that will be used to connect to Pinterest, and click Next; or, create a new Pinterest API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Pinterest API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area. The note under each group names the OAuth scopes it needs; all of them are in the default Access Scope.
Pinterest objects are nested: the user owns boards, a board holds sections and Pins, an ad account holds campaigns, a campaign holds ad groups, and an ad group holds ads and keywords. Most ads templates need an ad account ID: start with List Ad Accounts to find it, and use the matching list template to find any other ID a template asks for. Date settings use YYYY-MM-DD and UTC; analytics templates read at most 90 days back. Templates that say "Results are paged automatically" read every page; all other templates make a single request.
Ad accounts and the objects that belong to them directly: conversion tags, lead forms and order lines. Needs ads:read.
List Ad Accounts
Lists the ad accounts that the user owns or can access, with each account's name, owner, country, currency and permissions. Use it to find the ad account ID that most ads templates need.
Returns the minimum bids for a billable event, objective and targeting. This template sends a POST request, but it only reads data.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Bid Floor Request: the JSON request body, with bid_floor_specs (billable_event, currency, objective_type and so on) and, optionally, targeting_spec. Defaults to {"bid_floor_specs": [{"billable_event": "IMPRESSION", "currency": "USD", "objective_type": "AWARENESS"}]}.
Estimates the audience size range for an ad group targeting spec. This template sends a POST request, but it only reads data.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Sizing Request: the JSON request body, with targeting_spec and, optionally, keywords, creative_types, placement_group and auto_targeting_enabled. Defaults to {"targeting_spec": {"GEO": ["US"], "AGE_BUCKET": ["25-34"]}}.
Organic analytics for the user account and Pins need user_accounts:read, or pins:read and boards:read. Ads analytics and reports need ads:read.
Get User Account Analytics
Reads daily organic metrics for the user's account over a date range: impressions, saves, Pin clicks, outbound clicks and engagement. Each day is one record.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Lists the user's top 50 video Pins, ranked by a video metric over a date range, with their metrics.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Select the video metric to rank Pins by in Sort By, such as IMPRESSION, SAVE, OUTBOUND_CLICK, VIDEO_MRC_VIEW, VIDEO_AVG_WATCH_TIME or VIDEO_START. Defaults to IMPRESSION.
Reads daily metrics for one Pin over a date range. Each day is one record.
Enter the Pin ID. Use the List Pins or List Board Pins template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Metric Types, separated by commas, for example IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK,VIDEO_MRC_VIEW. Defaults to IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK.
Reads metrics for up to 100 Pins over a date range. The result is one record, keyed by Pin ID.
Enter the Pin IDs (up to 100), separated by commas. Use the List Pins template to find them.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Metric Types, separated by commas, for example IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK,VIDEO_MRC_VIEW. Defaults to IMPRESSION,SAVE,PIN_CLICK,OUTBOUND_CLICK.
Reads ad account metrics, such as spend, impressions, clicks, CTR and conversions, by day, hour, week, month or in total.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads ad account metrics broken down by targeting type, such as age, gender, country or keyword.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads metrics for one or more campaigns over a date range, such as spend, impressions, clicks and conversions.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Campaign IDs, separated by commas. Use the List Campaigns template to find them.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads campaign metrics broken down by targeting type.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Campaign IDs, separated by commas. Use the List Campaigns template to find them.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads metrics for one or more ad groups over a date range.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Ad Group IDs, separated by commas. Use the List Ad Groups template to find them.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads ad group metrics broken down by targeting type.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Ad Group IDs, separated by commas. Use the List Ad Groups template to find them.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads metrics for one or more ads over a date range.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Ad IDs, separated by commas. Use the List Ads template to find them.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Ad IDs, separated by commas. Use the List Ads template to find them.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Targeting Types to break the metrics down by, separated by commas, for example AGE_BUCKET,GENDER,COUNTRY,KEYWORD. Defaults to AGE_BUCKET.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads metrics for the promoted Pins of a campaign over a date range.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Campaign ID. Use the List Campaigns template to find it.
Enter the Pin IDs, separated by commas: the pin_id values returned by the List Ads template.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Reads metrics for shopping ad product groups over a date range.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC), at most 90 days back. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Enter the Product Group IDs, separated by commas: the IDs of the product groups used in your shopping ad groups.
Enter the metric Columns, separated by commas, for example SPEND_IN_DOLLAR,IMPRESSION_1,CLICKTHROUGH_1,CTR. Defaults to SPEND_IN_DOLLAR,PAID_IMPRESSION,IMPRESSION_1,CLICKTHROUGH_1,CTR,TOTAL_CONVERSIONS. Use the List Delivery Metrics template to see the available metrics.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Runs an asynchronous ads report end to end and reads its rows into the Nexset: it requests a CSV report, polls until the report is FINISHED, then downloads the CSV. See Asynchronous ads reports for how it works.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Enter the Start Date in YYYY-MM-DD format (UTC). It can be up to 914 days back, and the report can cover at most 186 days. Defaults to 7 days ago.
Enter the End Date in YYYY-MM-DD format (UTC). Defaults to today.
Select the Granularity: TOTAL, DAY, HOUR, WEEK or MONTH. Defaults to DAY.
Select the report Level: ADVERTISER, CAMPAIGN, AD_GROUP, PIN_PROMOTION, KEYWORD, PRODUCT_GROUP or PRODUCT_ITEM. Defaults to CAMPAIGN.
Enter the report Columns as a JSON array, for example ["SPEND_IN_DOLLAR", "IMPRESSION_1"]. Defaults to ["CAMPAIGN_NAME", "SPEND_IN_DOLLAR", "IMPRESSION_1", "CLICKTHROUGH_1", "CTR"].
Lists the definitions of Pinterest's reporting metrics, with each metric's name, definition and display name. Use it to choose report and analytics columns.
Reads catalog items by item ID for a country and language. This template sends a POST request, but it only reads data.
Enter the Items Request: the JSON request body, with country, language and filters (catalog_type and item_ids). The default, {"country": "US", "language": "EN", "filters": {"catalog_type": "RETAIL", "item_ids": ["SKU1"]}}, is an example; replace the item IDs with your own.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Pinterest builds ads reports asynchronously: you request a report, Pinterest generates it in the background, and you download the file once it is ready. The connector supports this in two ways:
Run Ads Report does the whole process in one source. On each run, it:
requests a CSV report for the ad account, with the level, columns, granularity and date range from the template settings, and gets back the report's token;
polls the report's status with that token until report_status is FINISHED, and stops with an error if Pinterest reports FAILED;
downloads the CSV from the report's url, a pre-signed link that needs no Pinterest token, and reads each row of the CSV as a record.
Get Report Status reads the status, size and download url of a report you requested in another way, such as through the Pinterest API directly, given its token. There is no destination template that requests a report on its own.
A report can start up to 914 days back and cover at most 186 days. For metrics as JSON, without a report, use the analytics templates above, such as Get Campaign Analytics, which read at most 90 days back. Use Get Metrics Ready State to check whether a day's metrics are final before you read them.
Pinterest data sources can also be manually configured to ingest data from any valid Pinterest API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or optional filters that the templates do not send. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. Pinterest endpoint URLs take the form https://api.pinterest.com/v5/.... List endpoints return their records in items and the next page's cursor in bookmark. See the Pinterest API reference for the available endpoints.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Pinterest data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Pinterest destination, and select the Send to Destination option from the menu. Select the Pinterest API connector from the list of available destination connectors, then select the credential that will be used to connect to Pinterest, and click Next; or, create a new Pinterest API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Pinterest API endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent as the JSON body of one request, one record at a time, so shape each record to match the request body that Pinterest documents for the endpoint. The campaign, ad group and ad templates are the exception: they send records in batches of up to 30, because Pinterest creates and updates these objects in bulk. ID settings, such as an ad account or board ID, are fixed on the destination and apply to every record it sends. Templates are marked Publishes content, Spends budget or Deletes data as described in Prerequisites.
The ads and catalog templates need the ads:write or catalogs:write scope, which Pinterest must approve for your app, and which you must add to the credential's Access Scope before you authorize it.
Needs pins:read, pins:write, boards:read and boards:write, which are in the default scope.
Create Pin
Creates a Pin from each record. A record carries board_id, media_source (for example, source_type set to image_url, and url) and, optionally, title, description and link.
Publishes content: the Pin is published to the user's profile, and is public on a public board.
Sends conversion events to the Pinterest Conversions API, for ad attribution. A record carries data: a list of events, each with event_name, action_source, event_time, event_id and user_data.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Needs ads:write, which is not in the default scope. See Prerequisites.
Create Campaign
Creates campaigns. A record carries ad_account_id, name, objective_type, and, optionally, status, budgets and dates. A campaign is created ACTIVE unless the record sets status.
Spends budget: a new campaign is ACTIVE unless the record sets status, and its ad groups and ads can start delivering and spending budget.
Records are sent in batches of up to 30, as a JSON array in one request, so shape each record as one object of that array.
Enter the Ad Account ID. Use the List Ad Accounts template to find it.
Creates, updates or deletes catalog items in one batch request. A record carries country, language, operation and items. Read the batch's results with the Get Items Batch Status source.
Publishes content: created and updated items become product Pins on the user's profile.
Deletes data: a DELETE operation removes the items and their product Pins.
Pinterest destinations can also be manually configured to send data to any valid Pinterest API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Pinterest API expects JSON request bodies for create and update requests. Include the ad account, board and other object IDs in the endpoint URL, for example https://api.pinterest.com/v5/ad_accounts/AD_ACCOUNT_ID/campaigns. Campaign, ad group and ad requests take a JSON array of up to 30 objects.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Pinterest endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Pinterest endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.