{"id":6842,"date":"2026-03-23T14:38:12","date_gmt":"2026-03-23T14:38:12","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/data-stream\/"},"modified":"2026-03-23T14:38:12","modified_gmt":"2026-03-23T14:38:12","slug":"data-stream","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/data-stream\/","title":{"rendered":"Data Stream: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Analytics"},"content":{"rendered":"\n

A Data Stream<\/strong> is the continuous flow of marketing, product, and customer signals\u2014events, attributes, and outcomes\u2014moving from where they happen (a website, app, POS system, call center, ad platform) into systems that turn them into insight and action. In Conversion & Measurement<\/strong>, a Data Stream is the backbone of trustworthy attribution, funnel analysis, experimentation, and optimization because it determines what you can measure, how fast you can respond, and how confident you are in results. In Analytics<\/strong>, it\u2019s the raw material that powers dashboards, models, and decisions\u2014so the quality of the stream often matters more than the sophistication of the reports.<\/p>\n\n\n\n

Modern Conversion & Measurement<\/strong> strategies increasingly depend on first-party data, privacy-aware collection, and near real-time feedback loops. A well-designed Data Stream<\/strong> makes those requirements achievable by standardizing how data is captured, validated, enriched, and activated across channels.<\/p>\n\n\n\n

What Is Data Stream?<\/h2>\n\n\n\n

A Data Stream<\/strong> is a structured, ongoing sequence of data records generated by user behavior, system activity, or business operations and sent to one or more destinations for storage, analysis, and activation. In a marketing context, those records are often event-based (page views, sign-ups, purchases, lead submissions, video plays) plus supporting context (campaign parameters, device details, consent state, user identifiers).<\/p>\n\n\n\n

The core concept is continuity: instead of waiting for periodic exports, a Data Stream delivers incremental updates as they happen (or close to it). That makes it ideal for Conversion & Measurement<\/strong>, where teams need to see what\u2019s working, detect tracking issues quickly, and connect touchpoints to outcomes.<\/p>\n\n\n\n

From a business perspective, a Data Stream is how you translate customer behavior into measurable performance. It\u2019s how your organization answers questions like: Which campaigns drive qualified leads? Where do users drop off? What is the true cost per acquisition? Inside Analytics<\/strong>, it\u2019s the input that fuels metrics, segmentation, and modeling\u2014so accuracy, consistency, and governance are essential.<\/p>\n\n\n\n

Why Data Stream Matters in Conversion & Measurement<\/h2>\n\n\n\n

A Data Stream<\/strong> matters because measurement is only as strong as the data foundation. In Conversion & Measurement<\/strong>, teams frequently struggle with fragmented tracking, inconsistent event naming, duplicate conversions, and mismatched definitions across departments. A well-governed Data Stream addresses those root causes.<\/p>\n\n\n\n

Strategically, a Data Stream creates competitive advantage by enabling faster learning cycles. When you can observe conversion behavior quickly and reliably, you can iterate creatives, landing pages, audiences, and budgets with less guesswork. In Analytics<\/strong>, it improves comparability over time and across platforms, making trend analysis and experimentation more defensible.<\/p>\n\n\n\n

Business value typically shows up as:<\/p>\n\n\n\n

    \n
  • More reliable conversion reporting and attribution (even when the ecosystem changes)<\/li>\n
  • Faster detection of drops in lead flow or purchase tracking<\/li>\n
  • Better audience building and personalization driven by verified events<\/li>\n
  • Reduced wasted spend from mis-optimized campaigns based on bad data<\/li>\n<\/ul>\n\n\n\n

    How Data Stream Works<\/h2>\n\n\n\n

    A Data Stream<\/strong> can be understood as a practical workflow that connects actions to outcomes in Conversion & Measurement<\/strong> and Analytics<\/strong>:<\/p>\n\n\n\n

      \n
    1. \n

      Input (trigger and capture)<\/strong>\n A user action or system event occurs\u2014viewing a product, submitting a form, completing checkout, calling a sales line, or renewing a subscription. A tracking method captures it (client-side, server-side, or both) along with context such as timestamp, page\/screen, referrer, and campaign information.<\/p>\n<\/li>\n

    2. \n

      Processing (validation and enrichment)<\/strong>\n The event is validated against a measurement plan (required fields, correct formats, expected values). It may be enriched with additional context: normalized campaign naming, product categories, geo, device grouping, customer status, or consent flags. Deduplication and identity resolution may occur here to avoid double-counting conversions.<\/p>\n<\/li>\n

    3. \n

      Execution (routing and activation)<\/strong>\n The processed event is routed to destinations: data warehouses, reporting tools, marketing automation, or audiences for ad platforms. In Conversion & Measurement<\/strong>, this stage determines whether conversions are usable for optimization and whether downstream systems agree on \u201cwhat happened.\u201d<\/p>\n<\/li>\n

    4. \n

      Output (insight and action)<\/strong>\n Teams use the resulting datasets for Analytics<\/strong> reporting, funnel analysis, cohort tracking, attribution, experimentation readouts, and budget decisions. Alerts and monitoring may trigger actions when anomalies occur (conversion rate drops, event volume spikes, latency increases).<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      In practice, the \u201chow\u201d is less about a single tool and more about designing the stream so it remains consistent as your site, apps, and campaigns evolve.<\/p>\n\n\n\n

      Key Components of Data Stream<\/h2>\n\n\n\n

      A robust Data Stream<\/strong> for Conversion & Measurement<\/strong> and Analytics<\/strong> usually includes:<\/p>\n\n\n\n

        \n
      • Event taxonomy and measurement plan<\/strong>: clear definitions of events (e.g., lead_submit<\/code>, purchase<\/code>), parameters, and what counts as a conversion.<\/li>\n
      • Collection mechanisms<\/strong>: client-side tags, SDKs, server-side tracking, and offline ingestion for CRM\/POS events.<\/li>\n
      • Schema and data contracts<\/strong>: agreed field names, types, required parameters, and versioning to prevent breaking changes.<\/li>\n
      • Identity and matching strategy<\/strong>: how you connect sessions, devices, and customers (while respecting consent and policy).<\/li>\n
      • Consent and privacy controls<\/strong>: consent states, retention rules, and minimization of sensitive fields.<\/li>\n
      • Data quality monitoring<\/strong>: checks for completeness, duplication, latency, and unexpected shifts.<\/li>\n
      • Governance and ownership<\/strong>: defined responsibilities across marketing, analytics, engineering, and data teams; change management and documentation.<\/li>\n<\/ul>\n\n\n\n

        Types of Data Stream<\/h2>\n\n\n\n

        \u201cData Stream\u201d doesn\u2019t have a single universal taxonomy, but several distinctions matter in Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

        1) Real-time vs. batch<\/h3>\n\n\n\n
          \n
        • Real-time (or near real-time)<\/strong> streams support rapid optimization, anomaly detection, and responsive Analytics<\/strong>.<\/li>\n
        • Batch<\/strong> streams (hourly\/daily loads) are common for finance-grade reconciliation and some offline sources.<\/li>\n<\/ul>\n\n\n\n

          2) Client-side vs. server-side<\/h3>\n\n\n\n
            \n
          • Client-side<\/strong> streams originate in the browser or app and are easier to deploy but can be affected by blockers, connectivity, and device limitations.<\/li>\n
          • Server-side<\/strong> streams originate from your servers, tend to be more controllable, and can improve resilience\u2014especially important for conversions and deduplication.<\/li>\n<\/ul>\n\n\n\n

            3) First-party digital vs. offline\/business system<\/h3>\n\n\n\n
              \n
            • Digital behavior<\/strong> streams: website\/app events and engagement.<\/li>\n
            • Offline\/business<\/strong> streams: CRM status changes, call tracking outcomes, in-store purchases, subscription renewals\u2014critical for full-funnel Conversion & Measurement<\/strong>.<\/li>\n<\/ul>\n\n\n\n

              4) Raw vs. modeled\/aggregated<\/h3>\n\n\n\n
                \n
              • Raw event<\/strong> streams support flexible analysis and debugging.<\/li>\n
              • Aggregated<\/strong> streams support lightweight reporting but can hide issues and reduce diagnostic power.<\/li>\n<\/ul>\n\n\n\n

                Real-World Examples of Data Stream<\/h2>\n\n\n\n

                Example 1: Lead generation with CRM feedback loops<\/h3>\n\n\n\n

                A B2B company streams website form submissions with campaign metadata into a warehouse and Analytics<\/strong> reporting. Separately, CRM updates stream back key lifecycle changes (qualified lead, opportunity created, closed-won). In Conversion & Measurement<\/strong>, this Data Stream enables optimization toward qualified outcomes rather than just form fills, improving lead quality and reducing cost per qualified lead.<\/p>\n\n\n\n

                Example 2: Ecommerce conversion deduplication across web and backend<\/h3>\n\n\n\n

                An online retailer captures purchase<\/code> events in the browser but also streams backend order confirmations. By deduplicating on order ID and enforcing a strict schema, the Data Stream prevents double-counting and supports accurate revenue in Analytics<\/strong>. In Conversion & Measurement<\/strong>, this makes ROAS calculations and channel comparisons more trustworthy.<\/p>\n\n\n\n

                Example 3: App onboarding funnels and experimentation<\/h3>\n\n\n\n

                A mobile app streams onboarding events (install<\/code>, signup_start<\/code>, signup_complete<\/code>, trial_start<\/code>) with experiment variant identifiers. The Data Stream powers near real-time funnel Analytics<\/strong> to detect friction and compare variant performance. In Conversion & Measurement<\/strong>, the team can iterate onboarding flows faster and validate improvements with cleaner event definitions.<\/p>\n\n\n\n

                Benefits of Using Data Stream<\/h2>\n\n\n\n

                A well-managed Data Stream<\/strong> delivers tangible outcomes for Conversion & Measurement<\/strong> and Analytics<\/strong>:<\/p>\n\n\n\n

                  \n
                • Performance improvements<\/strong>: faster optimization because conversion signals arrive consistently and quickly.<\/li>\n
                • Cost savings<\/strong>: reduced wasted spend caused by broken tracking, misattribution, or inflated conversion counts.<\/li>\n
                • Operational efficiency<\/strong>: fewer one-off data fixes, less time reconciling dashboards, and smoother cross-team collaboration.<\/li>\n
                • Better customer experience<\/strong>: more relevant personalization and fewer \u201cmeasurement-driven\u201d mistakes (like retargeting users who already converted).<\/li>\n
                • Stronger experimentation<\/strong>: cleaner inputs lead to clearer test readouts and more credible decisions.<\/li>\n<\/ul>\n\n\n\n

                  Challenges of Data Stream<\/h2>\n\n\n\n

                  A Data Stream<\/strong> is powerful, but it introduces real constraints and risks:<\/p>\n\n\n\n

                    \n
                  • Event ambiguity and inconsistent definitions<\/strong>: \u201cconversion\u201d can mean different things across teams unless governed tightly.<\/li>\n
                  • Data quality drift<\/strong>: site\/app changes can silently break events or change parameter meanings, undermining Analytics<\/strong> trends.<\/li>\n
                  • Identity complexity<\/strong>: matching users across devices and systems is difficult, especially with consent requirements and limited identifiers.<\/li>\n
                  • Latency and reliability issues<\/strong>: delayed or dropped events can distort Conversion & Measurement<\/strong> reporting and optimization.<\/li>\n
                  • Overcollection<\/strong>: capturing too much data increases cost, complicates governance, and can introduce privacy risk.<\/li>\n
                  • Organizational friction<\/strong>: marketing wants speed, engineering wants stability, and data teams want consistency\u2014alignment is required.<\/li>\n<\/ul>\n\n\n\n

                    Best Practices for Data Stream<\/h2>\n\n\n\n

                    To build a durable Data Stream<\/strong> that supports Conversion & Measurement<\/strong> and Analytics<\/strong>, focus on fundamentals:<\/p>\n\n\n\n

                      \n
                    1. \n

                      Start with a measurement plan, not a tag list<\/strong>\n Define conversions, micro-conversions, and required parameters. Include examples and edge cases (refunds, duplicates, partial payments).<\/p>\n<\/li>\n

                    2. \n

                      Use consistent naming and versioning<\/strong>\n Establish event naming conventions, parameter standards, and a versioning approach for changes. Treat schema changes like product changes.<\/p>\n<\/li>\n

                    3. \n

                      Implement validation and monitoring<\/strong>\n Validate required fields and acceptable values. Monitor event volume, conversion rate shifts, and missing parameters. Add alerts for anomalies.<\/p>\n<\/li>\n

                    4. \n

                      Design for deduplication and reconciliation<\/strong>\n Use stable IDs (order ID, lead ID) where possible. Define source-of-truth rules between client and server events.<\/p>\n<\/li>\n

                    5. \n

                      Minimize and protect sensitive data<\/strong>\n Collect only what\u2019s needed for Conversion & Measurement<\/strong>. Avoid sending sensitive fields; apply consent logic consistently.<\/p>\n<\/li>\n

                    6. \n

                      Document ownership and change management<\/strong>\n Assign owners for key events, dashboards, and downstream dependencies. Require review for changes that affect conversion definitions.<\/p>\n<\/li>\n

                    7. \n

                      Test end-to-end<\/strong>\n Validate that an event not only fires, but also appears correctly in Analytics<\/strong>, reporting, and activation workflows.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                      Tools Used for Data Stream<\/h2>\n\n\n\n

                      A Data Stream<\/strong> typically spans multiple tool categories. The goal is interoperability and governed flow, not dependency on any single vendor.<\/p>\n\n\n\n

                        \n
                      • Analytics tools<\/strong>: receive and process event streams for reporting, funnels, cohorts, and audience definitions.<\/li>\n
                      • Tag management and SDK tooling<\/strong>: deploy and manage event collection rules across web and apps with controlled releases.<\/li>\n
                      • Server-side tracking and API integrations<\/strong>: send events from backend systems and reduce reliance on browser-only collection.<\/li>\n
                      • Data warehouses and lakes<\/strong>: store raw and enriched stream data for durable analysis and cross-source joins.<\/li>\n
                      • ETL\/ELT and orchestration<\/strong>: transform, validate, and route streaming or batch data into consistent datasets.<\/li>\n
                      • CRM systems and marketing automation<\/strong>: provide lifecycle events (qualification, revenue) and consume events for nurturing.<\/li>\n
                      • Reporting dashboards and BI<\/strong>: unify Analytics<\/strong> outputs and business metrics for stakeholders.<\/li>\n
                      • Data quality and observability<\/strong>: monitor freshness, completeness, schema drift, and anomalies\u2014critical for Conversion & Measurement<\/strong> trust.<\/li>\n<\/ul>\n\n\n\n

                        Metrics Related to Data Stream<\/h2>\n\n\n\n

                        Because a Data Stream<\/strong> is infrastructure for Analytics<\/strong>, you should measure both marketing outcomes and stream health.<\/p>\n\n\n\n

                        Stream health metrics<\/h3>\n\n\n\n
                          \n
                        • Event volume and completeness<\/strong>: expected vs. actual counts; % of events missing required parameters.<\/li>\n
                        • Latency (freshness)<\/strong>: time from event occurrence to availability in reporting\/warehouse.<\/li>\n
                        • Duplicate rate<\/strong>: share of conversions\/events that are repeated and need deduplication.<\/li>\n
                        • Schema error rate<\/strong>: events rejected or malformed due to invalid formats.<\/li>\n
                        • Match rate<\/strong>: ability to connect events to users, sessions, or customers (within policy).<\/li>\n
                        • Consent coverage<\/strong>: percentage of traffic\/events with known consent state and compliant handling.<\/li>\n<\/ul>\n\n\n\n

                          Conversion & Measurement outcome metrics<\/h3>\n\n\n\n
                            \n
                          • Conversion rate and funnel step rate<\/strong>: from visit to lead, lead to opportunity, cart to purchase.<\/li>\n
                          • Cost per acquisition \/ cost per qualified lead<\/strong>: tied to downstream quality events when possible.<\/li>\n
                          • Revenue per visitor \/ average order value<\/strong>: validated against backend outcomes.<\/li>\n
                          • Attribution stability<\/strong>: consistency of channel performance rankings over time (useful as a sanity check).<\/li>\n
                          • Experiment lift and confidence<\/strong>: clearer results when event definitions and data quality are stable.<\/li>\n<\/ul>\n\n\n\n

                            Future Trends of Data Stream<\/h2>\n\n\n\n

                            Several forces are shaping how Data Stream<\/strong> design evolves in Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

                              \n
                            • AI-assisted instrumentation and QA<\/strong>: automated detection of missing events, schema drift, and unusual conversion patterns in Analytics<\/strong>.<\/li>\n
                            • More server-side and hybrid collection<\/strong>: to improve resilience, reduce loss, and support consistent deduplication.<\/li>\n
                            • Privacy-by-design measurement<\/strong>: stronger minimization, consent-aware routing, and governance embedded into pipelines.<\/li>\n
                            • Incrementality and causal measurement<\/strong>: as last-click and simplistic attribution become less reliable, Data Stream designs will prioritize experiment-ready datasets.<\/li>\n
                            • Real-time personalization<\/strong>: streaming signals increasingly power on-site\/app experiences, not just reporting, tightening the loop between measurement and action.<\/li>\n<\/ul>\n\n\n\n

                              Data Stream vs Related Terms<\/h2>\n\n\n\n

                              Data Stream vs data pipeline<\/h3>\n\n\n\n

                              A Data Stream<\/strong> is the continuous flow of event records; a data pipeline<\/strong> is the broader system that moves and transforms data from sources to destinations (often including batch jobs, transformations, and warehousing). In Analytics<\/strong>, the stream is an input; the pipeline is the end-to-end transport and processing.<\/p>\n\n\n\n

                              Data Stream vs event tracking<\/h3>\n\n\n\n

                              Event tracking<\/strong> is the practice of defining and capturing user\/system events. A Data Stream<\/strong> includes event tracking but also covers routing, validation, enrichment, governance, and operational monitoring required for dependable Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                              Data Stream vs ETL\/ELT<\/h3>\n\n\n\n

                              ETL\/ELT refers to transformation methods (extract-transform-load or extract-load-transform). A Data Stream<\/strong> may feed ETL\/ELT processes, but the stream concept focuses on continuous event flow and timeliness, whereas ETL\/ELT focuses on transformation and loading patterns.<\/p>\n\n\n\n

                              Who Should Learn Data Stream<\/h2>\n\n\n\n

                              Understanding Data Stream<\/strong> fundamentals helps multiple roles collaborate effectively in Conversion & Measurement<\/strong> and Analytics<\/strong>:<\/p>\n\n\n\n

                                \n
                              • Marketers and growth teams<\/strong>: to define meaningful conversions, interpret results correctly, and avoid optimizing to flawed signals.<\/li>\n
                              • Analysts<\/strong>: to diagnose data anomalies, build reliable datasets, and explain confidence levels in reporting.<\/li>\n
                              • Agencies<\/strong>: to standardize measurement across clients, reduce implementation churn, and prove impact with defensible data.<\/li>\n
                              • Business owners and founders<\/strong>: to evaluate reporting quality, align teams on outcomes, and invest in scalable measurement.<\/li>\n
                              • Developers and engineers<\/strong>: to implement tracking with clear contracts, reduce rework, and support privacy-safe data collection.<\/li>\n<\/ul>\n\n\n\n

                                Summary of Data Stream<\/h2>\n\n\n\n

                                A Data Stream<\/strong> is the continuous flow of structured events and context from customer interactions and business systems into destinations where they can be used. It matters because Conversion & Measurement<\/strong> depends on consistent, validated conversion signals and because Analytics<\/strong> depends on reliable inputs more than flashy dashboards. When designed with clear definitions, governance, monitoring, and privacy-aware practices, a Data Stream becomes a durable measurement foundation that supports optimization, experimentation, and smarter business decisions.<\/p>\n\n\n\n

                                Frequently Asked Questions (FAQ)<\/h2>\n\n\n\n

                                1) What is a Data Stream in marketing measurement?<\/h3>\n\n\n\n

                                A Data Stream<\/strong> is the ongoing flow of event data (like page views, sign-ups, purchases, and CRM updates) from where it occurs into systems used for Conversion & Measurement<\/strong> and Analytics<\/strong>, enabling timely reporting and activation.<\/p>\n\n\n\n

                                2) How do I know if my Data Stream is \u201chealthy\u201d?<\/h3>\n\n\n\n

                                Track freshness (latency), completeness (missing parameters), duplicate conversion rate, schema errors, and sudden shifts in event volume. If those are stable, your Conversion & Measurement<\/strong> reporting is far more likely to be trustworthy.<\/p>\n\n\n\n

                                3) What\u2019s the difference between real-time and batch data for Analytics?<\/h3>\n\n\n\n

                                Real-time streams support rapid decisions and debugging, while batch loads are often used for reconciliation and offline sources. Many teams use a hybrid approach so Analytics<\/strong> can be both fast and auditable.<\/p>\n\n\n\n

                                4) Do I need server-side tracking for a good Data Stream?<\/h3>\n\n\n\n

                                Not always, but server-side (or hybrid) approaches often improve reliability, deduplication, and control\u2014especially for high-stakes conversions. The best choice depends on your risk tolerance, technical resources, and Conversion & Measurement<\/strong> requirements.<\/p>\n\n\n\n

                                5) How should I choose which events count as conversions?<\/h3>\n\n\n\n

                                Start from business outcomes (revenue, qualified pipeline, retained users) and work backward to measurable events. Define primary conversions and supporting micro-conversions, then document rules so Analytics<\/strong> and stakeholders interpret them consistently.<\/p>\n\n\n\n

                                6) What common mistakes break Conversion & Measurement reporting?<\/h3>\n\n\n\n

                                The most common issues are inconsistent event naming, missing campaign parameters, double-counted purchases\/leads, unmonitored schema changes, and unclear ownership. All of these can be mitigated with a governed Data Stream<\/strong> and routine quality checks.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                A **Data Stream** is the continuous flow of marketing, product, and customer signals\u2014events, attributes, and outcomes\u2014moving from where they happen (a website, app, POS system, call center, ad platform) into systems that turn them into insight and action. In **Conversion & Measurement**, a Data Stream is the backbone of trustworthy attribution, funnel analysis, experimentation, and optimization because it determines what you can measure, how fast you can respond, and how confident you are in results. In **Analytics**, it\u2019s the raw material that powers dashboards, models, and decisions\u2014so the quality of the stream often matters more than the sophistication of the reports.<\/p>\n","protected":false},"author":10235,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1887],"tags":[],"class_list":["post-6842","post","type-post","status-publish","format-standard","hentry","category-analytics"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6842","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/users\/10235"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/comments?post=6842"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6842\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=6842"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=6842"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=6842"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}