Stape.io. Pinterest Conversions API. Server-side catalog sales for discovery ads.

What this means for your store

Home décor and gift retailers bet heavily on Pinterest catalog ads - then wonder why in-platform ROAS looks strong while Shopify revenue lags. Pinners save products on mobile, switch devices, and checkout days later; browser tags lose epik and click identifiers along the way. Pinterest Conversions API sends server-side checkout events from Stape sGTM with matching event_id so discovery campaigns optimise on complete purchase data, not partial browser signals.

Scenario on a real storefront

A Nashville home décor merchant ($95 AOV, 2,400-SKU Pinterest catalog) fires checkout from sGTM on the same dataLayer purchase that feeds GA4. The Stape Pinterest tag includes epik from the landing cookie and product IDs aligned to the catalog feed:

// Server GTM - Tag: Pinterest Conversions API (Stape)

event_name: checkout
action_source: web
event_time: {{event_timestamp}}
event_id: {{event_id}}               // dedup with browser Pinterest tag
custom_data:
  currency: USD
  value: {{event_data.value}}
  order_id: {{event_data.transaction_id}}
  contents: {{pinterest_items}}      // content_ids must match catalog feed SKUs
user_data:
  client_ip_address: {{client_ip}}
  client_user_agent: {{user_agent}}
  epik: {{epik}}

// Pinterest Ads → Conversions → Web + API deduplication enabled

What to do next

• Your feed management team aligns content_ids across Pinterest catalog, dataLayer, and CAPI - SKU format mismatches break dynamic retargeting.
• CRM and legal hash email in user_data only with consent and only where Pinterest enhanced matching is permitted for your market.
• Performance marketing judges Pinterest CAPI over 7–14 days, not hourly dashboards - low-volume accounts show delayed reporting after deploy.

Bottom line

Pinterest CAPI via Stape strengthens discovery-channel measurement - deduplicate with the browser tag, keep epik in server hits, and match product IDs to your catalog feed.