Destinations
A destination is an ad platform Pivolio sends enriched events to, server-side, through that platform’s conversions API. You connect it once with credentials, Pivolio verifies them, and from then on every matching event is transformed into the platform’s payload shape and delivered — with hashed PII, click IDs, and the attribution context already attached.
Destinations are configured per workspace, so two brands sharing an account never share a pixel.
Nine platforms tracked, four delivered to
Pivolio recognizes click IDs from nine ad platforms and uses all nine for attribution. It can only deliver conversions to four of them.
Click source only means exactly that: LinkedIn, Microsoft, Pinterest, Snapchat and X clicks are captured, stored against the person, and credited in your attribution reports — but Pivolio never sends a conversion back to those platforms. There is no adapter to configure and none is hidden behind a setting. If you need server-side delivery to one of them today, you need another tool for that platform.
gbraid and wbraid are captured but deliberately never used to stitch
identity. They are Google’s privacy-aggregated iOS click IDs and are too coarse
to identify a person — treating them as identifiers would merge unrelated
visitors.
The shape of every setup
All four destinations follow the same three moves, whatever the platform calls its credentials:
Enter credentials
Open Destinations, pick the platform, and supply what it needs — a pixel identifier and an access token for Meta, TikTok and Reddit, or an OAuth connect for Google Ads.
Verify
Pivolio calls the platform with the credentials you gave before saving anything. A typo fails here, not silently at 3am on a Saturday.
Enable and map
Turn the destination on. Each platform ships default event mappings; Google Ads ships none, because every event has to point at one of your conversion actions.
Credentials are encrypted at rest and never returned by the API. Once saved, the dashboard shows you that a secret exists — it cannot show you the secret. Rotating a token means pasting a new one, not editing the old one.
The four guides
Conversions API — pixel ID and a system-user token.
Data Manager API — OAuth, and mapping-only delivery.
Events API 2.0 — pixel code and access token.
Conversions API v3 — a2_ pixel ID, and a 7-day age cap.
Related
- Event mappings — how a Pivolio event name becomes a platform event name.
- Consent rules — gate a destination on the categories the visitor actually granted.
- Troubleshooting — delivery statuses, error codes, and what to check when nothing arrives.
Events are tracked, stored and reported on every plan, but dispatch to destinations requires an active plan or trial. An unsubscribed workspace collects everything and delivers nothing.