B2B vs DTC conversion tracking patterns
Pipeline SaaS and e-commerce shops share ad platforms but not conversion logic. Match keys, event timing, and what you optimize for differ — and your tracking setup should reflect that.
- B2B
- DTC
- funnel events
Problem: Your B2B SaaS copied a DTC e-commerce tracking setup from a blog post. Meta optimizes for Purchase events that happen once a quarter, while your real funnel milestone is a demo booked on day two.
Different conversion moments
DTC tracks AddToCart, InitiateCheckout, and Purchase with value and SKU data. The conversion loop is minutes to days. B2B tracks SignUp, demo requests, trial starts, and eventually Purchase or Subscribe — often weeks apart.
Sending the wrong milestone trains algorithms on noise. A B2B app sending only PageView and Purchase gives Meta almost nothing between those events.
Use the canonical catalog in Events — BookDemo, StartTrial, Purchase — and map only what you optimize for.
Match keys by audience
DTC benefits from click IDs captured at product view and preserved through checkout. B2B often converts on work email after multiple sessions — email hash match becomes the primary key.
Prioritize CAPI setup for platforms that receive spend: LinkedIn and Google for pipeline; Meta and TikTok for DTC discovery.
trackstack.capture("SignUp", {
email: lead.workEmail,
eventId: `signup_${lead.id}`,
});
trackstack.capture("Purchase", {
email: order.email,
value: order.totalCents / 100,
currency: "USD",
transactionId: order.id,
eventId: `purchase_${order.id}`,
});Value and LTV signals
DTC should send actual order value on every Purchase. B2B may send value on closed-won deals but should use StartTrial for mid-funnel optimization when deal size varies.
Do not inflate value fields — platforms deprioritize inconsistent value signals.
Sales-assisted conversions
B2B deals often close in Salesforce after ad touchpoints weeks earlier. Offline conversion import and CRM-connected CAPI bridge this gap. SDK events cover product milestones; CRM sync covers closed revenue.
Read offline conversions and CRM feedback loops for the full B2B loop.
Instrumentation ownership
Growth engineering should own canonical events in code. Marketing can keep pixels for creative testing, but revenue milestones belong next to auth and billing webhooks.
Sources
Official documentation and references cited in this article.
More in Guides
Google Enhanced Conversions for web apps
Enhanced Conversions improves Google's match rate by sending hashed first-party data with each conversion. This guide covers what to hash, where to fire events, and how to verify payloads land.
Read postLinkedIn and TikTok CAPI: a practical overview
Beyond Meta and Google, LinkedIn and TikTok have server-side conversion APIs with their own payload shapes and match keys. Here is what each expects and where teams get stuck.
Read postHow to set up Meta CAPI in Next.js without GTM
Skip Google Tag Manager. Wire first-party Meta CAPI in Next.js with an SDK that handles hashing, deduplication, retries, and delivery logs from your existing app code.
Read postReady to fix your conversion pipeline?
Install the TrackStack SDK, route events to Meta and Google, and verify delivery from one dashboard.