{"id":11517,"date":"2026-04-02T01:06:07","date_gmt":"2026-04-02T01:06:07","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/consent-receipt\/"},"modified":"2026-04-02T01:06:07","modified_gmt":"2026-04-02T01:06:07","slug":"consent-receipt","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/consent-receipt\/","title":{"rendered":"Consent Receipt: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Privacy & Consent"},"content":{"rendered":"\n

A Consent Receipt<\/strong> is a durable, shareable record that captures what a person agreed to, when they agreed, how they agreed, and what that consent allows a business to do with their data. In Privacy & Consent<\/strong> work, it functions like a transaction confirmation: it makes consent auditable, portable, and easier to prove if questions arise later.<\/p>\n\n\n\n

Why it matters now: modern marketing depends on first-party data, personalized experiences, and multi-channel measurement\u2014all under tighter expectations from regulators, browsers, and customers. A well-designed Consent Receipt<\/strong> helps turn Privacy & Consent<\/strong> from a risky checkbox activity into an operational capability: transparent to users, reliable for teams, and defensible for audits.<\/p>\n\n\n\n

What Is Consent Receipt?<\/h2>\n\n\n\n

A Consent Receipt<\/strong> is a structured record provided to a user (and stored by the organization) that documents the details of a consent action. It is not \u201cthe consent\u201d itself; it is the evidence and description of the consent event and its scope.<\/p>\n\n\n\n

At its core, the concept is simple: when a person opts in (or opts out), the business should be able to show:<\/p>\n\n\n\n

    \n
  • What<\/strong> they agreed to (purposes, channels, data uses)<\/li>\n
  • Who<\/strong> collected it (the organization, product, or domain)<\/li>\n
  • When and where<\/strong> it happened (timestamp, context, property\/app)<\/li>\n
  • How<\/strong> it was captured (UI, checkbox, API, call recording reference)<\/li>\n
  • What the terms were<\/strong> at that moment (policy\/version, language)<\/li>\n<\/ul>\n\n\n\n

    From a business perspective, a Consent Receipt<\/strong> reduces ambiguity. Marketing, analytics, support, and engineering can all reference the same source of truth, which strengthens governance in Privacy & Consent<\/strong> and prevents inconsistent interpretations across tools and teams.<\/p>\n\n\n\n

    Within Privacy & Consent<\/strong>, a Consent Receipt<\/strong> sits alongside preference management, data mapping, and retention controls. It supports the \u201cprove it\u201d requirement\u2014being able to demonstrate that consent was informed, specific, and recorded in a way that can be audited.<\/p>\n\n\n\n

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

    A Consent Receipt<\/strong> is strategically important because consent is no longer a one-time legal event; it\u2019s an ongoing relationship signal. People change preferences, laws change expectations, and your marketing stack changes frequently.<\/p>\n\n\n\n

    Key business value points:<\/p>\n\n\n\n

      \n
    • Risk reduction:<\/strong> If a complaint, audit, or internal review happens, a Consent Receipt<\/strong> helps show the precise scope and timing of permission.<\/li>\n
    • Operational clarity:<\/strong> Teams stop guessing which list is \u201csafe\u201d or which audience can be targeted. That reduces accidental overreach and improves Privacy & Consent<\/strong> alignment.<\/li>\n
    • Better marketing outcomes:<\/strong> When consent status is trustworthy, segmentation becomes cleaner (fewer suppressed-by-mistake records, fewer unintentional sends), which can improve deliverability and engagement.<\/li>\n
    • Competitive advantage:<\/strong> Transparent consent practices build trust. In crowded markets, trust affects signups, opt-in rates, and willingness to share first-party data.<\/li>\n<\/ul>\n\n\n\n

      In short, a Consent Receipt<\/strong> supports both compliance posture and performance\u2014two goals that often conflict without strong Privacy & Consent<\/strong> foundations.<\/p>\n\n\n\n

      How Consent Receipt Works<\/h2>\n\n\n\n

      A Consent Receipt<\/strong> is more practical than theoretical. In real implementations, it follows a repeatable workflow that connects user choices to downstream systems.<\/p>\n\n\n\n

        \n
      1. \n

        Input or trigger (consent event)<\/strong>\n – A user checks a marketing opt-in box, accepts analytics cookies, agrees to SMS messaging, or sets preferences in an account portal.\n – The event may occur on web, app, point-of-sale, phone, or via an embedded form.<\/p>\n<\/li>\n

      2. \n

        Processing (interpretation and validation)<\/strong>\n – The system determines what the action means: which purposes, channels, and legal bases apply.\n – It associates the event with an identifier (account ID, hashed email, device ID, consent string, or session reference).\n – It records context: UI language, geo\/jurisdiction logic, and policy\/version shown.<\/p>\n<\/li>\n

      3. \n

        Execution (apply permissions)<\/strong>\n – The consent state is written to a central store or propagated to tools (CRM, email platform, analytics tags, CDP).\n – Suppression rules, tag firing rules, and audience eligibility update based on the new consent state.<\/p>\n<\/li>\n

      4. \n

        Output (receipt and audit trail)<\/strong>\n – A Consent Receipt<\/strong> is generated and made accessible (e.g., emailed confirmation, downloadable receipt in an account area, or available upon request).\n – The business stores an immutable or tamper-evident log for audits and troubleshooting\u2014critical for Privacy & Consent<\/strong> governance.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        Key Components of Consent Receipt<\/h2>\n\n\n\n

        A useful Consent Receipt<\/strong> is consistent, complete, and traceable across systems. The components usually span data, process, and ownership.<\/p>\n\n\n\n

        Core data elements<\/h3>\n\n\n\n
          \n
        • Data subject identifier:<\/strong> user ID, customer ID, or other stable reference (avoid storing unnecessary identifiers).<\/li>\n
        • Timestamp and time zone:<\/strong> when consent was captured and, if relevant, when it expires.<\/li>\n
        • Collector identity:<\/strong> organization name, brand, app\/site, and sometimes the specific form or endpoint.<\/li>\n
        • Purposes and permissions:<\/strong> analytics, personalization, email marketing, SMS, third-party sharing, etc.<\/li>\n
        • Status and action:<\/strong> opt-in, opt-out, granular toggles, or \u201cdo not sell\/share\u201d style preferences depending on regime.<\/li>\n
        • Policy or notice version:<\/strong> which privacy notice\/terms were presented at the time.<\/li>\n
        • Method and provenance:<\/strong> checkbox, double opt-in confirmation, in-app prompt, signed document reference, call center workflow ID.<\/li>\n<\/ul>\n\n\n\n

          Systems and processes<\/h3>\n\n\n\n
            \n
          • Consent store or registry:<\/strong> a database or service that acts as the system of record.<\/li>\n
          • Propagation layer:<\/strong> integrations that synchronize consent status into marketing tools.<\/li>\n
          • Change history:<\/strong> an append-only timeline of updates rather than a single overwritten value.<\/li>\n<\/ul>\n\n\n\n

            Governance and team responsibilities<\/h3>\n\n\n\n
              \n
            • Marketing defines use cases and channels.<\/li>\n
            • Legal\/privacy sets minimum requirements and retention expectations within Privacy & Consent<\/strong>.<\/li>\n
            • Engineering implements capture, storage, and access controls.<\/li>\n
            • Analytics ensures event integrity and reporting consistency.<\/li>\n<\/ul>\n\n\n\n

              Types of Consent Receipt<\/h2>\n\n\n\n

              There isn\u2019t one universal \u201ctype system,\u201d but in practice Consent Receipt<\/strong> approaches vary by context and how the receipt is delivered.<\/p>\n\n\n\n

              By consent context<\/h3>\n\n\n\n
                \n
              • Marketing communications consent:<\/strong> email, SMS, push notifications, phone calls.<\/li>\n
              • Cookie and tracking consent:<\/strong> analytics tags, advertising pixels, personalization cookies.<\/li>\n
              • Account and product consent:<\/strong> feature-level permissions, data sharing between services.<\/li>\n
              • Offline consent:<\/strong> event registrations, in-store forms, call center opt-ins.<\/li>\n<\/ul>\n\n\n\n

                By delivery format<\/h3>\n\n\n\n
                  \n
                • User-visible receipts:<\/strong> emailed confirmation, account portal history, or downloadable summary.<\/li>\n
                • Machine-readable receipts:<\/strong> structured payloads stored in systems for automation and audits (often with standardized fields).<\/li>\n<\/ul>\n\n\n\n

                  By granularity<\/h3>\n\n\n\n
                    \n
                  • Purpose-based:<\/strong> \u201canalytics,\u201d \u201cpersonalization,\u201d \u201cmarketing.\u201d<\/li>\n
                  • Channel-based:<\/strong> email vs SMS vs push.<\/li>\n
                  • Vendor\/partner-based:<\/strong> consent scoped to specific third parties when required.<\/li>\n<\/ul>\n\n\n\n

                    These distinctions matter because Privacy & Consent<\/strong> obligations and user expectations differ widely between \u201csend me the newsletter\u201d and \u201callow cross-site advertising measurement.\u201d<\/p>\n\n\n\n

                    Real-World Examples of Consent Receipt<\/h2>\n\n\n\n

                    Example 1: Newsletter sign-up with double opt-in<\/h3>\n\n\n\n

                    A SaaS company uses a form to collect email subscriptions. After submission, the user confirms via a second email (double opt-in). The Consent Receipt<\/strong> includes the original sign-up timestamp, confirmation timestamp, form identifier, and the exact subscription purpose. This helps the marketing team defend deliverability complaints and proves permission in Privacy & Consent<\/strong> reviews.<\/p>\n\n\n\n

                    Example 2: Cookie banner with granular tracking choices<\/h3>\n\n\n\n

                    An ecommerce site offers toggles for analytics and advertising. When a user accepts analytics but rejects advertising, the site stores a Consent Receipt<\/strong> capturing those purpose-level choices plus banner version and jurisdiction logic. The analytics team can trust reporting tags fire appropriately, and the ad team avoids building audiences from users who did not agree\u2014tightening Privacy & Consent<\/strong> compliance and improving data quality.<\/p>\n\n\n\n

                    Example 3: Event lead capture synced to CRM and email platform<\/h3>\n\n\n\n

                    At a conference booth, attendees scan a QR code to request a demo and opt into follow-up emails. The Consent Receipt<\/strong> records the event name, location, and the specific statement shown at capture. When leads flow into CRM, the receipt data travels with them, preventing mismatched assumptions across sales and marketing\u2014especially important in distributed Privacy & Consent<\/strong> operations.<\/p>\n\n\n\n

                    Benefits of Using Consent Receipt<\/h2>\n\n\n\n

                    A strong Consent Receipt<\/strong> program delivers measurable advantages beyond compliance.<\/p>\n\n\n\n

                      \n
                    • Improved targeting hygiene:<\/strong> Cleaner segmentation reduces accidental outreach to non-consented audiences.<\/li>\n
                    • Higher trust and opt-in quality:<\/strong> Clear documentation and transparent receipts can reduce skepticism and increase willingness to share preferences.<\/li>\n
                    • Fewer internal disputes:<\/strong> Teams can resolve \u201ccan we use this data?\u201d questions faster with an authoritative record.<\/li>\n
                    • Audit readiness:<\/strong> Faster response to access requests, complaints, and policy reviews.<\/li>\n
                    • Lower waste:<\/strong> Avoid spending on campaigns that must later be suppressed due to uncertain consent status.<\/li>\n<\/ul>\n\n\n\n

                      In mature Privacy & Consent<\/strong> programs, these benefits compound because consent becomes a reliable attribute used across lifecycle marketing and analytics.<\/p>\n\n\n\n

                      Challenges of Consent Receipt<\/h2>\n\n\n\n

                      Implementing Consent Receipt<\/strong> well is not trivial, especially in complex marketing stacks.<\/p>\n\n\n\n

                        \n
                      • Identity complexity:<\/strong> Mapping consent to a person across devices, browsers, and logged-out states can be difficult without over-collecting data.<\/li>\n
                      • Versioning and change control:<\/strong> If your privacy notice, UI copy, or preference options change, receipts must preserve what was shown at that time.<\/li>\n
                      • Tool fragmentation:<\/strong> Consent captured in one platform may not propagate correctly to others, creating inconsistent enforcement.<\/li>\n
                      • Jurisdiction logic:<\/strong> Requirements vary by region and purpose, and the receipt must reflect the right context without guessing.<\/li>\n
                      • Data minimization tension:<\/strong> Receipts need enough detail to be meaningful, but Privacy & Consent<\/strong> principles also push you to store less data.<\/li>\n<\/ul>\n\n\n\n

                        These challenges are solvable, but they require coordinated design across privacy, marketing operations, and engineering.<\/p>\n\n\n\n

                        Best Practices for Consent Receipt<\/h2>\n\n\n\n

                        Use these practical guidelines to make Consent Receipt<\/strong> both user-friendly and operationally reliable.<\/p>\n\n\n\n

                          \n
                        1. \n

                          Design for clarity first<\/strong>\n – Use plain language: what will happen, how often, and through which channels.\n – Avoid bundling unrelated purposes into a single \u201cagree\u201d action.<\/p>\n<\/li>\n

                        2. \n

                          Capture context, not just a checkbox<\/strong>\n – Store the purpose(s), the UI text version, and the policy\/notice version.\n – Record the capture source (form ID, app screen, call center flow).<\/p>\n<\/li>\n

                        3. \n

                          Centralize consent as a system of record<\/strong>\n – Maintain a single consent registry that other tools subscribe to.\n – Use an append-only change history to preserve prior states.<\/p>\n<\/li>\n

                        4. \n

                          Make it accessible to users<\/strong>\n – Provide a preference center or account page where users can view and change choices.\n – When appropriate, provide a user-facing Consent Receipt<\/strong> summary for transparency in Privacy & Consent<\/strong>.<\/p>\n<\/li>\n

                        5. \n

                          Enforce downstream<\/strong>\n – Ensure consent states control tag firing, audience building, and message sending.\n – Add automated tests or monitoring to catch regressions after website releases.<\/p>\n<\/li>\n

                        6. \n

                          Set retention and deletion rules<\/strong>\n – Keep receipts only as long as needed for operational and legal purposes.\n – Align retention with your broader Privacy & Consent<\/strong> policy and data lifecycle program.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                          Tools Used for Consent Receipt<\/h2>\n\n\n\n

                          A Consent Receipt<\/strong> is enabled by a toolkit rather than a single product category. Common tool groups include:<\/p>\n\n\n\n

                            \n
                          • Consent management platforms (CMPs):<\/strong> capture cookie and tracking choices, store consent signals, and manage banner experiences.<\/li>\n
                          • CRM systems:<\/strong> store contact-level marketing permissions and maintain communication history.<\/li>\n
                          • Marketing automation and email\/SMS platforms:<\/strong> enforce subscription status, double opt-in flows, and suppression logic.<\/li>\n
                          • Analytics tools and tag management systems:<\/strong> conditionally fire events\/tags based on consent states and document implementation changes.<\/li>\n
                          • Customer data platforms (CDPs) or data pipelines:<\/strong> unify consent attributes and propagate them to downstream destinations.<\/li>\n
                          • Reporting dashboards and data warehouses:<\/strong> consolidate consent metrics, audit trails, and operational monitoring for Privacy & Consent<\/strong> stakeholders.<\/li>\n
                          • Ticketing and governance workflows:<\/strong> manage requests, approvals, and evidence gathering during audits or investigations.<\/li>\n<\/ul>\n\n\n\n

                            The goal is interoperability: the Consent Receipt<\/strong> details should be consistent as they move across the stack.<\/p>\n\n\n\n

                            Metrics Related to Consent Receipt<\/h2>\n\n\n\n

                            Because Consent Receipt<\/strong> affects both compliance and marketing performance, track a mix of operational, experience, and business metrics.<\/p>\n\n\n\n

                            Consent quality and coverage<\/h3>\n\n\n\n
                              \n
                            • Opt-in rate by channel and purpose<\/strong><\/li>\n
                            • Granular choice distribution<\/strong> (e.g., analytics-only vs analytics + marketing)<\/li>\n
                            • Double opt-in completion rate<\/strong> (where used)<\/li>\n
                            • Consent refresh rate<\/strong> (users updating preferences over time)<\/li>\n<\/ul>\n\n\n\n

                              Operational integrity<\/h3>\n\n\n\n
                                \n
                              • Propagation latency:<\/strong> time for consent changes to reach all systems<\/li>\n
                              • Mismatch rate:<\/strong> contacts with conflicting consent statuses across tools<\/li>\n
                              • Tag firing compliance rate:<\/strong> percentage of sessions where tags respected consent state<\/li>\n<\/ul>\n\n\n\n

                                Business impact<\/h3>\n\n\n\n
                                  \n
                                • List growth quality:<\/strong> engagement rates of newly consented subscribers<\/li>\n
                                • Deliverability indicators:<\/strong> complaint rates and unsubscribe rates<\/li>\n
                                • Attribution coverage changes:<\/strong> how consent affects measurable conversions (interpreted carefully)<\/li>\n<\/ul>\n\n\n\n

                                  In strong Privacy & Consent<\/strong> programs, these metrics guide UX improvements and prevent quiet failures (like sending to suppressed audiences).<\/p>\n\n\n\n

                                  Future Trends of Consent Receipt<\/h2>\n\n\n\n

                                  Several trends are shaping how Consent Receipt<\/strong> evolves within Privacy & Consent<\/strong>:<\/p>\n\n\n\n

                                    \n
                                  • More automation and policy-aware enforcement:<\/strong> consent rules applied automatically across tags, audiences, and downstream exports.<\/li>\n
                                  • Greater granularity and preference experiences:<\/strong> users expect fine control, not binary yes\/no, especially across devices and channels.<\/li>\n
                                  • AI-assisted governance:<\/strong> AI can help detect inconsistent consent states, unexpected data flows, or risky audience definitions\u2014without replacing human oversight.<\/li>\n
                                  • Privacy-preserving measurement:<\/strong> as third-party tracking declines, organizations will rely more on first-party data and modeled measurement, making accurate receipts and consent states more valuable.<\/li>\n
                                  • Standardized logging and portability expectations:<\/strong> users and regulators increasingly expect traceability; a robust Consent Receipt<\/strong> helps meet those expectations consistently.<\/li>\n<\/ul>\n\n\n\n

                                    The direction is clear: Privacy & Consent<\/strong> is becoming an engineering and operations discipline, and Consent Receipt<\/strong> is a foundational artifact.<\/p>\n\n\n\n

                                    Consent Receipt vs Related Terms<\/h2>\n\n\n\n

                                    Understanding adjacent concepts helps teams implement the right thing.<\/p>\n\n\n\n

                                    Consent Receipt vs consent record<\/h3>\n\n\n\n

                                    A consent record is the internal stored data that indicates a person\u2019s current consent state (and often history). A Consent Receipt<\/strong> is the documented, shareable representation of the consent event details\u2014often user-facing or designed to be produced on demand.<\/p>\n\n\n\n

                                    Consent Receipt vs audit trail<\/h3>\n\n\n\n

                                    An audit trail is a broader log of system actions (who changed what, when, and sometimes why). A Consent Receipt<\/strong> focuses specifically on consent capture and its context. In practice, the receipt may be generated from an audit trail entry plus policy\/version metadata.<\/p>\n\n\n\n

                                    Consent Receipt vs preference center<\/h3>\n\n\n\n

                                    A preference center is the interface where users manage choices. A Consent Receipt<\/strong> is the proof and summary of what choices were made. The preference center is the control panel; the receipt is the confirmation and evidence, both important in Privacy & Consent<\/strong> operations.<\/p>\n\n\n\n

                                    Who Should Learn Consent Receipt<\/h2>\n\n\n\n
                                      \n
                                    • Marketers:<\/strong> to run campaigns confidently, improve opt-in UX, and avoid sending messages outside permission.<\/li>\n
                                    • Analysts:<\/strong> to interpret data correctly when consent affects tracking coverage, attribution, and cohort definitions.<\/li>\n
                                    • Agencies:<\/strong> to design compliant acquisition flows, audits, and measurement plans across clients with different stacks.<\/li>\n
                                    • Business owners and founders:<\/strong> to reduce risk while maintaining growth, especially when scaling internationally.<\/li>\n
                                    • Developers and product teams:<\/strong> to implement reliable consent capture, versioning, and propagation\u2014core to modern Privacy & Consent<\/strong> engineering.<\/li>\n<\/ul>\n\n\n\n

                                      Summary of Consent Receipt<\/h2>\n\n\n\n

                                      A Consent Receipt<\/strong> is a structured record of a user\u2019s consent decision\u2014what they agreed to, when, how, and under which terms. It matters because it strengthens trust, reduces compliance risk, and improves operational clarity for marketing and analytics. In Privacy & Consent<\/strong>, it acts as evidence and a coordination mechanism across tools, teams, and channels. Done well, it supports reliable permission-based marketing and consistent Privacy & Consent<\/strong> governance at scale.<\/p>\n\n\n\n

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

                                      What should a Consent Receipt include at minimum?<\/h3>\n\n\n\n

                                      At minimum, include the user identifier (or reference), timestamp, purposes\/channels consented to, the capture source\/context, and the privacy notice or policy version shown at the time.<\/p>\n\n\n\n

                                      Is a Consent Receipt legally required everywhere?<\/h3>\n\n\n\n

                                      Not everywhere in the same way. Requirements vary by jurisdiction and use case. Even when not explicitly required, a Consent Receipt<\/strong> is a strong best practice for Privacy & Consent<\/strong> accountability and dispute resolution.<\/p>\n\n\n\n

                                      How is Consent Receipt different from simply storing \u201copted in = true\u201d?<\/h3>\n\n\n\n

                                      A boolean doesn\u2019t capture scope, context, or proof. A Consent Receipt<\/strong> documents what the user consented to (specific purposes\/channels), plus when and how it happened, which is essential for audits and internal governance.<\/p>\n\n\n\n

                                      Where should we store Consent Receipt data in our stack?<\/h3>\n\n\n\n

                                      Store it in a central consent registry or system of record, then propagate the current consent status to downstream tools (CRM, marketing automation, analytics\/tag management). Keep a change history so prior states are not lost.<\/p>\n\n\n\n

                                      How does Privacy & Consent affect marketing attribution and analytics when receipts are used?<\/h3>\n\n\n\n

                                      Consent choices can reduce tracking coverage, which changes attribution inputs. Receipts help analysts understand which users were eligible for tracking and why, making Privacy & Consent<\/strong> impacts measurable and explainable.<\/p>\n\n\n\n

                                      Should we email a Consent Receipt to every subscriber?<\/h3>\n\n\n\n

                                      It depends on your channel and UX strategy. For some programs (like double opt-in email), it\u2019s natural to provide confirmation. For others (like cookie choices), an account page or downloadable record may be more appropriate.<\/p>\n\n\n\n

                                      What happens when a user withdraws consent?<\/h3>\n\n\n\n

                                      You should generate an updated Consent Receipt<\/strong> (or receipt entry) showing the withdrawal event, apply suppression immediately, and propagate changes to all relevant tools\u2014an essential operational step in Privacy & Consent<\/strong> management.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                      A **Consent Receipt** is a durable, shareable record that captures what a person agreed to, when they agreed, how they agreed, and what that consent allows a business to do with their data. In **Privacy & Consent** work, it functions like a transaction confirmation: it makes consent auditable, portable, and easier to prove if questions arise later.<\/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-11517","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\/11517","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=11517"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/11517\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=11517"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=11517"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=11517"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}