{"id":11602,"date":"2026-04-02T04:09:52","date_gmt":"2026-04-02T04:09:52","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/privacy-dashboard\/"},"modified":"2026-04-02T04:09:52","modified_gmt":"2026-04-02T04:09:52","slug":"privacy-dashboard","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/privacy-dashboard\/","title":{"rendered":"Privacy Dashboard: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Privacy & Consent"},"content":{"rendered":"\n

A Privacy Dashboard<\/strong> is a centralized view that helps an organization understand, manage, and prove how it handles personal data, user choices, and compliance obligations. In Privacy & Consent<\/strong> work, it acts like an operational command center: it brings together signals from consent collection, tracking technologies, data flows, and user requests so teams can make decisions confidently and quickly.<\/p>\n\n\n\n

As privacy expectations rise and regulations evolve, a Privacy Dashboard matters because Privacy & Consent<\/strong> is no longer a one-time legal exercise. It\u2019s an ongoing system that touches marketing performance, analytics reliability, customer trust, and the ability to run campaigns responsibly. When implemented well, a Privacy Dashboard turns privacy from \u201cunknown risk\u201d into measurable, manageable operations within your broader Privacy & Consent<\/strong> strategy.<\/p>\n\n\n\n

What Is Privacy Dashboard?<\/h2>\n\n\n\n

A Privacy Dashboard<\/strong> is a structured interface\u2014often a set of reports, controls, and workflows\u2014that consolidates privacy-related information into a usable view for specific audiences (such as customers, marketers, security teams, or compliance leaders). It can be customer-facing (so people can see and manage their choices) or internal-facing (so teams can govern data use and track compliance tasks).<\/p>\n\n\n\n

The core concept is visibility plus control:<\/p>\n\n\n\n

    \n
  • Visibility:<\/strong> what data is collected, where it goes, which tags fire, which vendors receive data, and what consents exist.<\/li>\n
  • Control:<\/strong> the ability to change settings, enforce rules, or route actions (e.g., restrict tracking until consent is present).<\/li>\n<\/ul>\n\n\n\n

    From a business standpoint, a Privacy Dashboard helps reduce regulatory risk, prevent accidental misuse of data, and protect marketing measurement from \u201csilent failure\u201d (like tags firing incorrectly or consent signals not reaching downstream tools).<\/p>\n\n\n\n

    In Privacy & Consent<\/strong>, the Privacy Dashboard sits at the intersection of governance, technology, and customer experience. It supports Privacy & Consent<\/strong> execution by making privacy status measurable and operational rather than abstract.<\/p>\n\n\n\n

    Why Privacy Dashboard Matters in Privacy & Consent<\/h2>\n\n\n\n

    A Privacy Dashboard has strategic importance because it aligns multiple teams around one source of truth. Without it, privacy decisions tend to be scattered across legal documents, ticket queues, tag managers, and vendor settings\u2014creating gaps that are hard to detect until something breaks.<\/p>\n\n\n\n

    Key business value areas include:<\/p>\n\n\n\n

      \n
    • Trust and retention:<\/strong> Clear preference controls reduce frustration and can increase long-term loyalty, especially in subscription and high-consideration categories.<\/li>\n
    • Risk reduction:<\/strong> Central tracking of consent coverage, vendor disclosures, and request handling reduces compliance exposure and audit pain.<\/li>\n
    • Marketing resilience:<\/strong> When consent is managed consistently, campaign attribution and audience building become more stable\u2014especially as browsers and platforms reduce third-party tracking.<\/li>\n
    • Competitive advantage:<\/strong> Organizations that can explain their data practices clearly often win deals, partnerships, and enterprise procurement reviews.<\/li>\n<\/ul>\n\n\n\n

      In practical terms, a Privacy Dashboard turns Privacy & Consent<\/strong> from \u201cpolicy\u201d into \u201cprocess,\u201d which is what modern privacy programs require.<\/p>\n\n\n\n

      How Privacy Dashboard Works<\/h2>\n\n\n\n

      A Privacy Dashboard<\/strong> can be implemented in different ways, but the practical workflow usually looks like this:<\/p>\n\n\n\n

        \n
      1. \n

        Input \/ triggers<\/strong>\n The dashboard receives signals such as consent choices (opt-in\/opt-out), cookie categories, user identity status (known vs anonymous), data processing activities, tag scans, and privacy requests (access, deletion, correction).<\/p>\n<\/li>\n

      2. \n

        Processing \/ normalization<\/strong>\n Those signals are standardized so they mean the same thing across tools. For example, \u201cmarketing cookies allowed\u201d must map consistently to analytics collection, ad pixels, and server-side event routing. This step often includes policy rules, vendor mappings, and region-specific logic.<\/p>\n<\/li>\n

      3. \n

        Execution \/ enforcement<\/strong>\n The dashboard either directly controls enforcement or reflects enforcement done elsewhere. Examples include blocking tags until consent is granted, restricting downstream sharing to approved vendors, or routing a deletion request to systems that store user profiles.<\/p>\n<\/li>\n

      4. \n

        Outputs \/ outcomes<\/strong>\n Outputs include privacy status reporting, consent coverage trends, unresolved requests, vendor compliance status, and audit-ready logs. For customer-facing experiences, outputs also include user controls (download data, change preferences, opt out).<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        In Privacy & Consent<\/strong> operations, the key is not the \u201cscreen\u201d\u2014it\u2019s the reliability of the signals and the actions tied to them.<\/p>\n\n\n\n

        Key Components of Privacy Dashboard<\/h2>\n\n\n\n

        A robust Privacy Dashboard typically includes the following elements:<\/p>\n\n\n\n

        Data inputs and sources<\/h3>\n\n\n\n
          \n
        • Consent interactions from banners, pop-ups, and preference centers<\/li>\n
        • Website\/app tracking events and tag firing behavior<\/li>\n
        • CRM and identity systems (where lawful and appropriate)<\/li>\n
        • Vendor and partner lists, including disclosure requirements<\/li>\n
        • Privacy request intake (forms, support tickets, email workflows)<\/li>\n
        • Data inventory signals (what categories of data exist and where)<\/li>\n<\/ul>\n\n\n\n

          Controls and workflows<\/h3>\n\n\n\n
            \n
          • Rules that define when tracking is allowed, limited, or prohibited<\/li>\n
          • Role-based access (marketing vs compliance vs engineering)<\/li>\n
          • Request processing workflows and approvals<\/li>\n
          • Evidence logs for changes and actions taken<\/li>\n<\/ul>\n\n\n\n

            Reporting views<\/h3>\n\n\n\n
              \n
            • Executive summaries (risk, trends, SLA performance)<\/li>\n
            • Marketing views (consent rate by region\/device, measurement impact)<\/li>\n
            • Technical views (tag audits, vendor endpoints, data routing status)<\/li>\n
            • Compliance views (request queues, completion status, documentation)<\/li>\n<\/ul>\n\n\n\n

              Governance ownership<\/h3>\n\n\n\n

              A Privacy Dashboard succeeds when ownership is clear. Common responsibility splits include:\n– Marketing ops: tag governance and campaign implications\n– Engineering: implementation integrity and data routing\n– Legal\/compliance: policy alignment and recordkeeping\n– Security\/privacy office: risk oversight and incident coordination <\/p>\n\n\n\n

              This cross-functional governance is central to Privacy & Consent<\/strong> maturity and to sustaining Privacy & Consent<\/strong> improvements over time.<\/p>\n\n\n\n

              Types of Privacy Dashboard<\/h2>\n\n\n\n

              \u201cPrivacy Dashboard\u201d isn\u2019t a single rigid standard, but it commonly shows up in a few practical forms:<\/p>\n\n\n\n

                \n
              1. \n

                Customer-facing Privacy Dashboard<\/strong>\n Lets individuals view and manage privacy choices (communication preferences, consent categories, data rights requests). This is most visible in Privacy & Consent<\/strong> UX.<\/p>\n<\/li>\n

              2. \n

                Internal Privacy Dashboard (operations and compliance)<\/strong>\n Built for teams to track compliance obligations, request SLAs, data processing activities, and vendor status.<\/p>\n<\/li>\n

              3. \n

                Marketing and measurement Privacy Dashboard<\/strong>\n Focuses on how consent impacts analytics quality, attribution, audience eligibility, and conversion tracking\u2014critical for performance marketing under modern Privacy & Consent<\/strong> constraints.<\/p>\n<\/li>\n

              4. \n

                Hybrid model<\/strong>\n Combines customer controls with internal reporting and evidence logs. Many organizations evolve toward this as Privacy & Consent<\/strong> programs mature.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                Real-World Examples of Privacy Dashboard<\/h2>\n\n\n\n

                Example 1: Consent-aware campaign measurement<\/h3>\n\n\n\n

                A retail brand launches paid campaigns across multiple regions. Their Privacy Dashboard shows opt-in rates by country, device, and traffic source, and flags when consent signals aren\u2019t reaching analytics. Marketing learns one landing page template is missing consent-mode integration, causing attribution drops. Fixing it improves reporting consistency while keeping Privacy & Consent<\/strong> rules intact.<\/p>\n\n\n\n

                Example 2: Vendor governance for a new marketing tool<\/h3>\n\n\n\n

                A SaaS team wants to add a new chat widget. The internal Privacy Dashboard includes a vendor intake workflow: data categories collected, processing purpose, retention, sub-processors, and regional restrictions. The widget is approved only after the right configurations are validated (e.g., no tracking before consent). This prevents \u201cshadow data sharing\u201d and strengthens the Privacy & Consent<\/strong> posture.<\/p>\n\n\n\n

                Example 3: Handling deletion requests across systems<\/h3>\n\n\n\n

                A consumer app receives deletion requests that must propagate to analytics, CRM, and support tooling. The Privacy Dashboard shows request status by system, deadlines, and failures (e.g., one downstream tool failing API deletion). Operations can intervene quickly and document outcomes, improving reliability and audit readiness within Privacy & Consent<\/strong> operations.<\/p>\n\n\n\n

                Benefits of Using Privacy Dashboard<\/h2>\n\n\n\n

                A well-designed Privacy Dashboard<\/strong> delivers benefits beyond compliance:<\/p>\n\n\n\n

                  \n
                • Performance improvements:<\/strong> Cleaner consent signals reduce broken attribution and improve the quality of conversion reporting under consent constraints.<\/li>\n
                • Cost savings:<\/strong> Fewer incidents, fewer rushed audits, and less rework from misconfigured tags and vendors.<\/li>\n
                • Operational efficiency:<\/strong> Centralized status and workflows reduce handoffs and duplicated tracking spreadsheets.<\/li>\n
                • Better customer experience:<\/strong> Clear controls and transparency reduce confusion and improve trust.<\/li>\n
                • Faster decision-making:<\/strong> Teams can evaluate tradeoffs (measurement vs privacy) with real data rather than assumptions.<\/li>\n<\/ul>\n\n\n\n

                  In modern Privacy & Consent<\/strong> programs, these benefits often compound: better governance leads to more stable measurement, which supports better marketing decisions.<\/p>\n\n\n\n

                  Challenges of Privacy Dashboard<\/h2>\n\n\n\n

                  A Privacy Dashboard can fail if it\u2019s treated as a cosmetic reporting layer rather than an operational system. Common challenges include:<\/p>\n\n\n\n

                    \n
                  • Data fragmentation:<\/strong> Consent signals and user identity may live in separate systems, making reconciliation difficult.<\/li>\n
                  • Inconsistent taxonomy:<\/strong> \u201cMarketing,\u201d \u201canalytics,\u201d and \u201cfunctional\u201d categories can be defined differently across vendors, breaking enforcement.<\/li>\n
                  • Implementation complexity:<\/strong> Tag managers, SDKs, server-side routing, and regional rules can create edge cases that are hard to test.<\/li>\n
                  • Overconfidence in metrics:<\/strong> A dashboard can show \u201chigh consent rate\u201d while still leaking data via undocumented tags or partner pixels.<\/li>\n
                  • Organizational misalignment:<\/strong> If marketing, legal, and engineering don\u2019t share definitions and ownership, the Privacy Dashboard becomes stale.<\/li>\n<\/ul>\n\n\n\n

                    These issues are normal growing pains in Privacy & Consent<\/strong> and should be addressed through governance and validation.<\/p>\n\n\n\n

                    Best Practices for Privacy Dashboard<\/h2>\n\n\n\n

                    To make a Privacy Dashboard<\/strong> trustworthy and scalable:<\/p>\n\n\n\n

                      \n
                    1. \n

                      Define a consent and purpose taxonomy once<\/strong>\n Document what each category means, which tools it affects, and how it maps to regional requirements. Consistency is foundational to Privacy & Consent<\/strong> accuracy.<\/p>\n<\/li>\n

                    2. \n

                      Build evidence, not just visuals<\/strong>\n Keep logs of consent changes, vendor approvals, request completion, and configuration updates. Audits require proof, not charts.<\/p>\n<\/li>\n

                    3. \n

                      Validate with real-world testing<\/strong>\n Test by region, device, browser, and user state (anonymous vs logged-in). Confirm tags do not fire before consent where required.<\/p>\n<\/li>\n

                    4. \n

                      Use role-based views<\/strong>\n Executives need risk and trends; marketers need measurement impact; developers need diagnostics. A single cluttered dashboard helps no one.<\/p>\n<\/li>\n

                    5. \n

                      Operationalize alerts<\/strong>\n Create triggers for anomalies: sudden consent-rate shifts, new tags detected, vendor endpoints changing, backlog growth in user requests.<\/p>\n<\/li>\n

                    6. \n

                      Review vendors and tags continuously<\/strong>\n Treat privacy governance like security: a continuous discipline within Privacy & Consent<\/strong>, not a quarterly checkbox.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                      Tools Used for Privacy Dashboard<\/h2>\n\n\n\n

                      A Privacy Dashboard<\/strong> typically pulls from multiple tool categories rather than relying on a single platform:<\/p>\n\n\n\n

                        \n
                      • Consent and preference management systems:<\/strong> Store consent status, categories, and user choices; provide interfaces for consent capture and updates.<\/li>\n
                      • Tag management and SDK management:<\/strong> Control which scripts or events run and when; crucial for enforcing consent-aware data collection.<\/li>\n
                      • Analytics tools:<\/strong> Measure traffic and conversions; provide diagnostics when consent changes affect data volume.<\/li>\n
                      • CRM and customer data systems:<\/strong> Store customer profiles and communication preferences; support lawful preference enforcement.<\/li>\n
                      • Data governance and inventory systems:<\/strong> Track where personal data exists and how it is processed; helpful for internal Privacy Dashboard completeness.<\/li>\n
                      • Reporting dashboards and BI tools:<\/strong> Combine privacy, marketing, and operational metrics into stakeholder-friendly views.<\/li>\n
                      • Ticketing and workflow systems:<\/strong> Manage privacy request queues and approvals; track SLAs and outcomes.<\/li>\n<\/ul>\n\n\n\n

                        In Privacy & Consent<\/strong> practice, the \u201cdashboard\u201d is often a carefully governed layer across these systems.<\/p>\n\n\n\n

                        Metrics Related to Privacy Dashboard<\/h2>\n\n\n\n

                        Metrics should reflect both compliance health and marketing impact. Common indicators include:<\/p>\n\n\n\n

                          \n
                        • Consent rate by category:<\/strong> Opt-in\/opt-out rates for analytics and marketing purposes (segmented by region, device, source).<\/li>\n
                        • Consent signal integrity:<\/strong> Percentage of sessions\/events with valid consent state attached; mismatch rate between banner choice and downstream tracking behavior.<\/li>\n
                        • Tag and vendor compliance coverage:<\/strong> Number of tags detected vs documented; percentage of vendors mapped to an approved purpose.<\/li>\n
                        • Privacy request SLA performance:<\/strong> Time to complete access\/deletion\/correction requests; backlog size; reopen rate.<\/li>\n
                        • Data minimization indicators:<\/strong> Reduction in unnecessary data collection points; fewer unapproved events or parameters.<\/li>\n
                        • Measurement impact metrics:<\/strong> Changes in attributable conversions, modeled vs observed conversions (where applicable), and data completeness trends after consent changes.<\/li>\n
                        • Incident and exception counts:<\/strong> Number of privacy-related incidents, exceptions granted, and unresolved risks.<\/li>\n<\/ul>\n\n\n\n

                          A Privacy Dashboard becomes more valuable as these metrics are tied to decision-making, not just reporting.<\/p>\n\n\n\n

                          Future Trends of Privacy Dashboard<\/h2>\n\n\n\n

                          The Privacy Dashboard<\/strong> is evolving alongside shifts in measurement and regulation within Privacy & Consent<\/strong>:<\/p>\n\n\n\n

                            \n
                          • More automation:<\/strong> Expect automated tag discovery, vendor classification, and policy enforcement checks to reduce manual audits.<\/li>\n
                          • AI-assisted governance (with care):<\/strong> AI can help summarize data flows or detect anomalies, but outputs must be reviewed to avoid false assurance in Privacy & Consent<\/strong> decisions.<\/li>\n
                          • Privacy-preserving measurement:<\/strong> Greater reliance on aggregated reporting, modeled conversions, and on-device or server-side processing patterns will influence what a Privacy Dashboard needs to track.<\/li>\n
                          • Identity and preference unification:<\/strong> Organizations will increasingly link consent and preferences across devices and channels\u2014requiring stronger governance and clearer user experiences.<\/li>\n
                          • Continuous compliance:<\/strong> \u201cAlways audit-ready\u201d becomes the goal; dashboards will emphasize evidence logs, change history, and automated controls.<\/li>\n<\/ul>\n\n\n\n

                            Privacy Dashboard vs Related Terms<\/h2>\n\n\n\n

                            Privacy Dashboard vs Preference Center<\/h3>\n\n\n\n

                            A preference center<\/strong> usually focuses on communication choices (email frequency, topics) and sometimes marketing consent. A Privacy Dashboard<\/strong> is broader: it can include data rights requests, vendor transparency, consent status across purposes, and internal compliance operations.<\/p>\n\n\n\n

                            Privacy Dashboard vs Consent Management Platform<\/h3>\n\n\n\n

                            A consent management platform primarily captures and stores consent and controls firing of tags based on choices. A Privacy Dashboard<\/strong> may include CMP data, but it also unifies reporting, workflows, audits, and cross-system visibility\u2014often spanning the full Privacy & Consent<\/strong> program.<\/p>\n\n\n\n

                            Privacy Dashboard vs Data Inventory (ROPA)<\/h3>\n\n\n\n

                            A data inventory (often used for records of processing activities) documents what data exists and why. A Privacy Dashboard<\/strong> is more operational and time-sensitive: it monitors live signals (consent integrity, request queues, tag behavior) and supports day-to-day Privacy & Consent<\/strong> execution.<\/p>\n\n\n\n

                            Who Should Learn Privacy Dashboard<\/h2>\n\n\n\n
                              \n
                            • Marketers:<\/strong> To understand how consent affects attribution, audiences, and campaign performance\u2014and how to design privacy-respecting growth.<\/li>\n
                            • Analysts:<\/strong> To interpret data correctly when consent changes alter tracking, and to monitor data quality in Privacy & Consent<\/strong> contexts.<\/li>\n
                            • Agencies:<\/strong> To implement tags and measurement responsibly, advise clients on compliance-aware tracking, and avoid preventable data loss.<\/li>\n
                            • Business owners and founders:<\/strong> To balance growth with trust, reduce risk, and meet enterprise customer requirements tied to Privacy & Consent<\/strong>.<\/li>\n
                            • Developers:<\/strong> To implement consent-aware tracking, preference storage, and request fulfillment systems that the Privacy Dashboard depends on.<\/li>\n<\/ul>\n\n\n\n

                              Summary of Privacy Dashboard<\/h2>\n\n\n\n

                              A Privacy Dashboard<\/strong> is a centralized way to monitor and manage privacy status, consent choices, data flows, and privacy operations. It matters because it improves visibility, reduces risk, and stabilizes measurement\u2014turning Privacy & Consent<\/strong> from a policy into a functioning system. In a mature Privacy & Consent<\/strong> program, the Privacy Dashboard supports governance, enforcement, evidence collection, and better experiences for both customers and internal teams.<\/p>\n\n\n\n

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

                              1) What is a Privacy Dashboard used for?<\/h3>\n\n\n\n

                              A Privacy Dashboard is used to consolidate privacy and consent signals, track compliance operations (like deletion requests), and provide actionable visibility into how data is collected and shared.<\/p>\n\n\n\n

                              2) Is a Privacy Dashboard customer-facing or internal?<\/h3>\n\n\n\n

                              It can be either. Many organizations offer a customer-facing Privacy Dashboard for preference and rights controls, while running an internal Privacy Dashboard for audits, workflows, and enforcement monitoring.<\/p>\n\n\n\n

                              3) How does Privacy & Consent affect marketing measurement in a Privacy Dashboard?<\/h3>\n\n\n\n

                              Privacy & Consent choices can limit which events are collected and how they\u2019re attributed. A Privacy Dashboard helps teams see where measurement drops are expected (because of opt-outs) versus where implementation is broken (because consent signals aren\u2019t applied correctly).<\/p>\n\n\n\n

                              4) What should be included in a Privacy Dashboard for a website?<\/h3>\n\n\n\n

                              At minimum: consent rates by category, tag\/vendor lists with purpose mapping, consent signal integrity checks, region\/device segmentation, and an audit log of configuration changes.<\/p>\n\n\n\n

                              5) Can a Privacy Dashboard prevent non-compliant tracking?<\/h3>\n\n\n\n

                              It can help prevent it when paired with enforcement mechanisms (tag controls, SDK rules, server-side routing policies). The dashboard alone doesn\u2019t block tracking unless it\u2019s integrated with execution controls.<\/p>\n\n\n\n

                              6) How often should a Privacy Dashboard be reviewed?<\/h3>\n\n\n\n

                              Key operational metrics should be monitored continuously or weekly (alerts help), while deeper vendor and implementation reviews are commonly monthly or quarterly\u2014depending on traffic volume and change frequency.<\/p>\n\n\n\n

                              7) What\u2019s the biggest mistake teams make with a Privacy Dashboard?<\/h3>\n\n\n\n

                              Treating it as static reporting. The most effective Privacy Dashboard is connected to governance, testing, and enforcement, so it stays accurate as campaigns, vendors, and regulations change.<\/p>\n","protected":false},"excerpt":{"rendered":"

                              A **Privacy Dashboard** is a centralized view that helps an organization understand, manage, and prove how it handles personal data, user choices, and compliance obligations. In **Privacy & Consent** work, it acts like an operational command center: it brings together signals from consent collection, tracking technologies, data flows, and user requests so teams can make decisions confidently and quickly.<\/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":[1916],"tags":[],"class_list":["post-11602","post","type-post","status-publish","format-standard","hentry","category-privacy-consent"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/11602","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=11602"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/11602\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=11602"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=11602"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=11602"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}