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

# Are you utilizing customer and order tagging for deeper enrichment of your data?

> How to use Shopify customer and order tags to enrich your SourceMedium data with demographics, purchase patterns, and marketing insights

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

* [Shopify tagging](https://help.shopify.com/en/manual/shopify-admin/productivity-tools/using-tags)
* [Shopify Flow - Automatic Tagging](https://shopify.dev/docs/apps/flow)
* [Stripe metadata](https://stripe.com/docs/api/metadata)
* [Chargebee custom fields](https://www.chargebee.com/docs/2.0/custom_fields.html)
* [Salesforce Commerce Cloud metadata](https://documentation.b2c.commercecloud.salesforce.com/DOC3/index.jsp?topic=%2Fcom.demandware.dochelp%2Fcontent%2Fb2c_commerce%2Ftopics%2Fsearch_engine_optimization%2Fb2c_creating_page_meta_tag_rules.html)
* [Recharge order and customer tags](https://support.rechargepayments.com/hc/en-us/articles/360008829873-Using-Shopify-order-and-customer-tags)
* [Skio subscription tags](https://integrate.skio.com/skio/extras/subscription-tags)
* [Stay AI subscription basics](https://stay.ai/features-subscription-basics/)
* [SPINS shelf tags](https://www.spins.com/tag/shelf-tags/)