Articles in this section
Category / Section

Pinterest Ads Connector

The Pinterest Ads Connector is used to send data to both the Pinterest Ads Pixel and Conversion API.

Prerequisites

You will need the following to complete the setup of the connector successfully:

  • Pinterest Tag ID
  • Pinterest Conversion API Access Token
  • Pinterest Ad Account ID

Pinterest Connector Setup

Choose the Pinterest Connector from the "Connectors" section on your tracking container dashboard.

Press "Add" or "Edit" on the Pinterest Connector:

select_pinterest

Provide the following information:

Screenshot 2025-09-08 at 15.02

Find the ID

Pinterest Tag ID:

  • Click Ads, then find Conversion Tracking and click Get started under Install Pinterest Tag.
  • The 13 digit number below Unique Tag ID is your Pinterest tag ID.

Conversion API Access Token:

  • Click Ads in the top menu and choose Conversions and select Set Up API.
  • Click the Generate new token button and copy the new access token.

Ad Account ID:

  • Click Viewing inside Ads Manager and copy the Ad Account ID.
  • If you have access to multiple accounts, make sure to copy the ID of the Ad Account that you are connecting to Tracklution.

If you are ready to go live sending data to Pinterest, toggle the "Live" button and press "Save". Otherwise you can save your details by pressing "Save" and later come back to toggle the "Live" button. 

When your Connector is live, your collected data will be sent to Snapchat Pixel and Conversion API.

Please note before activating the Pinterest Connector in Tracklution: If you have previously included the pixel code in your website's header or footer HTML or e.g. via GTM, you must remove or deactivate existing pixels. Otherwise, the pixel will fire twice and lead to inconsistent data in your reporting. Pinterest Connector in Tracklution includes both the Pixel and Conversions API which allows Pinterest to deduplicate events. For Shopify's Native Pinterest tag, see more information below.

Disabling Shopify’s Native Pinterest Tracking

If you are using Tracklution for Pinterest conversion tracking, you may want to disable Shopify’s built-in Pinterest tracking to avoid duplicate events. Shopify’s Pinterest Sales Channel automatically installs Pinterest’s native pixel, and it does not allow separating the Catalog feed from Pixel tracking. This means if you keep the Pinterest Sales Channel active, Shopify will continue sending browser-side pixel events in addition to Tracklution’s server-side tracking.

To disable Shopify’s native Pinterest tracking:

  • In your Shopify admin, go to Settings → Apps and sales channels.
  • Find the Pinterest app in the list.
  • Click Uninstall and confirm.
  • Removing the Pinterest Sales Channel disables Shopify’s pixel tracking.

Sending Custom Events from Tracklution to Pinterest

Note that Pinterest only allows you to use the name "Custom" for your custom events, for them to be included in Pinterest's conversion reporting. This means that in your Pinterest conversion report, you will be able to see how many "Custom" events were made but you cannot see whether that event is scrolling, clicking, time, or something else. A workaround to this is to include the specification of your custom event as a parameter of your "Custom" event when setting up your custom data collection for these events before sending them to Tracklution. The included parameter will be visible under your "Custom" event in your conversion report. For more details on event codes for Pinterest refer to this guide: Pinterest: Add event codes.

If you are okay with all your custom events to have the same name "Custom" in your Pinterest conversion report, then you can just rename your custom events under the Settings-tab in Tracklution. OBS, since these events are sent server-to-server using the Pinterest API, the name must be all-lowercase: custom

Troubleshooting

Issues with a connector? Visit our Troubleshooting and FAQ to find answers to most common issues for each connector.

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied