{"id":6918,"date":"2026-03-23T17:34:38","date_gmt":"2026-03-23T17:34:38","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/purchase-revenue\/"},"modified":"2026-03-23T17:34:38","modified_gmt":"2026-03-23T17:34:38","slug":"purchase-revenue","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/purchase-revenue\/","title":{"rendered":"Purchase Revenue: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Analytics"},"content":{"rendered":"\n

Purchase Revenue is the amount of money your business generates from completed purchases that you can attribute to marketing, product experiences, and sales activities through Conversion & Measurement<\/strong>. In practical Analytics<\/strong>, it\u2019s the revenue value tied to a conversion event (a purchase) and used to evaluate what is truly working\u2014not just what is getting clicks.<\/p>\n\n\n\n

Modern Conversion & Measurement<\/strong> strategies increasingly prioritize outcomes over activity. Tracking Purchase Revenue helps you move beyond surface metrics and make decisions based on profitability, customer value, and sustainable growth. When implemented well, Purchase Revenue becomes the \u201csource of truth\u201d metric that aligns marketing teams, finance, product, and leadership.<\/p>\n\n\n\n

What Is Purchase Revenue?<\/h2>\n\n\n\n

Purchase Revenue is the monetary value recorded when a customer completes a transaction. In digital contexts, it typically represents the revenue associated with an online purchase event, such as an eCommerce checkout, a subscription payment, or an in-app transaction.<\/p>\n\n\n\n

At its core, Purchase Revenue answers a simple business question: How much money did we make from purchases\u2014and where did it come from?<\/strong> That \u201cwhere\u201d is where Conversion & Measurement<\/strong> and Analytics<\/strong> become essential, because the same total revenue can look very different once you break it down by channel, campaign, audience, landing page, device, or geography.<\/p>\n\n\n\n

In Conversion & Measurement<\/strong>, Purchase Revenue is a primary conversion outcome used to:\n– evaluate channel performance (paid, organic, email, affiliates, referrals)\n– compare campaigns based on financial impact\n– optimize funnels to increase completed purchases and order value<\/p>\n\n\n\n

Inside Analytics<\/strong>, Purchase Revenue functions as a key metric that can be aggregated, segmented, modeled, and used to compute other performance indicators (like ROAS, CAC payback, or profit contribution).<\/p>\n\n\n\n

Why Purchase Revenue Matters in Conversion & Measurement<\/h2>\n\n\n\n

Purchase Revenue matters because it connects your marketing actions to a business outcome that leadership cares about: money collected from customers. Strong Conversion & Measurement<\/strong> is not just about counting conversions; it\u2019s about understanding which conversions are valuable, repeatable, and efficient to acquire.<\/p>\n\n\n\n

Key reasons Purchase Revenue is strategically important:<\/p>\n\n\n\n

    \n
  • Budget allocation becomes evidence-based.<\/strong> Instead of optimizing for clicks or leads, teams optimize for revenue contribution and efficiency.<\/li>\n
  • It improves campaign decision quality.<\/strong> Two campaigns can have the same number of purchases, but very different Purchase Revenue due to differences in average order value, discounts, or product mix.<\/li>\n
  • It sharpens competitive advantage.<\/strong> Organizations that measure revenue accurately can shift spend faster, identify profitable segments, and scale what works before competitors do.<\/li>\n
  • It aligns teams.<\/strong> Purchase Revenue is a shared language between marketing, finance, and product\u2014especially when your Analytics<\/strong> definitions are consistent.<\/li>\n<\/ul>\n\n\n\n

    In short, Purchase Revenue is one of the clearest bridges between tactical marketing and strategic business performance within Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

    How Purchase Revenue Works<\/h2>\n\n\n\n

    Purchase Revenue is conceptual, but it follows a practical workflow in most organizations.<\/p>\n\n\n\n

      \n
    1. \n

      Input \/ trigger (the purchase happens)<\/strong>\n A customer completes a transaction. The purchase event is recorded with a revenue value (often the order total) along with details like currency, items, quantity, taxes, shipping, and discounts.<\/p>\n<\/li>\n

    2. \n

      Processing (data collection and attribution)<\/strong>\n Your tracking setup sends purchase details to your Analytics<\/strong> system. Attribution logic then connects that revenue to traffic sources, campaigns, or touchpoints. In Conversion & Measurement<\/strong>, this is where measurement design matters: what you count as revenue, when you count it, and how you handle refunds or cancellations.<\/p>\n<\/li>\n

    3. \n

      Application (analysis and optimization)<\/strong>\n Teams analyze Purchase Revenue by channel, campaign, landing page, audience, and funnel steps. They use it to optimize bids, creative, offers, user experience, and lifecycle messaging.<\/p>\n<\/li>\n

    4. \n

      Output \/ outcome (business decisions)<\/strong>\n Purchase Revenue informs reporting, forecasting, and budget decisions. It also supports experimentation by letting teams compare variants based on financial outcomes rather than proxy metrics.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      This workflow only works reliably when your event design, identity handling, and reporting logic are consistent across your Conversion & Measurement<\/strong> stack.<\/p>\n\n\n\n

      Key Components of Purchase Revenue<\/h2>\n\n\n\n

      Purchase Revenue is not \u201cjust a number.\u201d It\u2019s the output of multiple systems and responsibilities working together.<\/p>\n\n\n\n

      Data inputs and definitions<\/h3>\n\n\n\n
        \n
      • Revenue definition:<\/strong> gross vs net, inclusion\/exclusion of taxes and shipping, treatment of discounts and gift cards <\/li>\n
      • Currency handling:<\/strong> multi-currency normalization and exchange rate rules <\/li>\n
      • Refunds\/chargebacks:<\/strong> how negative revenue or reversals are recorded <\/li>\n
      • Timing:<\/strong> recorded at order confirmation vs payment capture vs fulfillment<\/li>\n<\/ul>\n\n\n\n

        Systems and pipelines<\/h3>\n\n\n\n
          \n
        • Event tracking:<\/strong> purchase event, order ID, value, currency, item details <\/li>\n
        • Order system \/ payment processor:<\/strong> the authoritative transaction record <\/li>\n
        • Analytics collection:<\/strong> how data is ingested, deduplicated, and stored <\/li>\n
        • Reporting layer:<\/strong> dashboards and datasets used by stakeholders<\/li>\n<\/ul>\n\n\n\n

          Governance and ownership<\/h3>\n\n\n\n
            \n
          • Marketing:<\/strong> uses Purchase Revenue for channel optimization and campaign evaluation <\/li>\n
          • Analytics team:<\/strong> maintains tracking plans, QA, and attribution logic <\/li>\n
          • Engineering:<\/strong> implements event instrumentation and data reliability <\/li>\n
          • Finance:<\/strong> validates revenue recognition alignment and reconciliation approach<\/li>\n<\/ul>\n\n\n\n

            Strong Conversion & Measurement<\/strong> requires that these components produce Purchase Revenue numbers that are accurate enough to trust and consistent enough to act on.<\/p>\n\n\n\n

            Types of Purchase Revenue<\/h2>\n\n\n\n

            \u201cTypes\u201d vary by business model more than by formal taxonomy. The most useful distinctions are contextual.<\/p>\n\n\n\n

            Gross vs net Purchase Revenue<\/h3>\n\n\n\n
              \n
            • Gross<\/strong> may include the full order total before refunds and sometimes before discounts. <\/li>\n
            • Net<\/strong> attempts to reflect the revenue after discounts, refunds, and adjustments.\nFor Analytics<\/strong>, you must define which one you track and why\u2014otherwise channel comparisons can become misleading.<\/li>\n<\/ul>\n\n\n\n

              First purchase vs repeat purchase revenue<\/h3>\n\n\n\n

              Separating revenue from first-time customers vs returning customers improves Conversion & Measurement<\/strong>. Acquisition channels may drive first purchases, while email or direct traffic may drive repeat Purchase Revenue.<\/p>\n\n\n\n

              Online vs offline purchase revenue<\/h3>\n\n\n\n

              Many businesses have blended journeys. Purchase Revenue may occur online, in-store, or through sales-assisted channels. Measuring offline conversions and importing them into Analytics<\/strong> can significantly change channel performance insights.<\/p>\n\n\n\n

              Subscription vs one-time Purchase Revenue<\/h3>\n\n\n\n

              Subscription businesses may track:\n– initial payment Purchase Revenue\n– recurring payments\n– upgrades\/downgrades\n– renewals\nThis affects forecasting and the interpretation of Conversion & Measurement<\/strong> performance over time.<\/p>\n\n\n\n

              Real-World Examples of Purchase Revenue<\/h2>\n\n\n\n

              Example 1: eCommerce campaign optimization<\/h3>\n\n\n\n

              A retailer runs two paid campaigns with the same number of purchases. In Analytics<\/strong>, Campaign A shows higher Purchase Revenue because it drives higher-priced product bundles. The team shifts budget toward Campaign A and updates Campaign B creative to promote higher-value bundles. This is classic Conversion & Measurement<\/strong>: optimizing for revenue, not just conversions.<\/p>\n\n\n\n

              Example 2: SEO landing page prioritization<\/h3>\n\n\n\n

              An SEO team sees that a product comparison page has lower traffic than a blog guide but produces disproportionately high Purchase Revenue per session. Using Analytics<\/strong>, they prioritize internal linking, content refresh, and technical improvements for the comparison page. Purchase Revenue becomes the metric that justifies work beyond \u201crankings\u201d and ties SEO to business impact.<\/p>\n\n\n\n

              Example 3: App monetization and lifecycle messaging<\/h3>\n\n\n\n

              A mobile app sells in-app credits. The team tracks Purchase Revenue by acquisition source and learns that certain audiences purchase quickly but churn faster, while others have lower initial Purchase Revenue but stronger repeat purchases. In Conversion & Measurement<\/strong>, they adjust onboarding and lifecycle messaging to increase long-term revenue, not only first-day conversions.<\/p>\n\n\n\n

              Benefits of Using Purchase Revenue<\/h2>\n\n\n\n

              When Purchase Revenue is measured consistently, it improves both performance and operational clarity.<\/p>\n\n\n\n

                \n
              • Better optimization:<\/strong> campaigns, audiences, and landing pages can be improved based on real financial outcomes. <\/li>\n
              • Higher efficiency:<\/strong> teams reduce wasted spend by focusing on revenue-producing paths, not vanity metrics. <\/li>\n
              • Improved forecasting:<\/strong> more accurate revenue signals strengthen planning and budgeting. <\/li>\n
              • Stronger customer experience:<\/strong> optimizing for Purchase Revenue often surfaces friction points (checkout issues, payment failures, confusing offers) that harm both users and performance. <\/li>\n
              • Clearer cross-team alignment:<\/strong> Analytics<\/strong> reporting based on Purchase Revenue helps stakeholders agree on what \u201csuccess\u201d means in Conversion & Measurement<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                Challenges of Purchase Revenue<\/h2>\n\n\n\n

                Purchase Revenue is powerful, but it is also easy to measure incorrectly.<\/p>\n\n\n\n

                  \n
                • Attribution limitations:<\/strong> different attribution models can assign Purchase Revenue differently across channels, changing perceived performance. <\/li>\n
                • Tracking gaps:<\/strong> ad blockers, cookie restrictions, and consent choices can reduce observed Purchase Revenue in Analytics<\/strong>. <\/li>\n
                • Data mismatch with finance:<\/strong> Analytics<\/strong> revenue often won\u2019t match accounting revenue due to timing, refunds, taxes, shipping, and recognition rules. <\/li>\n
                • Duplicate or missing transactions:<\/strong> poor instrumentation can double-count orders (retries, reloads) or miss them (failed event fires). <\/li>\n
                • Cross-device identity issues:<\/strong> a user who researches on mobile and buys on desktop may fragment Purchase Revenue across identities.<\/li>\n<\/ul>\n\n\n\n

                  A mature Conversion & Measurement<\/strong> approach expects these issues and designs controls to manage them.<\/p>\n\n\n\n

                  Best Practices for Purchase Revenue<\/h2>\n\n\n\n

                  Define revenue clearly (and document it)<\/h3>\n\n\n\n

                  Specify whether Purchase Revenue includes:\n– taxes and shipping\n– discounts and promotions\n– gift cards and store credit\n– refunds\/chargebacks and how they appear (negative values or separate events)<\/p>\n\n\n\n

                  Clear definitions reduce disputes and make Analytics<\/strong> reports more reliable.<\/p>\n\n\n\n

                  Use transaction IDs and deduplication<\/h3>\n\n\n\n

                  Ensure every purchase has a unique order ID and that your pipeline prevents double counting. This is a foundational technical requirement for trustworthy Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                  Validate against source-of-truth systems<\/h3>\n\n\n\n

                  Regularly reconcile Purchase Revenue totals against your commerce platform or payment records. The goal is not always a perfect match, but a known, explainable difference.<\/p>\n\n\n\n

                  Segment revenue, not just conversions<\/h3>\n\n\n\n

                  Track Purchase Revenue by:\n– channel and campaign\n– device and geography\n– new vs returning customers\n– product categories and margin bands\nThis turns revenue into actionable insight in Analytics<\/strong>.<\/p>\n\n\n\n

                  Monitor data quality continuously<\/h3>\n\n\n\n

                  Create checks for sudden drops, spikes, currency errors, missing parameters, and unusual average order value. Data reliability is an ongoing practice, not a one-time setup.<\/p>\n\n\n\n

                  Tools Used for Purchase Revenue<\/h2>\n\n\n\n

                  Purchase Revenue measurement typically spans multiple tool categories within Conversion & Measurement<\/strong> and Analytics<\/strong>:<\/p>\n\n\n\n

                    \n
                  • Analytics tools:<\/strong> collect purchase events, support segmentation, and provide attribution views. <\/li>\n
                  • Tag management and event tracking systems:<\/strong> manage implementation, event rules, and QA processes. <\/li>\n
                  • Ad platforms:<\/strong> import or receive Purchase Revenue to optimize bidding and measure ROAS. <\/li>\n
                  • CRM and lifecycle tools:<\/strong> connect Purchase Revenue to customer profiles and retention campaigns. <\/li>\n
                  • Data warehouses and ETL pipelines:<\/strong> unify purchase data from multiple sources, deduplicate orders, and enable advanced modeling. <\/li>\n
                  • Reporting dashboards and BI tools:<\/strong> provide stakeholder-ready views of Purchase Revenue trends, cohorts, and channel contribution. <\/li>\n
                  • SEO tools (supporting role):<\/strong> help identify pages and queries that correlate with higher Purchase Revenue, especially when paired with Analytics<\/strong> landing page reporting.<\/li>\n<\/ul>\n\n\n\n

                    The best stack is the one that keeps definitions consistent and makes Purchase Revenue accessible to decision-makers without losing accuracy.<\/p>\n\n\n\n

                    Metrics Related to Purchase Revenue<\/h2>\n\n\n\n

                    Purchase Revenue is often the input for more diagnostic and decision-oriented metrics:<\/p>\n\n\n\n

                      \n
                    • Revenue per session \/ revenue per user:<\/strong> monetization efficiency of traffic or audiences <\/li>\n
                    • Average order value (AOV):<\/strong> helps separate \u201cmore purchases\u201d from \u201chigher-value purchases\u201d <\/li>\n
                    • Conversion rate (purchase):<\/strong> volume efficiency; critical but incomplete without revenue context <\/li>\n
                    • Return on ad spend (ROAS):<\/strong> Purchase Revenue divided by ad spend (mind attribution and timing) <\/li>\n
                    • Customer acquisition cost (CAC) and payback:<\/strong> needs revenue and margin context to be meaningful <\/li>\n
                    • Lifetime value (LTV):<\/strong> extends Purchase Revenue into a longer horizon for subscription and repeat purchase models <\/li>\n
                    • Refund rate \/ return rate:<\/strong> quality and expectation alignment; high Purchase Revenue with high refunds can be a warning sign <\/li>\n
                    • Gross margin contribution (when available):<\/strong> Purchase Revenue is not profit; margin-aware measurement improves decisions<\/li>\n<\/ul>\n\n\n\n

                      A strong Conversion & Measurement<\/strong> practice pairs Purchase Revenue with efficiency and quality signals rather than treating it as a standalone scoreboard.<\/p>\n\n\n\n

                      Future Trends of Purchase Revenue<\/h2>\n\n\n\n

                      Purchase Revenue measurement is evolving due to technology, privacy, and automation shifts:<\/p>\n\n\n\n

                        \n
                      • More modeled measurement:<\/strong> privacy constraints reduce observable tracking, pushing Analytics<\/strong> toward modeled and aggregated approaches for Purchase Revenue. <\/li>\n
                      • Server-side and first-party data growth:<\/strong> organizations increasingly move data collection closer to the source to improve reliability and control. <\/li>\n
                      • AI-assisted insights:<\/strong> anomaly detection, forecasting, and creative optimization will use Purchase Revenue as a primary outcome for learning systems. <\/li>\n
                      • Better incrementality practices:<\/strong> instead of relying only on attribution, teams will use experiments and lift studies to estimate the incremental Purchase Revenue caused by marketing. <\/li>\n
                      • Personalization tied to value:<\/strong> experiences will adapt not just to convert, but to increase Purchase Revenue through bundles, upsells, and retention\u2014measured within Conversion & Measurement<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                        The common direction: more resilient measurement and more decisioning based on Purchase Revenue quality, not just quantity.<\/p>\n\n\n\n

                        Purchase Revenue vs Related Terms<\/h2>\n\n\n\n

                        Purchase Revenue vs Revenue (general)<\/h3>\n\n\n\n

                        Revenue in finance is a broad accounting concept with strict recognition rules. Purchase Revenue in Analytics<\/strong> is an operational measurement used for optimization and may differ due to timing, refunds, taxes, or tracking gaps. They should be reconcilable, but they are not identical by default.<\/p>\n\n\n\n

                        Purchase Revenue vs Conversion Value<\/h3>\n\n\n\n

                        Conversion value is a more general term for the value assigned to any conversion (lead, signup, trial, purchase). Purchase Revenue is specifically tied to transactions and monetary purchase amounts, making it more concrete for Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                        Purchase Revenue vs Average Order Value (AOV)<\/h3>\n\n\n\n

                        AOV is an average derived from revenue and order count. Purchase Revenue is the total (or segmented total) amount. You use Purchase Revenue to compute AOV, but AOV alone can hide whether growth is coming from more orders or larger orders.<\/p>\n\n\n\n

                        Who Should Learn Purchase Revenue<\/h2>\n\n\n\n
                          \n
                        • Marketers:<\/strong> to optimize channels based on outcomes and defend budgets with revenue evidence in Analytics<\/strong>. <\/li>\n
                        • Analysts:<\/strong> to design consistent definitions, validate data quality, and build trusted Conversion & Measurement<\/strong> reporting. <\/li>\n
                        • Agencies:<\/strong> to demonstrate business impact and improve campaign strategy using Purchase Revenue, not just traffic metrics. <\/li>\n
                        • Business owners and founders:<\/strong> to understand what drives revenue, where growth is profitable, and which initiatives deserve investment. <\/li>\n
                        • Developers:<\/strong> to implement reliable event tracking, deduplication, and integrations that make Purchase Revenue accurate and usable.<\/li>\n<\/ul>\n\n\n\n

                          Summary of Purchase Revenue<\/h2>\n\n\n\n

                          Purchase Revenue is the measured monetary value generated by completed purchases, used as a core outcome metric in Conversion & Measurement<\/strong>. In practical Analytics<\/strong>, it enables segmentation, attribution, optimization, and forecasting tied to real business results. When defined clearly and tracked reliably, Purchase Revenue helps teams allocate budgets smarter, improve customer journeys, and connect marketing performance to revenue impact.<\/p>\n\n\n\n

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

                          1) What is Purchase Revenue and what should it include?<\/h3>\n\n\n\n

                          Purchase Revenue is the revenue value tied to completed purchases. What it includes depends on your definition\u2014commonly the item subtotal or order total, with explicit rules for taxes, shipping, discounts, and refunds. Document the definition so Conversion & Measurement<\/strong> remains consistent.<\/p>\n\n\n\n

                          2) Why doesn\u2019t Purchase Revenue in Analytics match finance revenue?<\/h3>\n\n\n\n

                          Differences usually come from timing (order vs capture vs recognition), refunds\/chargebacks, taxes and shipping treatment, currency conversions, and tracking gaps. Analytics<\/strong> aims to support optimization, while finance follows accounting rules.<\/p>\n\n\n\n

                          3) How can I avoid double-counting Purchase Revenue?<\/h3>\n\n\n\n

                          Use a unique transaction\/order ID, deduplicate events in your pipeline, and test edge cases like refreshes, retries, and multiple thank-you page loads. This is a core technical control for trustworthy Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                          4) Is Purchase Revenue the same as profit?<\/h3>\n\n\n\n

                          No. Purchase Revenue is top-line money from purchases, not profit. To assess profitability, pair it with cost data and (when possible) margin or contribution metrics in Analytics<\/strong>.<\/p>\n\n\n\n

                          5) Which attribution model should I use for Purchase Revenue?<\/h3>\n\n\n\n

                          There is no universal best model. Choose an attribution approach that matches your buying cycle and decision needs, and supplement it with experiments or incrementality tests when possible. Consistency over time is crucial for Conversion & Measurement<\/strong> comparisons.<\/p>\n\n\n\n

                          6) Can I track Purchase Revenue for offline sales?<\/h3>\n\n\n\n

                          Yes, if you can connect offline transactions to marketing touchpoints using a consistent identifier and import the results into your Analytics<\/strong> and reporting workflows. Be clear about matching logic and privacy requirements.<\/p>\n\n\n\n

                          7) What\u2019s the best way to use Purchase Revenue for optimization?<\/h3>\n\n\n\n

                          Segment Purchase Revenue by channel, campaign, audience, and landing page; monitor revenue per session and AOV; validate data quality; and test changes via controlled experiments. This turns Purchase Revenue into actionable Conversion & Measurement<\/strong> insight rather than a static report.<\/p>\n","protected":false},"excerpt":{"rendered":"

                          Purchase Revenue is the amount of money your business generates from completed purchases that you can attribute to marketing, product experiences, and sales activities through **Conversion & Measurement**. In practical **Analytics**, it\u2019s the revenue value tied to a conversion event (a purchase) and used to evaluate what is truly working\u2014not just what is getting clicks.<\/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-6918","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\/6918","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=6918"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6918\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=6918"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=6918"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=6918"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}