> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linquid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up S2S and Web Conversion Tracking

> Implement lead/sale/custom conversion tracking and validate attribution

# Set Up S2S and Web Conversion Tracking

## Recommended architecture

* 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

<Steps>
  <Step title="Enable tracking on target links or campaigns">
    Confirm conversion tracking is enabled before sending events.
  </Step>

  <Step title="Capture click identity client-side">
    Preserve click identifier and customer identity context.
  </Step>

  <Step title="Send conversion events server-side">
    Send `lead`, `sale`, or custom events from trusted backend paths.
  </Step>

  <Step title="Include financial/status fields intentionally">
    Set currency, value, quantity, transaction ID, and status explicitly.
  </Step>

  <Step title="Verify cross-page visibility">
    Validate in Conversions, Events, Customers, and scoped Analytics pages.
  </Step>
</Steps>

## 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.

## Related

* `/help/conversions/manage-customers-events-and-statuses`
* `/user-guides/manual/data/conversion-tracking-setup-playbook`