Search specific term/phrase surrounded by double quotes. e.g. “deep linking”
Exclude records that contain a specific term prefixed with a minus. e.g. Android -Firebase



Pinterest is a visual discovery engine for finding ideas like recipes, home and style inspiration, and more.
With billions of Pins on Pinterest, you'll always find ideas to spark inspiration. When you discover Pins you love, save them to boards to keep your ideas organized and easy to find.


Partner Capabilities


Company Type

  • Ad Network
  • DSP
  • Publisher
  • RTB
  • Self Serve

Deep Linking



  • Click-Through Attribution
  • View-Through Attribution

Ad Campaign Types

  • Acquisition campaigns
  • Retargeting campaigns

Ad Formats

Contact support at Pinterest for more information.

Click Types

  • Server-side click

Supported Platforms

  • iOS
  • Android
  • Windows
  • Mac OS
  • Unix
  • Tizen

Link Wrapping

Not Supported

Cost Ingestion Support

Not Supported

Pricing Models

  • CPC
  • CPM
  • CPA
  • CPV
  • CPL

1. Complete Universal Ads Prerequisites



The following Universal Ads prerequisite includes providing URI schemes and other components that may require a developer:



The following Universal Ads prerequisites involve app code changes:

2. Enable the Integration

  1. Visit the Ads page on the Branch dashboard.
  2. Select Partner Management from the sidebar.
  3. Search for Pinterest.
  4. Select Pinterest, and click Save & Enable.

3. Enable Postbacks

When Branch measures a conversion (install or other event), it determines which ad network or partner is responsible for generating the action, then attributes credit to the proper partner accordingly. Branch notifies the Ad partner of these events via postbacks which are turned on when you enable any Universal Ads integrated partner.

Basic postbacks will automatically be activated for events like Install and Purchase when you enable your ad partner.

Branch’s postback system is highly customizable; you can set up postbacks for specific events, as well as specific subsections of events, filtered by link data, user data or event properties.

You can then add additional postbacks, for example, if you wanted to add postbacks for custom events that are specific to your app like Account Created. You can also edit postbacks if there's additional data you really need to pass along to your ad partner.


Additional Information Required

Pinterest requires the Pinterest Tag ID that corresponds to each postback - Hardcode the Pinterest event name in the event_type macro. To do this, go to the Postback Config tab > click on the Ellipses > Advanced Edit > Body and find the macro event_type": "${ (name)! } and change it to the correct Pinterest event name (Pinterest should provide you the mapping).

Example: View Item in Branch is pin_category_view in Pinterest so the postback should be "event_type": "pin_category_view"

Talk to your Account Manager at Pinterest to learn how to access your Pinterest Tag ID.


Troubleshoot Postbacks

There may be times when you need to reset a partner's settings; i.e. when a partner updates their postback templates or when perhaps you've made a mistake during partner setup. Resetting a partner's settings allows you to re-enable the partner integration with the correct information to accurately measure and attribute conversion.

Note, by resetting your partner settings, this will:

  • Disable the ad partner
  • Clear out all of your saved credentials and postbacks that are already setup
  • Return the ad partner to its basic configuration

Learn more here on how to reset your ad partner's settings.

4. Verify Integration Setup

View Link Parameters

By default, Branch automatically appends partner-specific link parameters during the link creation process. When a user clicks on the link, Pinterest provides the appropriate parameter values which Branch ingests and uses for attribution and reporting purposes.

Below are the link parameters that Branch automatically appends for this ad partner:

View Attribution Windows

Branch employs Attribution Windows at both the app level and the ad partner level. When you enable Pinterest, Branch uses the attribution windows you've selected at the app level.

However, you can choose to use the attribution windows provided specifically by Pinterest. To do so, toggle the Use Ad Partner Attribution Windows to on. Please keep in mind that only conversions attributed to this ad partner will use these specific windows; otherwise, the app-level windows prevail.

Test Postbacks

Testing your configuration is a very important step that we highly recommend you take the time to complete before going live with marketing campaigns.

Learn how to Test Postbacks

5. Create a Branch Link

If you are running paid advertising campaigns, you'll want to create a Branch Ad Link so we can accurately attribute resulting app conversions to the appropriate advertising partner.

Branch Ad Links support deferred deep linking, Android App Links, and iOS Universal Links, as well as web and app conversions.

Learn how to Create A Branch Ad Link.

6. Create a Campaign

  1. Use a direct link to the Apple Store or Google Play Store in the Destination URL field.
  2. Remove $idfa_sha1={sha1_advertising_id} from your Branch Link if your Destination URL goes to the Google Play Store.
  3. Remove $aaid_sha1={sha1_advertising_id} from your Branch Link if your Destination URL goes to the Apple Store.
  4. Place your Branch link in the Click Tracking URL.
  5. Avoid using the View Tracking URL until further notice.

7. Troubleshoot

If you are running campaigns on Pinterest and having issues with Attribution on Branch, please check if you are using correct tracking links:

  1. Link to the Apple AppStore or Google Play.
  2. Click and Impression links, generated on Branch dashboard, configured as described below.

Verify Link Formatting

Click Tracking Link{sha1_advertising_id}&%24s2s=true&~ad_set_id={ad_group_id}&~ad_set_name={ad_group_name}&~campaign={campaign_name}&~campaign_id={campaign_id}&~click_id={click_id}&~creative_id={creative_id}&~creative_name={creative_name}&~secondary_publisher={publisher]({sha1_advertising_id}&%24idfa_sha1={sha1_advertising_id}&%24s2s=true&~ad_set_id={ad_group_id}&~ad_set_name={ad_group_name}&~campaign={campaign_name}&~campaign_id={campaign_id}&~click_id={click_id}&~creative_id={creative_id}&~creative_name={creative_name}&~secondary_publisher={publisher)

Impression Tracking Link{sha1_advertising_id}&~ad_set_id={ad_group_id}&~ad_set_name={ad_group_name}&~branch_ad_format=App%20Only&~campaign={campaign_name}&~campaign_id={campaign_id}&~click_id={click_id}&~creative_id={creative_id}&~creative_name={creative_name}&~feature=paid%20advertising&~secondary_publisher={publisher]({sha1_advertising_id}&~ad_set_id={ad_group_id}&~ad_set_name={ad_group_name}&~branch_ad_format=App%20Only&~campaign={campaign_name}&~campaign_id={campaign_id}&~click_id={click_id}&~creative_id={creative_id}&~creative_name={creative_name}&~feature=paid%20advertising&~secondary_publisher={publisher)

Since Pinterest users server-to-server clicks, make sure the following parameters are always present on the link:

  • %24s2s=true
    • Must be always present on the link
  • %24aaid_sha1={sha1_advertising_id}
    • For Android campaigns only, must be removed from the link for iOS campaigns
  • %24idfa_sha1={sha1_advertising_id}
    • For iOS campaigns only, must be removed from the link for Android campaigns
      Only one OS-specific Advertiser Identifier parameter must be on the link: either %24idfa_sha1 for iOS or %24aaid_sha1 for Android campaigns.

Most Common Issues

  • Advertiser ID is missed on the link
    • Solution: Add OS-specific Advertiser Identifier
  • Both Advertiser IDs presented on the link
    • Solution: Keep only one OS-specific Advertiser Identifier
  • Clicks are getting blocked by Branch Anti-Fraud rule - GEO_CONFLICT
    • Pinterest currently can’t provide the user’s IP address and this can cause a GEO_CONFLICT Fraud Rule. If you use a GEO_CONFLICT fraud rule, we recommend either disabling it or not running on Pinterest until they are able to pass the client IP to MMPs.