DTC Glossary
Clear definitions for connected work.
Plain-English explanations of Shopify, conversion, acquisition, lifecycle, analytics, operations, automation, SEO and GEO concepts.


Connected by design
Shared language reduces expensive ambiguity
Teams can use the same word while measuring different audiences, windows or events. Each glossary entry connects the definition to a practical decision and reminds the reader which assumptions must be stated.
- Search by the term your team uses
- Check the measurement boundary
- Connect it to the affected decision
- Agree one definition in the working brief
System view
The parts work better when their interfaces are visible.
Every module has an owner, an input, an output and a decision it supports.
Commerce economics
Contribution, order value, payback and inventory.
Customer behavior
Conversion, retention, churn and repeat purchase.
Shopify technology
Themes, Functions, Markets, apps and architecture.
Growth execution
Attribution, creative, lifecycle and landing continuity.
Measurement
Cohorts, guardrails, power, events and data quality.
Discovery
Search intent, structured data, SEO, GEO and internal links.
Knowledge index
Find the term, then define the boundary.
Search sixty definitions across commerce, customer behavior, technology, growth and measurement.
Accessibility
Design and engineering practices that let people with varied abilities perceive and operate an experience.
Open resource ↗App proxy
A Shopify route that lets an app serve storefront content through the shop domain.
Open resource ↗Attach rate
The share of eligible purchases that include a related item, feature or offer.
Open resource ↗Attribution window
The time period during which an interaction can receive credit for a conversion.
Open resource ↗Average order value
Revenue divided by the number of orders in the selected period.
Open resource ↗Blended efficiency ratio
Total revenue divided by a broader acquisition investment over the same period.
Open resource ↗Canonical URL
The preferred URL declared for substantially similar or duplicate pages.
Open resource ↗Churn
The loss of subscribers or customers from an active relationship during a defined period.
Open resource ↗Cohort analysis
Comparison of groups that share a starting event or characteristic over time.
Open resource ↗Composable commerce
An architecture that combines replaceable commerce capabilities through defined interfaces.
Open resource ↗Consent management
The controls and records used to respect a person’s communication and tracking choices.
Open resource ↗Content decay
The loss of usefulness or visibility as facts, examples, links or user needs change.
Open resource ↗Contribution margin
Revenue remaining after the variable costs required to produce and fulfill the sale.
Open resource ↗Conversion rate
The share of qualified visits or sessions that complete the defined conversion action.
Open resource ↗Core Web Vitals
Google experience metrics for loading, interaction responsiveness and visual stability.
Open resource ↗Creative fatigue
Declining response as an audience repeatedly encounters the same creative treatment.
Open resource ↗Customer acquisition cost
The acquisition investment divided by the customers attributed under a stated method.
Open resource ↗Customer journey
The connected set of customer goals, interactions and decisions across a relationship.
Open resource ↗Customer lifetime value
A model of expected customer contribution over a defined relationship horizon.
Open resource ↗Data layer
A governed structure that exposes consistent event and business data to analytics tools.
Open resource ↗Deliverability
The ability of an email or message to reach an intended recipient under sender and platform rules.
Open resource ↗First-party data
Information collected directly through a brand’s own customer relationships and properties.
Open resource ↗Frequency cap
A limit on how often an audience can receive an advertisement or communication in a period.
Open resource ↗Generative engine optimization
Content practices that make accurate, attributable answers easier for AI retrieval systems to use.
Open resource ↗Gross merchandise value
The total value of merchandise transacted under a stated inclusion method.
Open resource ↗Guardrail metric
A measure used to ensure an improvement does not create an unacceptable negative effect elsewhere.
Open resource ↗Headless commerce
A storefront architecture that separates the presentation layer from commerce back-end services.
Open resource ↗Identity resolution
The controlled process of relating events or records believed to represent the same person or account.
Open resource ↗Incrementality
The additional outcome caused by an intervention beyond what would otherwise have happened.
Open resource ↗Information architecture
The organization and labeling that helps people find, understand and act on information.
Open resource ↗Internal linking
Links between owned pages that help people and crawlers understand related topics and next steps.
Open resource ↗Inventory turnover
How often inventory is sold and replaced during a defined period.
Open resource ↗Landing page continuity
Consistency between an acquisition message and the page experience that follows it.
Open resource ↗Lifecycle marketing
Relevant communication and experiences organized around stages of a customer relationship.
Open resource ↗Localization
Adapting language, content, offer and experience to the expectations of a specific market.
Open resource ↗Merchandising
The decisions that shape product discovery, presentation, availability and offer relevance.
Open resource ↗Minimum detectable effect
The smallest change an experiment is designed with enough power to identify.
Open resource ↗North-star metric
A primary measure intended to align work around enduring customer value, not a complete scorecard.
Open resource ↗Payback period
The time required for customer contribution to recover acquisition investment.
Open resource ↗Product-market fit
Evidence that a defined market repeatedly chooses and values the product.
Open resource ↗Progressive enhancement
Building a reliable core experience before adding capabilities that depend on newer technology.
Open resource ↗Repeat purchase rate
The share of customers who place another order within the selected measurement window.
Open resource ↗Replenishment
A repeat purchase timed to a product’s expected consumption or replacement cycle.
Open resource ↗Retention rate
The share of a defined customer group that remains active after a stated period.
Open resource ↗Return on ad spend
Attributed revenue divided by advertising spend; useful only with its attribution and margin limits stated.
Open resource ↗Search intent
The underlying task or decision a person is trying to complete with a search.
Open resource ↗Server-side tracking
Event collection sent from a trusted server environment rather than only from the browser.
Open resource ↗Service-level objective
A target level of reliability or performance for a service over a defined period.
Open resource ↗Shopify Functions
Server-side Shopify extensions that customize supported commerce logic.
Open resource ↗Shopify Markets
Shopify capabilities for configuring international selling experiences by market.
Open resource ↗Statistical power
The probability that a study will detect an effect of a stated size when it exists.
Open resource ↗Stockout rate
The frequency with which demand cannot be met because an item is unavailable.
Open resource ↗Structured data
Machine-readable markup that describes page entities and relationships for eligible consumers.
Open resource ↗Technical debt
Future delivery cost created by shortcuts, outdated dependencies or insufficiently maintainable decisions.
Open resource ↗Theme architecture
The structure of templates, sections, snippets, settings and assets that make a storefront maintainable.
Open resource ↗Transcreation
Creative adaptation that preserves intended meaning and effect rather than translating literally.
Open resource ↗Value proposition
A clear explanation of who the offer is for, what useful change it creates and why it is credible.
Open resource ↗Voice of customer
Customer language and evidence collected from research, service, reviews and behavior.
Open resource ↗Web pixel
A controlled mechanism for collecting customer events within supported privacy boundaries.
Open resource ↗Zero-party data
Information a customer intentionally and proactively shares with a brand.
Open resource ↗Working sequence
From unknown to owned.
The depth changes by engagement, but the control points stay consistent.
Frame
Name the decision, behavior, owner, evidence and limits.
Diagnose
Find the constraint and map the dependencies around it.
Deliver
Design, build and release the smallest credible change.
Learn
Check quality and outcomes, then choose the next decision.
FAQ
Questions about the DTC glossary.
Clear scope, practical constraints and direct answers for the decision ahead.
How are glossary definitions selected?
Terms are chosen because they affect a real ecommerce decision across Shopify, conversion, acquisition, lifecycle, analytics, operations, automation, SEO or GEO.
Why do some terms include a “decision it affects” note?
A definition is more useful when it shows what changes in practice. The note connects language to an observable customer, commercial or operating decision.
How does DTCUP decide where to start when agreeing shared DTC language?
We begin with the commercial decision, customer behavior and operating constraint. The first engagement confirms the evidence, dependencies, owners and smallest useful release before a larger build is proposed. The same control is applied when agreeing shared DTC language.
What should our team prepare before the first workshop when agreeing shared DTC language?
Bring the store URL, current priorities, customer questions, analytics access, technology list, delivery constraints, budget range and the people who can approve decisions. Missing evidence becomes an explicit research task, not an assumption. The same control is applied when agreeing shared DTC language.
Can DTCUP work with an existing Shopify theme and app stack when agreeing shared DTC language?
Yes. We review maintainability, performance, licenses, accessibility, data flow and overlapping capabilities before recommending what to keep, repair, replace or extend. The same control is applied when agreeing shared DTC language.
How are scope changes handled when agreeing shared DTC language?
The agreed scope records outcomes, deliverables, dependencies, client inputs, acceptance criteria and exclusions. A material change is estimated and approved in writing before it enters delivery. The same control is applied when agreeing shared DTC language.
Who owns the work after delivery when agreeing shared DTC language?
Ownership, repositories, design files, documentation, access, licenses and third-party terms are itemized in the agreement and handoff. Your team keeps the assets it is entitled to own. The same control is applied when agreeing shared DTC language.
How does quality assurance work when agreeing shared DTC language?
QA is proportional to risk and can cover requirements, content states, responsive layouts, accessibility, performance, analytics, integrations, failure states and deployment checks. Issues are recorded with owners and acceptance criteria. The same control is applied when agreeing shared DTC language.
Does DTCUP guarantee a revenue result when agreeing shared DTC language?
No responsible partner can guarantee customer behavior or market conditions. We commit to a defined method, controlled delivery, visible evidence and measurement that makes the next decision clearer. The same control is applied when agreeing shared DTC language.
Can work be delivered in phases when agreeing shared DTC language?
Yes. Advisory, sprint, project and embedded formats let the team validate important assumptions before committing to later phases. Each phase has its own scope, decision gate and handoff. The same control is applied when agreeing shared DTC language.
How is customer data protected when agreeing shared DTC language?
We use the minimum data needed, prefer aggregate or anonymized evidence, restrict access by role and avoid placing personal customer information in public briefs, screenshots or community discussions. The same control is applied when agreeing shared DTC language.
What happens if analytics are unreliable when agreeing shared DTC language?
We document the limitation and decide whether to repair measurement, use a safer proxy, run targeted research or delay a claim until the evidence is strong enough. The same control is applied when agreeing shared DTC language.
Your next move
Bring the constraint. Leave with a clearer route.
Share the decision, timing and current system. We will respond with the most sensible next step.
