Skip to main content
Customer and order tags are a practical way to enrich your SourceMedium data with additional business context. They can help you segment customers, classify orders, and support more detailed analysis in BI tools and ad hoc queries.

What tags are good for

Tags are useful when you want to add merchant-defined context that may not exist as a standard field yet. Common examples include:
  • customer VIP tiers or loyalty status
  • product category or merchandising group
  • order characteristics such as bundle, gift, or promo order
  • operational attributes such as fulfillment flow or shipping destination

Customer tagging

Customer tags help you group customers by traits or behaviors so you can analyze retention, LTV, and campaign response more effectively. Examples:
  • customers who repeatedly buy a certain category
  • customers with a high average order value
  • customers who reached a loyalty milestone

Order tagging

Order tags help you add context to purchases so you can analyze order mix, operational workflows, and campaign outcomes. Examples:
  • one-time vs subscription context
  • product family or product category
  • shipping or fulfillment exception handling
  • payment or promotional workflows

Important limitation for subscription reporting

Tags are still valuable enrichment signals, but for subscription classification SourceMedium increasingly relies on direct subscription-platform integrations and explicit line-level metadata where available. That means:
  • tags are helpful context
  • tags can still act as fallback support in some scenarios
  • tags should not be treated as the only source of truth for subscription behavior
If your subscription app emits explicit line-item subscription metadata, that is generally a stronger signal than tag-only logic.

Best practices

  • Keep tag naming consistent over time.
  • Use tags for business context, not as a substitute for primary platform integrations.
  • When possible, automate tags through your ecommerce platform or app workflows.
  • Document internally what your important tags mean so analysts interpret them consistently.

Platform resources