Salesforce opportunity events → server-side CAPI

Enterprise B2B revenue rarely behaves like ecommerce checkout tracking. A campaign click may create an anonymous visit today, a lead record next week, an SDR meeting two weeks later, and an opportunity that only closes after procurement, security review, legal redlines, and executive signoff. If paid media is judged only on the original browser form event, the business ends up optimizing toward cheap top-of-funnel volume rather than opportunities that actually move through pipeline.

Multi-touch journeys also make browser-only reporting misleading for RevOps. The same buying committee can interact through ads, webinars, partner referrals, outbound sequences, and account-based nurture before the sales team updates Salesforce with the milestone that matters. Routing Salesforce opportunity and engagement changes into TrackLayer creates a cleaner operating model: media teams get server-side conversion truth, RevOps keeps its governance, and finance can reconcile attributed revenue against the CRM system of record instead of arguing over disconnected pixels.

The safest implementation keeps Salesforce, the relay service, and TrackLayer clearly separated. Salesforce emits the business event, the relay handles authentication and normalization, and TrackLayer applies routing, identity controls, and destination-specific event mapping.

Connected App essentials
callback URL → https://ingest.tracklayer.io/salesforce/oauth/callback
OAuth scopes → api refresh_token offline_access
integration user → tracklayer.integration@company.com
environment split → sandbox app and production app kept separate

POST https://login.salesforce.com/services/oauth2/token
grant_type=authorization_code
code=AUTH_CODE
client_id=CONNECTED_APP_CONSUMER_KEY
client_secret=CONNECTED_APP_CONSUMER_SECRET
redirect_uri=https://ingest.tracklayer.io/salesforce/oauth/callback

Webhook subscription targets
Opportunity → stage changes, amount changes, close date, owner, primary campaign source
Lead → status, source, qualification, conversion markers
Contact → account join, lifecycle changes, contactability fields
Account → named account status, segment, territory, parent account
Campaign Member → responded, status progression, campaign influence
Task → completed outreach, meeting logged, follow-up activity

{
  "event": "opportunity_stage_changed",
  "event_id": "opp_0068c00001ABCDQ_stage_closed_won",
  "occurred_at": "2026-04-23T09:42:00Z",
  "salesforce": {
    "account_id": "0018c00002XYZ12",
    "opportunity_id": "0068c00001ABCDQ",
    "contact_id": "0038c00004MNO56",
    "campaign_id": "7018c000000PQRS",
    "owner_id": "0058c000000LMN9"
  },
  "revenue": {
    "amount": 240000,
    "currency": "USD",
    "arr": 120000
  },
  "stage": "Closed Won"
}

Routing example
Lead status = MQL → canonical = marketing_qualified_lead → destination event = Lead
Opportunity stage = Qualification → canonical = sales_qualified_opportunity → destination event = QualifiedLead
Opportunity stage = Proposal/Price Quote → canonical = pipeline_advanced → destination event = CustomPipelineStage
Opportunity stage = Closed Won → canonical = closed_won → destination event = Purchase

Your exact stage names will vary by Salesforce org, but the important move is to map them into a small canonical vocabulary. That gives paid media, analytics, and warehouse exports one shared ladder of business intent instead of a dozen object-specific labels.

Enterprise revenue attribution needs more than an opportunity amount pushed into a single conversion field. Contract value, committed ARR, implementation services, geographic region, product family, and expected go-live timing all change how marketing should value a pipeline event. A large services-heavy deal may produce strong bookings but weak software expansion potential, while a smaller platform-first opportunity may be exactly the account profile the business wants to scale.

The durable pattern is to emit one canonical event with multiple revenue dimensions. Ad platforms can optimize on a simplified value when needed, while the warehouse keeps the richer contract context for cohorting, ROI analysis, and board-level reporting. That prevents the classic enterprise problem where the ad account says one thing, Salesforce says another, and finance trusts neither.

Account-based motion breaks when every contact is treated as an independent conversion. A target account may have a champion, economic buyer, security reviewer, and two evaluators, all of whom interact with campaigns before a single opportunity is created. If each person fires a separate conversion, reporting overstates success and bidding models learn the wrong lesson.

In practice, TrackLayer should emit the account-level conversion once, then preserve contact-level evidence as supporting identifiers and engagement metadata. That keeps ad platforms from learning duplicates while your internal attribution model can still understand which stakeholders influenced the deal.

Salesforce stage changes tell you when the opportunity moved. Outreach and Gong explain why it moved. Forwarding Outreach task completion and Gong call records into the same event stream gives the pipeline more context: a demo really happened, a follow-up sequence completed, procurement attended the call, or a discovery meeting occurred before the rep updated the opportunity stage.

These engagement events usually should not count as final conversions in ad platforms. They are better used as supporting quality signals, audience suppressors, sales activity indicators, and internal attribution features that make the account journey more legible.