Skip to content

Commit 2790a3f

Browse files
committed
fix inconsistencies
1 parent d89031d commit 2790a3f

4 files changed

Lines changed: 60 additions & 26 deletions

File tree

help-center/common-analyses/subscription-program-retention.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Use this guide to assess subscription retention or churn and how subscription cu
1515

1616
## Key concepts
1717

18-
- Subscription orders can be flagged in `obt_orders` through fields such as `is_subscription_order` and `is_order_recurring_subscription`.
18+
- Subscription orders can be flagged in `obt_orders` through fields such as `is_subscription_order` and `is_recurring_subscription_order`.
1919
- Subscription lines can be flagged in `obt_order_lines` through fields such as `is_order_line_subscription`, `order_line_type`, and `subscription_order_sequence`.
2020
- If you’re validating against your subscription platform, start by aligning the definition of `active`, `new`, and `cancelled`.
2121
- If the cart can mix subscription and one-time items, line-level analysis is usually more accurate for product questions.
@@ -44,6 +44,7 @@ SELECT
4444
FROM `your_project.sm_transformed_v2.obt_orders`
4545
WHERE is_order_sm_valid = TRUE
4646
AND is_subscription_order = TRUE
47+
AND order_processed_at_local_datetime >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 365 DAY)
4748
GROUP BY 1, 2
4849
ORDER BY month_start DESC, subscription_order_sequence;
4950
```

help-center/core-concepts/data-definitions/subscription-flags.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Common subscription-related fields in `your_project.sm_transformed_v2.obt_orders
1616
- `subscription_order_sequence`: first vs recurring subscription classification
1717
- `subscription_order_index`: sequential index of subscription orders per customer when available
1818
- `is_first_subscription_order`: convenience flag derived from `subscription_order_sequence`
19-
- `is_order_recurring_subscription`: convenience flag derived from `subscription_order_sequence`
19+
- `is_recurring_subscription_order`: convenience flag derived from `subscription_order_sequence`
2020

2121
## Line-level fields
2222

help-center/faq/account-management-faqs/are-you-utilizing-customer-and-order-tagging-for-deeper-enrichment-of-your-data.mdx

Lines changed: 54 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -4,34 +4,67 @@ description: "How to use Shopify customer and order tags to enrich your SourceMe
44
sidebarTitle: "Customer & Order Tagging"
55
icon: 'question-mark'
66
---
7-
**Customer and order tagging is a critical tool for enriching your data and gaining deeper insight into your customers and their purchasing behaviors. By tagging customers and orders, you can categorize and organize them based on a wide range of criteria, including demographics, purchase history, and behavior patterns.**
7+
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.
88

9-
### Customer Tagging
9+
## What tags are good for
1010

11-
By tagging customers based on their behavior or attributes, you can gain insights into their preferences and create personalized marketing campaigns to increase their loyalty and lifetime value.
11+
Tags are useful when you want to add merchant-defined context that may not exist as a standard field yet.
1212

13-
For instance, you can tag customers who frequently purchase a specific product or category, those who have made a large purchase, or those who have abandoned their cart before completing their purchase. With this information, you can create targeted email campaigns, offers, or product recommendations to engage and retain these customers.
13+
Common examples include:
1414

15-
### Order Tagging
15+
- customer VIP tiers or loyalty status
16+
- product category or merchandising group
17+
- order characteristics such as bundle, gift, or promo order
18+
- operational attributes such as fulfillment flow or shipping destination
1619

17-
By tagging orders based on their characteristics, you can gain insights into the effectiveness of your marketing campaigns, identify trends, and optimize your inventory and pricing strategies.
20+
## Customer tagging
1821

19-
For example, you can tag orders based on the type of order (for example, one time or subscription), the product category, the shipping destination, or the payment method used. With this information, you can identify the most effective marketing channels and campaigns, optimize your pricing and inventory strategies to align with customer preferences, and identify areas for improvement in your fulfillment process.
22+
Customer tags help you group customers by traits or behaviors so you can analyze retention, LTV, and campaign response more effectively.
2023

21-
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. Tags should be treated as helpful context and legacy fallback support, not the only source of truth for subscription behavior.
24+
Examples:
2225

23-
It's possible to use both customer and order tagging simultaneously. For instance, you can apply tags to customers and orders based on demographic data received from a service such as Klaviyo. This would enable you to gain a better understanding of customer profiles and order patterns, tracking factors such as age, gender, and behavioral information.
26+
- customers who repeatedly buy a certain category
27+
- customers with a high average order value
28+
- customers who reached a loyalty milestone
2429

25-
Overall, utilizing customer and order tagging is an essential component of any data-driven marketing or sales strategy. By taking advantage of this powerful tool, you can gain a deeper understanding of your customers and their needs, and use that knowledge to drive growth and success for your business.
30+
## Order tagging
2631

27-
<Accordion title = "Follow these links for more info on tagging for your specific e-commerce platforms">
28-
- [Shopify](https://help.shopify.com/en/manual/shopify-admin/productivity-tools/using-tags)
29-
- [Shopify Flow - Automatic Tagging](https://shopify.dev/docs/apps/flow)
30-
- [Stripe](https://stripe.com/docs/api/metadata)
31-
- [Chargebee](https://www.chargebee.com/docs/2.0/custom_fields.html)
32-
- [Salesforce Commerce Cloud](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)
33-
- [Recharge](https://support.rechargepayments.com/hc/en-us/articles/360008829873-Using-Shopify-order-and-customer-tags)
34-
- [Skio](https://integrate.skio.com/skio/extras/subscription-tags)
35-
- [Stay AI](https://stay.ai/features-subscription-basics/)
36-
- [SPINS](https://www.spins.com/tag/shelf-tags/)
37-
</Accordion>
32+
Order tags help you add context to purchases so you can analyze order mix, operational workflows, and campaign outcomes.
33+
34+
Examples:
35+
36+
- one-time vs subscription context
37+
- product family or product category
38+
- shipping or fulfillment exception handling
39+
- payment or promotional workflows
40+
41+
## Important limitation for subscription reporting
42+
43+
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.
44+
45+
That means:
46+
47+
- tags are helpful context
48+
- tags can still act as fallback support in some scenarios
49+
- tags should not be treated as the only source of truth for subscription behavior
50+
51+
If your subscription app emits explicit line-item subscription metadata, that is generally a stronger signal than tag-only logic.
52+
53+
## Best practices
54+
55+
- Keep tag naming consistent over time.
56+
- Use tags for business context, not as a substitute for primary platform integrations.
57+
- When possible, automate tags through your ecommerce platform or app workflows.
58+
- Document internally what your important tags mean so analysts interpret them consistently.
59+
60+
## Platform resources
61+
62+
- [Shopify tagging](https://help.shopify.com/en/manual/shopify-admin/productivity-tools/using-tags)
63+
- [Shopify Flow - Automatic Tagging](https://shopify.dev/docs/apps/flow)
64+
- [Stripe metadata](https://stripe.com/docs/api/metadata)
65+
- [Chargebee custom fields](https://www.chargebee.com/docs/2.0/custom_fields.html)
66+
- [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)
67+
- [Recharge order and customer tags](https://support.rechargepayments.com/hc/en-us/articles/360008829873-Using-Shopify-order-and-customer-tags)
68+
- [Skio subscription tags](https://integrate.skio.com/skio/extras/subscription-tags)
69+
- [Stay AI subscription basics](https://stay.ai/features-subscription-basics/)
70+
- [SPINS shelf tags](https://www.spins.com/tag/shelf-tags/)

yaml-files/latest-v2-schemas-10-20-25.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -870,8 +870,8 @@
870870
"business_domain": "Orders",
871871
"refresh_frequency": "Daily",
872872
"primary_use_case": "Analytics \u0026 BI",
873-
"column_name": "is_order_recurring_subscription",
874-
"original_column_name": "is_order_recurring_subscription",
873+
"column_name": "is_recurring_subscription_order",
874+
"original_column_name": "is_recurring_subscription_order",
875875
"data_type": "BOOL",
876876
"is_nullable": "true",
877877
"table_description": "Order analytics table for revenue, profitability, refunds, and channel performance analysis. Grain: One row per sm_order_key. Date field: order_processed_at_local_datetime. Critical filters: is_order_sm_valid \u003d TRUE (exclude test/cancelled orders); sm_channel for segmentation. Platform caveat: TikTok Shop coverage may be limited. Key joins: obt_order_lines via sm_order_key (1:many); obt_customers via sm_customer_key (many:1); dim_orders via sm_order_key (1:1). ",
@@ -25438,4 +25438,4 @@
2543825438
"stats_sample_percent": "10.0",
2543925439
"stats_method": "DEMO_SAMPLE_10_RECOMPUTED",
2544025440
"categorical_values_array": []
25441-
}]
25441+
}]

0 commit comments

Comments
 (0)