Integrations / Advertising
Pinterest Ads
Server-side conversion tracking via the Pinterest Conversions API.
Datafly Signal delivers first-party events to Pinterest Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Pinterest Ads expects.
Why route Pinterest Ads through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Pinterest Ads optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Pinterest Ads receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Pinterest Ads needs to attribute the event to the right session.
Click identifiers are captured and replayed
Signal stores click_id first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Pinterest Ads rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Pinterest Ads is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutdealer_contactedfinance_quote_requestedpagepurchaseservice_appointment_bookedtest_drive_bookedvehicle_savedvehicle_searchedvehicle_viewedview_itemVertical presets
Retail, Automotive. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Pinterest Ads documentation.
Frequently asked questions
Does Datafly Signal integrate with Pinterest Ads?
Yes. Datafly Signal delivers first-party events to Pinterest Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Pinterest Ads expects. The integration is included in every deployment at no additional cost.
How is server-side Pinterest Ads tracking different from the Pinterest Ads tag?
The Pinterest Ads tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Pinterest Ads from your server, so delivery does not depend on browser conditions.
What personal data is sent to Pinterest Ads?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so Pinterest Ads receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Pinterest Ads?
The blueprint ships with mappings for add_to_cart, begin_checkout, dealer_contacted, finance_quote_requested, page, purchase, service_appointment_booked, test_drive_booked, and more. Any event in your schema can be mapped to Pinterest Ads through pipeline configuration without a code change.
Do I need to keep the Pinterest Ads tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Pinterest Ads deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Pinterest Ads server-side?
See how Datafly Signal delivers first-party events to Pinterest Ads from infrastructure you control, with hashed identity and consent enforcement built in.