Debugging Server & Hybrid Tracking

In hybrid tracking architectures, conversion events may originate from backend systems such as payment processors, CRM workflows, or webhook automations.

Debugging requires validating identity continuity, event timing, and configuration consistency.

Confirming Server SDK Initialisation

Ensure that the server runtime is correctly configured.

Verify that:

• the server SDK is initialised using a valid secret key
• environment variables are correctly loaded in production
• event tracking calls execute without runtime errors

Incorrect key usage or environment configuration can silently prevent server events from being sent.

Validating Visitor Identity Linkage

Hybrid attribution depends on linking server-side conversions to prior browser activity.

Common verification steps:

• confirm the browser sends the visitor identifier to backend endpoints
• ensure server events include the correct visitor_id or user identity
• validate that consent state allows identity persistence

Missing identity linkage may result in:

• unattributed conversions
• fragmented customer journeys
• delayed insight generation

Checking Webhook & Postback Timing

Server conversion signals may be triggered asynchronously.

Typical causes of timing discrepancies include:

• delayed payment confirmation events
• queued job processing
• retry mechanisms in webhook systems

When debugging, confirm:

• webhook delivery logs indicate successful execution
• conversion events are emitted after transaction finalisation
• duplicate retries do not generate conflicting signals

Ensuring Site Context Consistency

In multi-site environments, incorrect site association may distort attribution reporting.

Validate that:

• site_id values match the intended digital property
• per-event overrides are used intentionally
• staging and production environments are not mixed

Consistent site context ensures conversion signals contribute to accurate growth intelligence.

Diagnosing Conversion Duplication

Duplicate conversion events can occur when:

• both browser and server emit the same outcome signal
• webhook retries trigger multiple tracking calls
• event naming conventions differ across systems

Mitigation strategies include:

• implementing idempotent conversion identifiers
• centralising conversion emission logic
• auditing event logs during integration testing

Careful hybrid debugging ensures that revenue attribution models reflect real customer behaviour rather than technical artefacts.