Add‑to‑Cart Rate (ATC)
Share of sessions that add at least one product to cart.
Why it matters: Leading indicator of PDP/PLP effectiveness.
A practical glossary for growth and platform teams. Find plain‑language definitions with why they matter, benchmarks, and how we apply them across SEO, Lifecycle/CRM, E‑commerce, Platform (broadcast/OTT), and Infrastructure & IT (SRE/ITSM/DevOps).
Explore related playbooks in SEO, Lifecycle & CRM, E‑commerce, Platform, and Infrastructure & IT.
We’ll send a one‑page checklist for SEO, Lifecycle, and E‑commerce with steps to start now.
Share of sessions that add at least one product to cart.
Why it matters: Leading indicator of PDP/PLP effectiveness.
Average revenue per order.
Why it matters: Small AOV lifts compound revenue.
Charging customers for services on a schedule (prepaid, postpaid, or hybrid).
Why it matters: Cash flow, compliance, and customer experience.
Rights‑based or geographic restriction that blocks content delivery to certain audiences.
Why it matters: Ensures compliance with licensing and regional regulations.
Group of channels bundled together for pricing and offers.
Why it matters: Enables flexible packaging, promotions, and regional offers.
Preferred URL for duplicate or variant pages.
Why it matters: Consolidates ranking signals and avoids duplication.
Share of carts that do not complete checkout.
Why it matters: Reducing abandonment directly lifts conversion and revenue.
Common Media Application Format.
Why it matters: Low‑latency streaming compatibility.
Ridsys conversion & retention engine.
Why it matters: Automated lifecycle and CRO.
Controls subscriber access to encrypted TV content.
Why it matters: Protects premium content and monetization.
Consent-aware data collection and messaging.
Why it matters: Respects privacy and keeps signals clean.
Percentage of visitors who complete a purchase.
Why it matters: Primary efficiency metric for the store.
Systematic improvements to increase the percentage of visitors who convert.
Why it matters: Lifts revenue by improving funnel efficiency.
Server‑side events for ad platforms.
Why it matters: Improves attribution and optimization quality.
Google’s user experience metrics for loading, interactivity, and visual stability.
Why it matters: Better UX improves ranking potential and conversion.
Benchmarks: Good: LCP < 2.5s, INP < 200ms, CLS < 0.1
Suggesting complementary products during browse or checkout.
Why it matters: Lifts basket size and AOV.
Visual stability metric.
Why it matters: Layout shifts frustrate users.
Benchmarks: Good < 0.1
System that unifies first‑party customer data for activation.
Why it matters: Enables accurate segments, triggers, and measurement.
Tooling and processes to manage customer interactions.
Why it matters: Coordinates sales/support data with lifecycle messaging.
Inbox placement health driven by domain reputation and sending practices.
Why it matters: Poor deliverability kills revenue from email/SMS.
Content protection for video.
Why it matters: Protects OTT monetization.
Assigning work to technicians with the right skills and location.
Why it matters: Reduces time to fix and travel overhead.
Confirming subscription via follow‑up, reducing spam complaints.
Why it matters: Improves list quality and deliverability.
Automated reminders and actions to recover failed or overdue payments.
Why it matters: Improves collections while reducing churn.
Distributed caching layer close to viewers.
Why it matters: Cuts latency and stream rebuffering by serving assets near the edge.
Schedule metadata for TV channels and programs.
Why it matters: Enables channel guides and time‑based navigation.
Rules that map subscribers to content rights and packages.
Why it matters: Guarantees only paying viewers or regions can access premium streams.
Allowance for downtime or failures within an SLO window.
Why it matters: Balances release velocity with reliability by making risk explicit.
Cloud financial operations.
Why it matters: Controls cost without blocking velocity.
Share of issues resolved in the first interaction.
Why it matters: Improves customer satisfaction and reduces costs.
Limit on messages per user over time.
Why it matters: Prevents fatigue and unsubscribes.
Ops driven by Git pull requests and CI/CD.
Why it matters: Auditability and safe changes.
Ridsys experimentation framework.
Why it matters: Systematic marketing experiments.
Central facility where channels are received, processed, and packaged for distribution.
Why it matters: Single control point for ingest, transcoding, and packaging.
Decoupled storefront and backend, typically using APIs for flexibility and performance.
Why it matters: Enables faster UX, custom flows, and channel expansion.
Language/region alternate mapping.
Why it matters: Serves the right locale to users.
Pages included in a search engine’s index and eligible to appear in results.
Why it matters: If priority pages are not indexed, they cannot rank or drive traffic.
Managing infra through code (e.g., Terraform).
Why it matters: Repeatability and speed.
Interactivity delay metric.
Why it matters: Slow inputs reduce engagement.
Benchmarks: Good < 200ms
TV over managed IP networks.
Why it matters: Carrier‑grade distribution.
Information security standard.
Why it matters: Structured security practices.
Processes for delivering and supporting IT services.
Why it matters: Consistency, compliance, and efficiency.
Repository of solutions, SOPs, and playbooks.
Why it matters: Improves FCR and speeds up onboarding.
Loading speed metric.
Why it matters: Slow LCP hurts rankings and UX.
Benchmarks: Good < 2.5s
Revenue a customer is expected to generate over time.
Why it matters: Guides investment in acquisition and retention.
Low‑Latency DASH streaming.
Why it matters: Reduces glass‑to‑glass delay.
Low‑Latency HLS streaming.
Why it matters: Reduces glass‑to‑glass delay.
Statistical model to estimate channel impact.
Why it matters: Budget allocation and incrementality checks.
Average time from ticket open to resolution.
Why it matters: Primary responsiveness KPI for support and field ops.
Software layer that orchestrates content, entitlements, and personalization between headend and apps.
Why it matters: Carries business rules, entitlements, and UI content to every endpoint.
Customer loyalty metric based on likelihood to recommend.
Why it matters: Signals overall service quality over time.
Open standard for traces, metrics, and logs instrumentation.
Why it matters: Unified telemetry enables deep visibility and faster incident response.
Remote firmware or software update delivered over the network to devices.
Why it matters: Keeps device fleets secure and current without on‑site visits.
Internet‑delivered video services.
Why it matters: Modern video distribution.
Page displaying information about a product.
Why it matters: Critical for add‑to‑cart and conversion.
Category or search results page listing multiple products with filters and sorting.
Why it matters: Strong discovery drives add‑to‑cart and revenue.
Matching transactions across systems (payments, invoices, bank).
Why it matters: Catches errors and improves financial accuracy.
Total revenue divided by visitors.
Why it matters: Captures both conversion and AOV effects.
Groups customers by Recency, Frequency, and Monetary value.
Why it matters: Targets offers by behavior to lift LTV.
Reliable Internet Stream Transport.
Why it matters: Resilient video contribution.
Process to identify underlying cause of an incident.
Why it matters: Prevents repeats and feeds continuous improvement.
Step‑by‑step guide to diagnose and resolve common issues.
Why it matters: Reduces MTTR and makes operations repeatable.
Machine‑readable markup that helps search engines understand content.
Why it matters: Enables rich results and improves relevance.
Improving visibility and clicks from search by aligning technical, content, and UX factors.
Why it matters: Drives qualified, intent‑rich traffic.
Stitching ads into streams server‑side.
Why it matters: Better QoE and ad blocking resistance.
Event tracking sent from server for accuracy.
Why it matters: Improves attribution and optimization.
Running Google Tag Manager on the server.
Why it matters: Cleaner signals and less client bloat.
Contracted reliability and response guarantees.
Why it matters: Sets expectations for uptime and support.
Measured metric of service performance.
Why it matters: Evidence for SLOs and reliability reviews.
Target reliability for a service.
Why it matters: Aligns engineering and business on reliability.
Customer‑premise receiver that authenticates and enforces access to TV services.
Why it matters: Primary enforcement point for CAS policies and device security.
Engineering discipline to keep systems reliable.
Why it matters: Balances velocity with reliability.
Security compliance framework.
Why it matters: Assurance for customers and partners.
Secure Reliable Transport.
Why it matters: Low‑latency contribution transport.
Binding an access card or identity to a specific device.
Why it matters: Reduces credential sharing and piracy by tying rights to hardware.
Manages subscribers, billing, and entitlements.
Why it matters: Coordinates operations across products and services.
A tracked unit of work for support or field operations.
Why it matters: Provides accountability and SLA tracking.
Encouraging a higher‑value version or add‑on at purchase time.
Why it matters: Increases AOV without additional traffic.
Creator or community content used in marketing.
Why it matters: Adds credibility and creative diversity.
Formal job instruction for a technician or team.
Why it matters: Standardizes tasks, parts, and checklists.