Pinterest Tracking
Change — subscription rebill reporting: Two things changed for auto-order rebills on Pinterest:
Rebills are now reported as the custom event
RecurringSubscriptionPaymentinstead ofcheckout.Rebills now actually get through to Pinterest. Previously every rebill was being silently dropped due to missing browser-level identifiers.
See "Subscription (auto order) event handling" below.
UltraCart now supports the Pinterest Conversation API which is a server-to-server method of sending conversion information to Pinterest.
This short tutorial will guide you through the process of configuring Pinterest tracking on your StoreFront. The first pre-requisite is to make sure that you have setup a pixel within Pinterest.
You will need to gather the following pieces of information from your Pinterest Account:
Account Id
Pixel Id
Conversation Access Token (Pinterest document on how to obtain - and https://developers.pinterest.com/docs/conversions/conversions/ )
Once you have the three values, navigate to StoreFront → Privacy & Tracking → Other → Pinterest.
Enter the three values in the field shown below and then click on Save.
At this point UltraCart will begin sending over server-to-server conversion information to Pinterest.
All of the logging of the communication with the Pinterest Conversion API will be visible within Integration Logs.
Subscription (auto order) event handling
Event mapping
Order type | Event sent to Pinterest |
|---|---|
One-time purchase |
|
First purchase of an auto order (subscription) |
|
Auto-order rebill (recurring payment) |
|
Rebill events carry order value, currency, and line items.
Two changes shipped together
1. Rebills now use a separate event name. Previously, rebills were reported as checkout, which inflated the standard checkout count in Pinterest Ads Manager and fed the optimizer misleading conversion rates. They are now isolated on a dedicated custom event.
2. Rebills now actually reach Pinterest. Previously, UltraCart's Pinterest integration required a user's browser user-agent and IP address to be present on every order before sending the postback. Subscription rebills are generated server-side and have neither, so every rebill was being silently dropped — Pinterest saw no rebill activity at all. For rebills specifically, this requirement has been relaxed: an email address is now the minimum identifier for a rebill to be sent. For one-time purchases and first auto-order purchases, the stricter requirement remains in place to preserve best match quality.
Expectation-setting
The
checkoutcount stays clean for actual checkouts — no surprise drop.A brand-new
RecurringSubscriptionPaymentstream will appear in your Pinterest reporting. This is rebill activity that was never reaching Pinterest before.
Merchant action required — register the custom event
To optimize Pinterest campaigns against rebill revenue:
Sign in to Pinterest Ads Manager and open Events Manager.
Select your Pinterest tag / conversion source.
Create a new custom event named
RecurringSubscriptionPayment.Save. The event will now be selectable for campaign optimization and in reporting.
Related platform docs
The custom event name RecurringSubscriptionPayment is consistent across Meta, TikTok, and Pinterest. See also: Facebook Analytics & Custom Audiences, TikTok Tracking, Snapchat Tracking, Twitter Tracking, Taboola Tracking.