{"id":7299,"date":"2026-03-24T07:34:42","date_gmt":"2026-03-24T07:34:42","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/form-id\/"},"modified":"2026-03-24T07:34:42","modified_gmt":"2026-03-24T07:34:42","slug":"form-id","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/form-id\/","title":{"rendered":"Form Id: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Tracking"},"content":{"rendered":"\n

In digital marketing, a \u201cform submission\u201d is often the moment intent becomes a lead, signup, quote request, or purchase. A Form Id<\/strong> is the identifier that lets your analytics and marketing systems distinguish which<\/em> form was completed\u2014so your Conversion & Measurement<\/strong> program can attribute outcomes correctly and your Tracking<\/strong> stays clean across pages, campaigns, and devices.<\/p>\n\n\n\n

Form experiences are increasingly dynamic: a single page can host multiple forms, forms can appear in modals, and A\/B tests can swap layouts without changing URLs. In that environment, relying on page-level signals alone leads to misattribution and blind spots. Using a Form Id<\/strong> gives you a stable \u201chandle\u201d for measurement, helping teams answer questions like: Which lead form drives the best-qualified pipeline? Which signup flow drops off? Which campaign fills which form?<\/p>\n\n\n\n

\n\n\n\n

What Is Form Id?<\/h2>\n\n\n\n

A Form Id<\/strong> is a unique identifier assigned to a specific form instance so it can be recognized consistently across systems. In practice, it may come from a website\u2019s markup or front-end framework, a form builder, a tag manager, or a CRM\/marketing automation platform that hosts or embeds the form.<\/p>\n\n\n\n

At a beginner level, think of Form Id<\/strong> as the \u201cserial number\u201d of a form. Two forms might look similar, but their identifiers let your Tracking<\/strong> differentiate them\u2014especially when multiple forms exist on the same page or share similar labels like \u201cContact Us.\u201d<\/p>\n\n\n\n

From a business perspective, Form Id<\/strong> is the bridge between user actions and measurable outcomes. When your Conversion & Measurement<\/strong> stack records \u201cForm submitted,\u201d the Form Id<\/strong> tells you which conversion mechanism<\/em> actually performed. That makes reporting actionable: you can optimize the right form, not just the right page.<\/p>\n\n\n\n

Within Conversion & Measurement<\/strong>, Form Id<\/strong> is commonly used to:\n– Attribute conversions to specific form experiences (lead-gen, demo request, newsletter, checkout).\n– Segment conversion performance by form type, placement, audience, or campaign.\n– Connect on-site behavior to downstream CRM outcomes (qualified leads, opportunities, revenue).<\/p>\n\n\n\n

In Tracking<\/strong>, Form Id<\/strong> is often captured as an event parameter, stored as a custom dimension, or mapped to a standardized taxonomy so different teams and tools interpret it consistently.<\/p>\n\n\n\n

\n\n\n\n

Why Form Id Matters in Conversion & Measurement<\/h2>\n\n\n\n

A strong Conversion & Measurement<\/strong> strategy aims to measure what matters, not just what\u2019s easy. Forms are high-value touchpoints, but without a Form Id<\/strong>, many organizations end up with vague conversion data like \u201cform_submit\u201d that can\u2019t be tied to a specific business outcome.<\/p>\n\n\n\n

Using Form Id<\/strong> creates strategic leverage in several ways:<\/p>\n\n\n\n

    \n
  • Clearer attribution for growth decisions:<\/strong> When you can tie lead volume and quality to a specific form, you can prioritize the best-performing experiences rather than making assumptions based on page traffic.<\/li>\n
  • Better budget allocation:<\/strong> Campaigns often drive to different forms (webinar signup vs. demo request). Accurate Tracking<\/strong> using Form Id<\/strong> helps ensure spend is optimized for the conversions you actually want.<\/li>\n
  • Faster optimization cycles:<\/strong> Form-level diagnostics (view-to-start, start-to-submit, error rate) become possible when forms are uniquely identified.<\/li>\n
  • Competitive advantage through measurement maturity:<\/strong> Many competitors still measure \u201csubmissions\u201d in aggregate. A disciplined Form Id<\/strong> approach improves insight quality and speeds experimentation, which compounds over time.<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    How Form Id Works<\/h2>\n\n\n\n

    A Form Id<\/strong> is simple as a concept, but powerful in execution. In real implementations, it usually flows through a measurement workflow like this:<\/p>\n\n\n\n

      \n
    1. \n

      Input or trigger<\/strong>\n A user views, starts, or submits a form. Your website or form platform exposes an identifier (the Form Id<\/strong>) associated with that form instance.<\/p>\n<\/li>\n

    2. \n

      Analysis or processing<\/strong>\n Your instrumentation captures the Form Id<\/strong> at the moment of interaction. This could be read from the page, from a form embed configuration, or from a platform event. In good Tracking<\/strong>, you also capture context such as page location, form placement (header\/footer\/modal), device, and traffic source.<\/p>\n<\/li>\n

    3. \n

      Execution or application<\/strong>\n The captured Form Id<\/strong> is sent to your analytics endpoint or measurement pipeline as an event parameter (for example, \u201cform_submit\u201d with \u201cform_id=XYZ\u201d). In more mature Conversion & Measurement<\/strong>, the same Form Id<\/strong> is also passed into the CRM or marketing automation record so downstream outcomes can be joined back to the original form.<\/p>\n<\/li>\n

    4. \n

      Output or outcome<\/strong>\n Reporting and dashboards use Form Id<\/strong> to break down performance: submissions, conversion rate, qualified lead rate, and revenue impact. Optimization teams use this to improve copy, layout, validation, and routing.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      This is how Form Id<\/strong> turns \u201csomeone submitted something\u201d into decision-grade measurement.<\/p>\n\n\n\n

      \n\n\n\n

      Key Components of Form Id<\/h2>\n\n\n\n

      A reliable Form Id<\/strong> approach depends on more than just picking an identifier. The strongest implementations include:<\/p>\n\n\n\n

        \n
      • A consistent identifier source:<\/strong> The Form Id<\/strong> might be defined by the site (front-end), the form tool, or the CRM. Consistency matters more than where it originates.<\/li>\n
      • An event taxonomy:<\/strong> A shared naming system for events like \u201cform_view,\u201d \u201cform_start,\u201d \u201cform_submit,\u201d and \u201cform_error,\u201d each carrying Form Id<\/strong> as a parameter. This reduces ambiguity across teams.<\/li>\n
      • Data layer or instrumentation layer:<\/strong> Many sites use an intermediate layer to standardize what gets sent to analytics. This is where Form Id<\/strong> is normalized.<\/li>\n
      • Analytics and reporting schema:<\/strong> Your analytics setup should store Form Id<\/strong> in a way that enables segmentation and long-term trend analysis (not just ephemeral debugging).<\/li>\n
      • CRM\/lead routing integration:<\/strong> If your business qualifies leads, mapping Form Id<\/strong> into lead records supports closed-loop Conversion & Measurement<\/strong>.<\/li>\n
      • Governance and ownership:<\/strong> Marketing ops, analytics, and development should agree on who creates, documents, and updates Form Id<\/strong> values\u2014especially during redesigns and tests.<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n

        Types of Form Id<\/h2>\n\n\n\n

        \u201cTypes\u201d of Form Id<\/strong> are less about formal standards and more about practical contexts. Common distinctions include:<\/p>\n\n\n\n

        1) Front-end (site-defined) Form Id<\/h3>\n\n\n\n

        This identifier is defined within the website implementation (often tied to the form component). It\u2019s useful when you control the site code and need stable Tracking<\/strong> across experiments and page templates.<\/p>\n\n\n\n

        2) Platform-generated Form Id<\/h3>\n\n\n\n

        Many form builders and marketing automation tools assign their own Form Id<\/strong>. This can be highly reliable, especially when the same form is embedded in multiple places.<\/p>\n\n\n\n

        3) CRM or database Form Id<\/h3>\n\n\n\n

        Some organizations treat the CRM\u2019s internal form identifier as the source of truth. This is valuable for Conversion & Measurement<\/strong> that connects form submissions to pipeline stages and revenue.<\/p>\n\n\n\n

        4) Contextual Form Id (composite identifiers)<\/h3>\n\n\n\n

        When a single form template appears in multiple placements, teams sometimes encode placement into the identifier (for example: \u201cdemo_request__pricing_page_modal\u201d). This improves analysis but requires governance to avoid uncontrolled variation.<\/p>\n\n\n\n

        \n\n\n\n

        Real-World Examples of Form Id<\/h2>\n\n\n\n

        Example 1: B2B demo requests across multiple pages<\/h3>\n\n\n\n

        A SaaS company embeds the same \u201cRequest a Demo\u201d form on the homepage, pricing page, and in a modal triggered by exit intent. Without Form Id<\/strong>, all submissions look identical. With Form Id<\/strong>, Tracking<\/strong> reveals the modal converts well but produces lower-qualified leads, while the pricing page converts slightly less but drives more opportunities. Conversion & Measurement<\/strong> improves by optimizing for qualified pipeline, not just raw submissions.<\/p>\n\n\n\n

        Example 2: E-commerce lead capture vs. customer support forms<\/h3>\n\n\n\n

        An e-commerce brand runs a newsletter signup form and a customer support contact form. If both are tracked as \u201cform_submit,\u201d marketing may overcount conversions. Using Form Id<\/strong> distinguishes acquisition (newsletter) from service (support), keeping Conversion & Measurement<\/strong> aligned to business outcomes and preventing misleading campaign reports.<\/p>\n\n\n\n

        Example 3: Multi-step onboarding with progressive profiling<\/h3>\n\n\n\n

        A product signup flow collects email first, then asks additional questions after verification. Assigning a Form Id<\/strong> per step enables step-level Tracking<\/strong> (drop-offs, validation errors, completion time). The team identifies that a particular step causes friction on mobile and improves completion rate by simplifying fields\u2014directly lifting activation metrics.<\/p>\n\n\n\n

        \n\n\n\n

        Benefits of Using Form Id<\/h2>\n\n\n\n

        Using Form Id<\/strong> well delivers measurable improvements across marketing, analytics, and operations:<\/p>\n\n\n\n

          \n
        • Higher-quality optimization:<\/strong> You can compare form variants, placements, and audiences with confidence, improving conversion rate and lead quality.<\/li>\n
        • Reduced reporting confusion:<\/strong> Clear identifiers prevent \u201cmystery conversions\u201d and reduce time spent reconciling dashboards.<\/li>\n
        • Better experiment analysis:<\/strong> A\/B testing and personalization are easier to interpret when Tracking<\/strong> ties outcomes to a specific form experience.<\/li>\n
        • More efficient lead operations:<\/strong> When sales teams see where leads came from (via Form Id<\/strong>), routing and follow-up can be tailored, often improving speed-to-lead and close rates.<\/li>\n
        • Improved user experience:<\/strong> Form-level analytics (errors, time to complete) highlights friction that hurts customers and revenue.<\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n

          Challenges of Form Id<\/h2>\n\n\n\n

          Even though Form Id<\/strong> sounds straightforward, real-world Tracking<\/strong> introduces pitfalls:<\/p>\n\n\n\n

            \n
          • Identifier instability:<\/strong> Redesigns, form rebuilds, or platform migrations can change IDs and break trends over time.<\/li>\n
          • Duplicate forms or cloned embeds:<\/strong> Copying a form can accidentally reuse an identifier, causing mixed data.<\/li>\n
          • Dynamic rendering issues:<\/strong> Single-page apps and modal forms can generate forms at runtime, making it harder to reliably capture Form Id<\/strong>.<\/li>\n
          • Inconsistent naming conventions:<\/strong> If teams invent identifiers ad hoc, reporting becomes fragmented and Conversion & Measurement<\/strong> loses clarity.<\/li>\n
          • Privacy and consent constraints:<\/strong> In some environments, data collection is restricted until consent. Your measurement plan must ensure Tracking<\/strong> remains compliant while still capturing essential form signals where permitted.<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n

            Best Practices for Form Id<\/h2>\n\n\n\n

            To make Form Id<\/strong> durable and useful, apply these practical practices:<\/p>\n\n\n\n

              \n
            • Define a \u201csource of truth\u201d:<\/strong> Decide whether the site, form platform, or CRM owns the canonical Form Id<\/strong>, then document it.<\/li>\n
            • Keep identifiers stable:<\/strong> Avoid encoding details that change frequently (like temporary campaign names) directly into Form Id<\/strong>.<\/li>\n
            • Create a naming convention:<\/strong> If you use readable identifiers, standardize structure (purpose, product line, placement) and enforce it through reviews.<\/li>\n
            • Track the full funnel, not just submit:<\/strong> Capture view\/start\/submit\/error events using the same Form Id<\/strong> so you can diagnose drop-offs.<\/li>\n
            • Pass Form Id downstream:<\/strong> Where feasible, store Form Id<\/strong> on the lead\/contact record. This strengthens closed-loop Conversion & Measurement<\/strong> and post-conversion analysis.<\/li>\n
            • Monitor for breakage:<\/strong> Add automated checks for sudden drops in events per Form Id<\/strong>, new unknown IDs, or spikes that indicate duplicates.<\/li>\n
            • Plan for migrations:<\/strong> When forms move platforms, maintain a mapping table (old to new Form Id<\/strong>) to preserve historical comparability.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              Tools Used for Form Id<\/h2>\n\n\n\n

              You don\u2019t need a specific vendor to operationalize Form Id<\/strong>, but you do need coordinated tooling across Conversion & Measurement<\/strong> and Tracking<\/strong>:<\/p>\n\n\n\n

                \n
              • Analytics tools:<\/strong> Capture form events and store Form Id<\/strong> as an event parameter or dimension for segmentation.<\/li>\n
              • Tag management systems:<\/strong> Standardize event collection and ensure Form Id<\/strong> is consistently passed with each interaction.<\/li>\n
              • Marketing automation and form builders:<\/strong> Create and manage forms, often generating a platform Form Id<\/strong> that can be reused in reporting.<\/li>\n
              • CRM systems:<\/strong> Store Form Id<\/strong> on lead\/contact records to support attribution to pipeline and revenue.<\/li>\n
              • Data warehouses and pipelines:<\/strong> Join Form Id<\/strong> across analytics + CRM + product data for deeper modeling.<\/li>\n
              • Reporting dashboards\/BI:<\/strong> Visualize performance by Form Id<\/strong>, including trends, funnel steps, and lead quality.<\/li>\n
              • Experimentation and personalization tools:<\/strong> Connect experiments to form outcomes using Tracking<\/strong> parameters, including Form Id<\/strong>.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n

                Metrics Related to Form Id<\/h2>\n\n\n\n

                A Form Id<\/strong> becomes valuable when it unlocks form-level metrics that guide action. Common metrics include:<\/p>\n\n\n\n

                  \n
                • Form view rate:<\/strong> How often each Form Id<\/strong> is seen (useful for placement and traffic allocation).<\/li>\n
                • Start rate:<\/strong> Percentage of viewers who begin interacting with the form.<\/li>\n
                • Submission conversion rate:<\/strong> Submits divided by views or starts, tracked per Form Id<\/strong>.<\/li>\n
                • Error rate and error frequency:<\/strong> Validation issues by Form Id<\/strong>, often a leading indicator of UX problems.<\/li>\n
                • Time to complete:<\/strong> How long users take to submit a form; long times can signal confusion or excessive fields.<\/li>\n
                • Abandonment rate:<\/strong> Starts minus submits, highlighting friction points.<\/li>\n
                • Lead quality rate:<\/strong> Percentage of submissions that become qualified leads or opportunities by Form Id<\/strong> (core to mature Conversion & Measurement<\/strong>).<\/li>\n
                • Cost per lead \/ cost per qualified lead:<\/strong> Combining paid media cost with submissions and downstream outcomes by Form Id<\/strong>.<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n

                  Future Trends of Form Id<\/h2>\n\n\n\n

                  Form Id<\/strong> will remain central to Conversion & Measurement<\/strong> because forms remain a primary conversion mechanism\u2014even as interfaces evolve.<\/p>\n\n\n\n

                  Key trends shaping how teams use Form Id<\/strong>:<\/p>\n\n\n\n

                    \n
                  • More automation in instrumentation:<\/strong> Modern analytics stacks increasingly auto-capture interactions, but teams still need a stable Form Id<\/strong> strategy to avoid noisy, inconsistent labels.<\/li>\n
                  • AI-assisted optimization:<\/strong> AI can analyze patterns like error spikes or drop-offs by Form Id<\/strong>, recommending field reductions, copy changes, or step restructuring.<\/li>\n
                  • Personalization and modular forms:<\/strong> As forms become personalized (different fields for different segments), Tracking<\/strong> must capture both Form Id<\/strong> and variant context to keep measurement interpretable.<\/li>\n
                  • Privacy-driven measurement changes:<\/strong> Consent rules and browser limitations push teams toward first-party, server-side, and modeled measurement. Form Id<\/strong> becomes even more important as a first-party key that links events to business outcomes within compliant boundaries.<\/li>\n
                  • Stronger governance and data contracts:<\/strong> Organizations are formalizing event schemas. Form Id<\/strong> will increasingly be treated as a required field in form-related events.<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n

                    Form Id vs Related Terms<\/h2>\n\n\n\n

                    Understanding adjacent concepts helps avoid measurement mistakes:<\/p>\n\n\n\n

                    Form Id vs Form Name<\/h3>\n\n\n\n

                    A form name is often human-friendly (\u201cContact Sales\u201d), while Form Id<\/strong> is meant to be unique and stable for Tracking<\/strong>. Names can change for UX reasons; identifiers should change only when the underlying form meaning changes.<\/p>\n\n\n\n

                    Form Id vs Event Name<\/h3>\n\n\n\n

                    The event name describes what happened (for example, \u201cform_submit\u201d). Form Id<\/strong> describes which form<\/em> it happened on. In Conversion & Measurement<\/strong>, you usually need both: a consistent event taxonomy plus identifiers for segmentation.<\/p>\n\n\n\n

                    Form Id vs Page URL<\/h3>\n\n\n\n

                    A URL identifies where the form was seen, not necessarily which form was used. Multiple forms can live on one URL, and the same form can appear on multiple URLs. Form Id<\/strong> prevents URL-based ambiguity and improves attribution.<\/p>\n\n\n\n

                    \n\n\n\n

                    Who Should Learn Form Id<\/h2>\n\n\n\n

                    Form Id<\/strong> knowledge is valuable across roles because it sits at the intersection of execution and measurement:<\/p>\n\n\n\n

                      \n
                    • Marketers:<\/strong> Improve campaign attribution, landing page optimization, and lead quality analysis.<\/li>\n
                    • Analysts:<\/strong> Build cleaner reporting, reduce ambiguity, and enable deeper funnel diagnostics within Conversion & Measurement<\/strong>.<\/li>\n
                    • Agencies:<\/strong> Deliver measurable outcomes with reliable Tracking<\/strong>, especially when managing multiple clients and templates.<\/li>\n
                    • Business owners and founders:<\/strong> Understand which lead mechanisms drive revenue, not just traffic or vanity metrics.<\/li>\n
                    • Developers:<\/strong> Implement stable identifiers, ensure instrumentation survives redesigns, and support scalable analytics.<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n

                      Summary of Form Id<\/h2>\n\n\n\n

                      A Form Id<\/strong> is a unique identifier for a form that enables accurate Tracking<\/strong> and actionable Conversion & Measurement<\/strong>. It helps teams distinguish conversions across pages, placements, and variants, and it supports deeper funnel metrics like starts, errors, abandonment, and downstream lead quality. When governed properly and passed through analytics and CRM systems, Form Id<\/strong> becomes a durable key that turns form submissions into reliable business insight.<\/p>\n\n\n\n

                      \n\n\n\n

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

                      1) What is a Form Id and where does it come from?<\/h3>\n\n\n\n

                      A Form Id<\/strong> is a unique identifier for a specific form. It may come from your website implementation, a form builder\/marketing automation platform, or your CRM, depending on how forms are created and embedded.<\/p>\n\n\n\n

                      2) Do I need a different Form Id for the same form embedded on multiple pages?<\/h3>\n\n\n\n

                      Not always. If it\u2019s truly the same form (same purpose, fields, and routing), using one Form Id<\/strong> can be useful for consolidated reporting. If placement meaningfully changes intent or performance, consider a separate Form Id<\/strong> or capture placement as an additional parameter for Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                      3) How does Form Id improve Tracking compared to using the page URL?<\/h3>\n\n\n\n

                      URLs can\u2019t reliably distinguish multiple forms on one page or the same form used across many pages. Tracking<\/strong> with Form Id<\/strong> removes that ambiguity and enables form-level segmentation.<\/p>\n\n\n\n

                      4) What should I do if Form Id values change after a redesign?<\/h3>\n\n\n\n

                      Treat it as a measurement migration: document old and new Form Id<\/strong> values, create a mapping for reporting continuity, and annotate the change so trends in Conversion & Measurement<\/strong> remain interpretable.<\/p>\n\n\n\n

                      5) Should Form Id be human-readable or numeric?<\/h3>\n\n\n\n

                      Either can work. Human-readable identifiers improve debugging and reporting clarity, while numeric IDs can be cleaner and less error-prone. The most important factor is stability and consistent governance in Tracking<\/strong>.<\/p>\n\n\n\n

                      6) Can I measure form errors and abandonment using Form Id?<\/h3>\n\n\n\n

                      Yes. If you track \u201cform_start,\u201d \u201cform_error,\u201d and \u201cform_submit\u201d events and include Form Id<\/strong> in each, you can quantify abandonment, identify problematic fields, and prioritize UX fixes that improve Conversion & Measurement<\/strong> outcomes.<\/p>\n","protected":false},"excerpt":{"rendered":"

                      In digital marketing, a \u201cform submission\u201d is often the moment intent becomes a lead, signup, quote request, or purchase. A **Form Id** is the identifier that lets your analytics and marketing systems distinguish *which* form was completed\u2014so your **Conversion & Measurement** program can attribute outcomes correctly and your **Tracking** stays clean across pages, campaigns, and devices.<\/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":[1890],"tags":[],"class_list":["post-7299","post","type-post","status-publish","format-standard","hentry","category-tracking"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7299","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=7299"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7299\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7299"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7299"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}