Skip to main content

​
Set Up S2S and Web Conversion Tracking

  • Capture click identifiers on web/client side.
  • Send conversion events server-side (S2S) for reliability.
  • Include identity and transaction fields for stitching and dedupe.

​
Steps

1

Enable tracking on target links or campaigns

Confirm conversion tracking is enabled before sending events.
2

Capture click identity client-side

Preserve click identifier and customer identity context.
3

Send conversion events server-side

Send lead, sale, or custom events from trusted backend paths.
4

Include financial/status fields intentionally

Set currency, value, quantity, transaction ID, and status explicitly.
5

Verify cross-page visibility

Validate in Conversions, Events, Customers, and scoped Analytics pages.

​
Required quality fields

  • stable customer identity (email or external customer ID)
  • unique transaction/event IDs for dedupe-sensitive events
  • explicit event type and event timestamp

​
Validation checklist

  • Confirm the change appears in the correct workspace context.
  • Confirm expected UI behavior on desktop and mobile.
  • Confirm analytics/events reflect the action.
  • Confirm role/permission boundaries are respected.
  • /help/conversions/manage-customers-events-and-statuses
  • /user-guides/manual/data/conversion-tracking-setup-playbook