Set up Pinterest Tag as a destination in RudderStack.
5 minute read
This guide will help you set up Pinterest Tag as a destination in the RudderStack dashboard. It also lists the configuration settings required to correctly send data from the supported sources to Pinterest.
In the web device mode integration, that is, using JavaScript SDK as a source, RudderStack loads the Pinterest Tag native SDK from the https://s.pinimg.com/ domain.
Based on your website’s content security policy, you might need to allowlist this domain to load the Pinterest Tag SDK successfully.
Get started
Once you have confirmed that the source platform supports sending events to Pinterest Tag, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select Pinterest Tag.
Assign a name to the destination and click Continue.
Connection settings
To successfully configure Pinterest Tag as a destination, configure the following settings:
App Store App ID: Enter the App Id from your App Store (required only for sending events using an iOS source).
API Version: Select the Pinterest Tag API version from the dropdown and enter the following values (required only for sending events via cloud mode):
V3(deprecating soon):
Pinterest Advertiser ID: Enter the Advertiser ID of your Pinterest account.
V5:
Ad Account ID: Enter your Pinterest’s Ad Account ID.
Conversion Token: Enter the Conversion Token associated with your Pinterest account.
Other settings
Send as test event: RudderStack marks the event as test requests if this setting is turned on. It does not record the event but the API still returns the same response messages.
Use this setting to verify if your requests are working and the events are constructed correctly.
Enable hashing for user data conversions: This setting is on by default and hashes your user data using SHA256 encoding.
Enable Event Deduplication: Turn on this setting to deduplicate the events. Then, specify the following:
Deduplication key: Enter the key using which Pinterest Tag should use to deduplicate the events.
Enable Enhanced Match on Page Load: This setting is on by default and attaches the hashed email address on the initial page load. Any further calls made to Pinterest will be an Enhanced Match.
When turned off, all visits made to your site become anonymous. However, you can still identify any user by making the identify() call.
A user is identified every time they visit your site.
A user visits your site anonymously but is identified at a later stage by making an identify() call.
If you use RudderStack’s identify() method to use Pinterest’s Enhanced Match, you can only collect this information for successive events. Pinterest does not retroactively update the values for the past events.
Send external_id for user: Turn on this setting to send the user’s external_id to Pinterest Tag (applicable only for sending events via cloud mode).
Send as custom event: Turn on this setting to send an unmapped event as a Pinterest custom event. If an event is neither mapped in the Map Your Events To Pinterest Events dashboard setting nor is one of the ecommerce tracking events, it will be sent as a custom event.
Custom Properties: Enter any custom properties which should be sent to Pinterest (applicable only for sending events via device mode). For more information on using the custom properties, refer to the Custom properties section.
Map Your Events To Pinterest Events: Use this field to map RudderStack events to Pinterest Standard Conversion Events.
Note that RudderStack gives the highest priority to the event mapping specified in this setting.
If Send as custom event toggle is turned on, then RudderStack sends the event with name custom to Pinterest.
If none of the above qualifies:
RudderStack sends the event name to Pinterest as is and it is shown as an unknown event in the Pinterest dashboard.
Client-side events filtering
This setting is applicable only if you are sending events to Pinterest Tag via device mode. Refer to the Client-side Event Filtering guide for more information.
Consent Settings
Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. See Consent Management in RudderStack for more information on this feature.
Web SDK Settings
Use device-mode to send events: If you are using the JavaScript SDK as a source, this setting is on by default and cannot be turned off.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.