Pinterest is a visual discovery engine for finding ideas such as recipes, home decor, style inspiration, and more. There are billions of pins on Pinterest, which can also be shared with others on Pinterest. You can collate the user interaction events and leverage Pinterest Analytics to understand user behavior and run targeted advertisements.
The Pinterest Conversions API event forwarding extension allows you to leverage data captured in the Adobe Experience Platform Edge Network and send it to Pinterest. This document covers the use cases of the extension, how to install it, and how to integrate its capabilities into your event forwarding rules.
Conversions access tokens are the authentication method used by Pinterest when interacting with the Pinterest API.
This extension should be used if you want to use data from the Edge Network in Pinterest to take advantage of its customer analytics capabilities.
For example, consider a marketing team in an organization. The team captures user interaction event data from their website and loads it into Pinterest using this event forwarding extension.
The marketing and analytics teams can then leverage Pinterest Analytics capabilities to understand key user interactions and behavior, allowing you to better understand users and target them for targeted ad campaigns.
For more information on use cases specific to Pinterest, refer to the Pinterest use cases documentation.
You will also need a Pinterest developer account, which will need to be associated with your Pinterest business account. To associate your developer account with your business account, refer to the Pinterest developer account.
In order to connect the Experience Platform to Pinterest, the following inputs are required:
|Ads Account Id
|Your Pinterest Ads Account Id. Refer to the Pinterest documentation for guidance.
|Conversion Access Token
|Your Pinterest Conversion Access Token. Refer to the Pinterest Conversions API document for guidance.
You will only be required to do this once as this token does not expire.
To install the extension, create an event forwarding property or choose an existing property to edit instead.
In the left navigation, select Extensions. Select Install on the card for the Pinterest extension in the Catalog tab.
Depending on your implementation needs, you may need to create a schema, data elements, and a dataset before configuring the extension. Please review all the configuration steps before starting in order to determine which entities you need to set up for your use case.
In the left navigation, select Extensions. Select Configure on the card for the Pinterest extension in the Installed** tab.
On the next screen, input the Ads Account Id and Conversion Access Token that you previously gathered in the configuration details section. When you’re finished, select Save.
Once all your data elements are set up, you can start creating event forwarding rules that determine when and how your events will be sent to Pinterest.
Create a new rule in your event forwarding property. Under Actions, add a new action and set the extension to Pinterest. To send Edge Network events to Pinterest, set the Action Type to Send Event.
After selection, additional controls appear to further configure the event. You need to map the Pinterest event properties to the data elements that you previously created.
The following event data will be required to create the new rule:
|The type of the user event. This can be any event type however, to leverage Pinterest Analytics it is recommended to use Pinterest event codes
* [User-defined event]
|The source indicating where the conversion event occurred.
|This refers to the event time. The default time format used is UNIX, in the format
<seconds>.<miliseconds> depending on your local timezone. For more information, refer to the Pinterest API.
|1433188255.500 indicates 1433188255 seconds and 500 milliseconds after epoch, or Monday, June 1, 2015, at 7:50:55 PM GMT.
|A unique id string that identifies this event and can be used for deduping between events ingested via both the conversion API and Pinterest tracking. Without this, the event’s data is likely to be double counted and will report metric inflation.
|A JSON object containing custom properties of the event. Select from providing raw JSON or using a simplified set of key-value inputs.
The following event properties can be configured:
|Event Source URL
|URL of the web conversion event.
|Application Store ID
|The app store app ID.
|The name of the application.
|The version of the application.
|Brand of device being used by the user.
|User’s mobile carrier for their device.
|Model of the user’s device.
|Type of device being used by the user.
|Version of the device’s operating system.
|Two-character ISO-639-1 language code indicating the user’s language.
The following user data can be entered by are not required fields:
|User email address or a SHA256 hash of the user address email.
|Mobile Adverstising IDs
|Sha256 hashes of user’s “Google Advertising IDs” (GAIDs) or “Apple’s Identifier for Advertisers” (IDFAs)
|Client IP Address
|The user’s IP address, which can be either in IPv4 or IPv6 format. Used for matching.
|Client User Agent
|The user agent string of the user’s web browser.
|Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion
|Customer information data
|A JSON object containing other customer information. Select from providing raw JSON or using a simplified set of key-value inputs.
The customer information properties that can be configured are:
|User contact number. Only digits are accepted and should be entered with country code, area code, and number.
|Gender can be entered as either “f” for female, “m” for male, or “n” for non-binary.
|Date of Birth
|Birth date, entered as year, month, and day.
|User’s last name.
|User’s first name.
|User’s residency city. This is mostly used for billing purposes.
|User’s state, which is provided as a two-letter code in lowercase.
|User’s zipcode, which is mostly used for billing purposes.
|Two-character ISO-3166 country code indicating the user’s country.
|Unique id from the advertiser that identifies a user in their space. For example, user id, loyalty id, and so on.
|The unique identifier stored in _epik cookie on your domain or &epik= query parameter in the URL.
Before sending the data to the Pinterest API endpoint, the extension will hash and normalize the values of the following fields: Email, Phone Number, First Name, Last Name, Gender, Date of Birth, City, State, Zip Code, Country, and External ID. The extension will not hash the value of these fields if a SHA256 string is already present.
The following custom data can be entered for the rule:
|The ISO-4217 currency code. If this is not provided, Pinterest will default to the advertiser’s currency that was set during account creation.
|Total value of the event. Accepted as a string in the request. This will be parsed into a double digit.
|The search string related to the user conversion event.
|The order ID. Sending
order_id will help Pinterest deduplicate events when necessary.
|Number of Products
|Total number of products of the event. For example, the total number of items purchased in a checkout event.
|List (array) of products IDs.
|A list (array) of objects containing information about products, such as price and quantity.
Once the event forwarding rule has been created and executed, validate whether the event that was sent to the Pinterest API is displayed as expected in the Pinterest UI.
If the event collection and Experience Platform integration were successful, you will see events within the Pinterest UI.
You can further drill through and view the Pinterest event data distribution.
This guide covered how to install and configure the Pinterest event forwarding extension in the UI. For more information, refer to the official documentation: