Skip to content

Stape.io. Incoming webhooks to sGTM. Push CRM and OMS orders into server GTM.

What this means for your store

B2B wholesale and hybrid ecommerce lose half their funnel in the browser. A US industrial parts distributor demos on Tuesday; Salesforce marks the deal won Thursday. Warehouse software ships the pallet Friday. None of those milestones touch the storefront - yet Google Ads offline conversions and lifecycle dashboards still need them. Incoming webhooks let CRM, payment, and OMS systems POST JSON directly to your Stape sGTM endpoint so server tags fire without a page load.

Scenario on a real storefront

A Chicago B2B wholesale electronics supplier uses Stripe Payment Links for trade accounts. When checkout.session.completed posts to collect.brand.com/hooks/stripe, a Data Client parses the payload and triggers GA4 MP plus Meta CAPI - attributing the $4,200 order to the original Google Ads click stored in session metadata:

// Stape custom domain endpoint
POST https://collect.brand.com/hooks/stripe
Content-Type: application/json
X-Webhook-Secret: {{shared_secret}}

// Server GTM - Client: Webhook / Data Client
  Parse JSON → event_name = purchase
  transaction_id = body.data.object.id
  value = body.data.object.amount_total / 100
  client_id = body.data.object.metadata.ga_client_id  // from checkout form

// Tags fired server-side only (no browser):
  - GA4 Measurement Protocol
  - Meta CAPI Purchase
  - Google Ads Offline (optional)

// Stripe dashboard → Webhooks → signing secret in sGTM variable

What to do next

  • Your engineering team verifies webhook signatures (Stripe, Shopify) in sGTM before firing paid conversion tags - unsigned endpoints attract spam hits that inflate ad platform revenue.
  • Analytics ops must map client_id from checkout metadata into the webhook payload; without it, GA4 MP attributes B2B revenue to orphan sessions.
  • DevOps should maintain separate test vs live webhook URLs per environment so staging orders never pollute production Google Ads or Meta accounts.

Bottom line

Authenticate every webhook POST, attach client identifiers, and route only confirmed transactions to conversion APIs - CRM and payment events extend measurement beyond the browser.