A Shopify merchant running Pinterest ads installs the official Pinterest app, sees the Pinterest Tag firing in the browser extension, and checks the box: conversions API, done. Three months later a Pinterest rep asks why Event Quality Score is sitting on Needs Improvement, and the honest answer is that nobody looked at it, because the app installing cleanly felt like confirmation enough.
That gap is common enough to be the default state for a Pinterest conversions API setup on most ecommerce platforms, not the exception.
- Shopify and WooCommerce's native Pinterest apps send some events server-side automatically, but that coverage has broken in production before without any visible error.
- An unclaimed domain gets conversion events flagged and partially dropped, independent of anything else in the setup.
- Pinterest treats
event_idas a hard requirement for deduplication. Meta only warns when it is missing and still counts the event. Pinterest's matching logic depends on it being present every single time. - Event Quality Score, not event volume, is the number that tells you whether the match is actually working.
The app installs the pixel. The API needs separate verification.
Pinterest's own documentation on the Conversions API lists action_source, event_id, event_name, event_time, and a user_data object carrying at least one match key, a hashed email, a hashed mobile advertising ID, or a client IP address paired with a user agent, as required fields on every event sent through the API. None of that is optional metadata; a payload missing a required field is the kind of thing that fails silently rather than throwing an error a merchant would actually see.
The native Shopify and WooCommerce apps handle a meaningful slice of this automatically once installed, which is exactly why most setup guides stop at "install the app." But automatic is not the same as reliable. A WooCommerce Pinterest plugin update shipped a regression where PageVisit events stopped sending server-side for any merchant whose Pinterest Tag was not also active, a dependency nothing in the setup flow had warned anyone about. The app was still installed. The toggle was still on. The events just stopped.
The same pattern shows up in Meta's Conversions API setup and TikTok's Events API setup: a native ecommerce-platform integration that looks finished because it was installed once, with no ongoing confirmation that it is still sending what it was sending on day one.
Claim the domain before debugging anything else
Pinterest requires advertisers to claim the website a Conversions API event originates from. An unclaimed domain does not just forfeit a feature; its events get flagged and partially dropped, which looks identical to a broken integration from the merchant's side. Checking domain claim status in Ads Manager's account settings takes under a minute and rules out the single most common reason a technically correct payload still underperforms.
The field Pinterest will not let you skip
Deduplication between the Pinterest Tag and the Conversions API runs on a shared event_id. Pinterest's documentation is explicit that the same event_id and event_name must be passed on every redundant copy of an event, and that Pinterest "retains the first event captured and removes duplicates within 48 hours" once it finds a match.
The detail worth sitting with is how differently Pinterest and Meta treat a missing event_id. Meta's Conversions API logs a warning and still counts the event, leaving deduplication to best-effort matching on other signals. Pinterest requires the field outright. Skip it on one side of a dual Tag-and-API setup and Pinterest has no basis for treating the browser event and the server event as the same checkout, which means a store can go from undercounting conversions, the exact problem the API exists to fix, to overcounting them by sending the same purchase twice.
Using the order number or transaction ID as the event_id, the same approach that works for Meta Conversions API setup, satisfies this cleanly because it is already unique and identical regardless of which system generates the event.
Event Quality Score: the number that actually confirms the setup works
A domain claim and a correctly deduplicated event still do not guarantee the match itself is strong. That is what Event Quality Score measures. Pinterest's own documentation on retrieving Event Quality Score describes it as a rating, visible per event source in Ads Manager, built from the customer identifiers an event carries, the relevant event metadata, and how cleanly duplicates are being identified across the Tag and the API combined.
The score resolves to three bands: Good, Fair, and Needs Improvement. A Good rating specifically requires strong customer identifiers, the applicable event metadata, and an overlap score above 90 percent between the Tag and the API, which is the number that confirms deduplication is working in practice rather than just configured on paper. Pinterest's own signal-priority breakdown rates IP address plus user agent, hashed email, and external ID as equally High priority for web conversion events, with the epik click ID, Pinterest's own identifier appended to ad click URLs, one tier down at Medium priority.
A store can send every checkout event successfully, with no errors anywhere in the pipeline, and still sit on a Fair or Needs Improvement score because those events carry only a hashed email and nothing else. Volume and quality are measured separately, and only one of them shows up by default when someone just checks whether events are arriving.
Checking volume or chasing a quality score: pick based on where the account actually is
If Pinterest events are not showing up in Ads Manager at all, start with the domain claim and the native app's data-sharing or integration settings before touching the payload itself, the same first move that resolves most Shopify conversion tracking issues on other ad platforms. That is a connectivity problem, and no amount of event_id precision fixes a domain that was never claimed.
If events are arriving and reporting looks roughly sane, the better question is the Event Quality Score sitting under Conversions in Ads Manager, not the raw event count. A store with full event volume and a Needs Improvement score is leaving match quality, and the bidding efficiency Pinterest's algorithm builds on top of it, on the table every day the gap goes unaddressed.
Either path converges on the same conclusion for a store running meaningful Pinterest spend alongside Meta, Google, and TikTok: native app integrations drift, and the only way to know which platform's server-side tracking is actually healthy right now is to check each one on its own terms. A fixed-scope tracking setup engagement wires the event_id and identifier logic correctly across every platform at once, and where Pinterest is one symptom among several, a tracking audit traces each platform's gap back to the specific setting or missing field causing it before anything gets rebuilt.
