AAA / RADIUS
Authentication, Authorization, and Accounting services (commonly via RADIUS) for broadband subscribers.
Why it matters: Controls network access policies and enforces provisioning rules automatically.
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.
Authentication, Authorization, and Accounting services (commonly via RADIUS) for broadband subscribers.
Why it matters: Controls network access policies and enforces provisioning rules automatically.
Targeted marketing approach focused on specific high-value accounts.
Why it matters: Improves conversion for enterprise sales cycles.
Streaming technique that switches between quality levels dynamically based on network conditions.
Why it matters: Maintains playback quality without buffering when bandwidth fluctuates.
Share of sessions that add at least one product to cart.
Why it matters: Leading indicator of PDP/PLP effectiveness.
Yearly subscription revenue from active customers.
Why it matters: Key SaaS growth metric for scaling businesses.
Process of assigning credit to marketing touchpoints that lead to conversions.
Why it matters: Enables accurate budget allocation and optimization decisions.
Comprehensive assessment of current state across technical, content, and performance dimensions.
Why it matters: Identifies opportunities and establishes baseline metrics.
Next-generation video codec with high compression efficiency.
Why it matters: Delivers high-quality streams at lower bitrates, reducing bandwidth costs.
Average revenue per order.
Why it matters: Small AOV lifts compound revenue.
Prioritized list of experiments, improvements, or work items to be executed.
Why it matters: Maintains focus and ensures high-impact work gets done first.
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.
Companies that sell products or services to other businesses.
Why it matters: Focuses on longer sales cycles, ABM, and account expansion.
Preferred URL for duplicate or variant pages.
Why it matters: Consolidates ranking signals and avoids duplication.
When shoppers add items to cart but leave without completing checkout.
Why it matters: Reducing abandonment directly lifts conversion and revenue.
Share of carts that do not complete checkout.
Why it matters: Reducing abandonment directly lifts conversion and revenue.
Executive responsible for marketing strategy, growth, and brand performance.
Why it matters: Primary stakeholder for GrowthLab™, Commerce Engine™, and Growth Scan™ programs.
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.
Distributed network of cache servers that deliver video and assets close to viewers.
Why it matters: Improves streaming performance, reduces latency, and absorbs peak load.
Percentage of visitors who complete a purchase.
Why it matters: Primary efficiency metric for the store.
Percentage of visitors who complete a desired action (purchase, signup, etc.).
Why it matters: Primary efficiency metric for funnels and campaigns.
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
Total cost to acquire a new customer.
Why it matters: Guides marketing spend efficiency and profitability.
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.
Brands that sell directly to consumers without intermediaries.
Why it matters: Enables control over customer experience and data.
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.
Large organizations with multi-region operations, complex governance, and established teams.
Why it matters: Requires alignment, standardization, and scalable experimentation frameworks.
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.
Systematic testing of hypotheses to validate improvements and learn what works.
Why it matters: Reduces risk and compounds learnings over time.
Policy that throttles or caps usage once subscribers hit defined thresholds.
Why it matters: Prevents abuse and keeps network performance predictable.
Cloud financial operations.
Why it matters: Controls cost without blocking velocity.
Amazon’s streaming platform (Fire TV Stick / Cube).
Why it matters: Common device footprint for OTT apps in emerging markets.
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.
Framework for decision-making, standards, and oversight across teams and regions.
Why it matters: Ensures consistency, compliance, and scalable operations.
Fast diagnostic audit covering SEO, speed, UX, content, security, and commerce readiness.
Why it matters: Gives teams a quantified starting point and prioritised opportunities before deeper programs.
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.
High Efficiency Video Coding standard for HD/4K video.
Why it matters: Sustains quality at lower bitrates for broadcast and OTT streams.
Language/region alternate mapping.
Why it matters: Serves the right locale to users.
Apple’s HTTP-based streaming protocol widely supported across devices.
Why it matters: Baseline delivery format for OTT apps and smart TVs.
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
Company providing internet access and related services.
Why it matters: Key partners for IPTV and broadband delivery.
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 between an alert triggering and the on-call team acknowledging it.
Why it matters: Reflects responsiveness of incident response before mitigation begins.
Average time from ticket open to resolution.
Why it matters: Primary responsiveness KPI for support and field ops.
Growing businesses in the $10M–$100M ARR range, scaling operations and teams.
Why it matters: Needs structured experimentation, lifecycle, and media discipline.
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.
Cable or telecommunications company operating multiple systems.
Why it matters: Primary customers for broadcast/IPTV infrastructure.
Customer loyalty metric based on likelihood to recommend.
Why it matters: Signals overall service quality over time.
Centralized facility for monitoring and managing network infrastructure.
Why it matters: Ensures 24×7 visibility and rapid incident response.
Platforms that aggregate and sell travel services (hotels, flights, etc.).
Why it matters: Hospitality businesses reduce dependency by building direct booking channels.
Open standard for traces, metrics, and logs instrumentation.
Why it matters: Unified telemetry enables deep visibility and faster incident response.
Operational and business support systems that manage provisioning, inventory, billing, and customer care.
Why it matters: Critical for ISP workflows that span network and commercial operations.
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.
Documented process, framework, or guide for executing specific strategies or tactics.
Why it matters: Enables repeatability and knowledge transfer across teams.
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.
Growth strategy where the product itself drives acquisition and expansion.
Why it matters: Reduces CAC and improves user activation.
Matching transactions across systems (payments, invoices, bank).
Why it matters: Catches errors and improves financial accuracy.
Alignment of sales, marketing, and customer success operations.
Why it matters: Improves revenue predictability and efficiency.
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.
Real-Time Messaging Protocol used for contribution and live streaming ingest.
Why it matters: Common legacy contribution format still used for many live workflows.
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.
Group of customers or businesses with shared characteristics for targeted strategies.
Why it matters: Enables personalized messaging and optimized experiences.
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.
Small to medium-sized businesses, typically under $10M ARR or early-stage scaling.
Why it matters: Requires focused, foundational digital growth strategies.
Security compliance framework.
Why it matters: Assurance for customers and partners.
Cloud-based software delivery model with subscription pricing.
Why it matters: Requires product-led growth, trial optimization, and retention focus.
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.
Automated collection and transmission of data from systems and applications.
Why it matters: Enables real-time monitoring, alerting, and performance optimization.
Device management layer for STBs and smart devices covering remote monitoring, firmware/APK updates, configuration, and diagnostics.
Why it matters: Keeps fleets updated with zero-touch maintenance and lifecycle tracking.
A tracked unit of work for support or field operations.
Why it matters: Provides accountability and SLA tracking.
Smart TV operating system used by Samsung TVs.
Why it matters: Important app ecosystem for IPTV/OTT distribution.
Packet-based transport protocols for low-latency video contribution and multicast delivery.
Why it matters: Enable real-time streams in broadcast and ISP networks.
Encouraging a higher‑value version or add‑on at purchase time.
Why it matters: Increases AOV without additional traffic.
Overall experience users have when interacting with a product or service.
Why it matters: Better UX improves conversion, retention, and customer satisfaction.
Creator or community content used in marketing.
Why it matters: Adds credibility and creative diversity.
LG’s smart TV operating system.
Why it matters: Requires dedicated app builds for living-room experiences.
Google’s DRM system for securing premium content on Android/Chrome ecosystems.
Why it matters: Required by many device partners and OTT distribution agreements.
Formal job instruction for a technician or team.
Why it matters: Standardizes tasks, parts, and checklists.