Pinterest Offline Conversions: In-Store Sales Through the API and File Upload
Pinterest offline conversions are the sales a browser pixel can never see - purchases in a physical store, orders closed by a sales team, phone transactions. Pinterest accepts them as one of the three conversion kinds the Conversions API supports - web, in-app, and in-store/offline - and keeps a no-code fallback for teams without development resources.
Two Channels Into the Platform
| Channel | What it takes | Who it fits |
|---|---|---|
| Conversions API, offline events | Server-side posts with the in-store conversion kind | Teams already running a delivery pipeline |
| Offline conversions file in Ads Manager | An uploaded file attributed to campaigns | Teams without development resources |
The API path treats offline as a first-class kind: the same event schema carries in-store conversions alongside web and app ones, which keeps mixed funnels - click-to-store, online research with offline purchase - inside one reporting model. The file path needs no development at all: upload the offline conversions file into Ads Manager and Pinterest attributes those conversions to campaigns from the file. Reporting for uploaded events is reviewed in Ads Manager - Pinterest documents the offline conversion events reporting view for exactly this.
What Offline Events Must Carry
An offline event is born without a page visit, a cookie, or a client-side click ID: the platform matches it against ad exposure using the identity the record carries - hashed email or phone where the point of sale captured them, plus the transaction identifiers your CRM assigns. That makes the offline discipline identical to the server-side one: normalize and hash identifiers to specification, keep a stable ID per transaction, and accept that matching quality depends entirely on how much identity the record carries. The matching mechanics are in match keys and match rate.
Fitting Offline Into the Pinterest Cluster
Because in-store rides the same Conversions API, the cluster's rules carry over unchanged: deduplication by event identity, delivery close to real time where the source allows, and the quality scoring that grades payload completeness. The wiring for lead and CRM-style delivery is covered in the complete guide, and a no-code first test runs through Pixel Activator before the file or API path goes live; Most automates recurring delivery alongside four other networks.
Frequently asked questions
Sources
Sources
- Manual testing and validation: Pixel Activator fires free test events while you tune parameters.
- Automated delivery: Most routes conversions from your tracker or CRM continuously, with deduplication and retries handled.