Setup & Integration

Multi-Site & Multi-Product Tracking Best Practice

Design tracking structures that maintain attribution continuity across domains, products, and growth surfaces.

Understanding Multi-Surface Growth Environments

Many organisations operate across multiple digital properties, such as:

  • marketing websites
  • product applications
  • ecommerce storefronts
  • campaign microsites
  • partner landing pages

User journeys often move between these surfaces before a conversion occurs.

Tracking architecture must therefore ensure signal continuity and identity stability.

Typical Cross-Surface User Journey

A simplified multi-site journey may include:

  • visitor lands on a campaign landing page
  • visitor explores the main marketing website
  • visitor signs up inside the product application
  • visitor converts later via checkout or sales interaction

Without structured tracking, attribution may become fragmented across domains.

To maintain reliable attribution:

  • initialise tracking consistently across all properties
  • define clear site_id values per digital surface
  • enable cross-domain identity persistence where applicable
  • ensure conversion events are associated with the correct site context

This allows analytics models to evaluate:

  • which surfaces generate demand
  • which surfaces close revenue
  • how journeys move between them

Using Site Context in Event Tracking

In multi-product or multi-domain environments, events may need explicit site association.

Example:

TS
<script>
  // Visitor exploring marketing site
  Mark.track('feature_page_viewed', {
    site_id: 'marketing-site-uuid'
  });

  // Conversion occurring in product environment
  Mark.conversion('subscription_started', {
    site_id: 'product-app-uuid',
    plan: 'scale'
  });
</script>

This structure enables OneLence to:

  • map cross-surface journeys
  • assign revenue influence correctly
  • evaluate funnel performance per product or domain

Cross-Domain Attribution Considerations

Reliable multi-site tracking often requires:

  • shared identity persistence configuration
  • consistent consent handling behaviour
  • coordinated campaign parameter usage
  • aligned event naming conventions

These practices reduce signal fragmentation and improve attribution confidence.

Measurement Insights Enabled

A well-designed multi-surface tracking architecture supports:

  • cross-product growth analysis
  • lifecycle attribution modelling
  • partner or campaign performance evaluation
  • expansion and upsell signal visibility

These insights are particularly relevant for:

  • SaaS ecosystems
  • marketplaces
  • ecommerce brand portfolios
  • multi-brand organisations