{"id":11534,"date":"2026-04-02T01:43:07","date_gmt":"2026-04-02T01:43:07","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/do-not-sell\/"},"modified":"2026-04-02T01:43:07","modified_gmt":"2026-04-02T01:43:07","slug":"do-not-sell","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/do-not-sell\/","title":{"rendered":"Do Not Sell: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Privacy & Consent"},"content":{"rendered":"\n

\u201cDo Not Sell\u201d is a consumer choice signal that tells a business not to sell (and, in many real-world implementations, not to share) a person\u2019s personal information with third parties in ways that trigger privacy obligations. In Privacy & Consent<\/strong> programs, \u201cDo Not Sell\u201d is less about a single button on a website and more about a durable operational promise: the individual\u2019s data must not be routed into data flows that constitute a sale under applicable rules.<\/p>\n\n\n\n

For modern digital marketing, \u201cDo Not Sell\u201d matters because much of the ad ecosystem depends on transferring identifiers and behavioral data to partners. Strong Privacy & Consent<\/strong> strategy requires honoring \u201cDo Not Sell\u201d preferences consistently across websites, apps, analytics, ad platforms, and customer databases\u2014without breaking measurement, personalization, or campaign performance.<\/p>\n\n\n\n

What Is Do Not Sell?<\/h2>\n\n\n\n

\u201cDo Not Sell\u201d is an opt-out choice that allows individuals to restrict a business from selling their personal information to third parties. Practically, it\u2019s a boundary around data disclosure: if a user opts out, the company must stop certain transfers of personal data that qualify as a \u201csale\u201d under relevant privacy frameworks.<\/p>\n\n\n\n

The core concept is control. \u201cDo Not Sell\u201d gives people a say in whether their data can be exchanged for value\u2014money, services, enhanced targeting, or other benefits. It sits squarely inside Privacy & Consent<\/strong> because it is a user preference that changes what data processing is allowed.<\/p>\n\n\n\n

From a business perspective, \u201cDo Not Sell\u201d influences how you run advertising, measurement, and partner integrations. It affects contracts, tagging strategy, and which identifiers can be shared. Within Privacy & Consent<\/strong> operations, it typically lives alongside consent management, preference centers, and data governance policies.<\/p>\n\n\n\n

Why Do Not Sell Matters in Privacy & Consent<\/h2>\n\n\n\n

\u201cDo Not Sell\u201d is strategically important because it connects legal obligations with marketing execution. If you treat it as a legal checkbox, you risk building data pipelines that quietly violate your own promise. If you treat it as a first-class Privacy & Consent<\/strong> requirement, you can reduce risk while still running effective campaigns.<\/p>\n\n\n\n

Business value shows up in several ways:<\/p>\n\n\n\n

    \n
  • Trust and brand resilience:<\/strong> Clear, honored choices reduce customer frustration and complaints.<\/li>\n
  • Operational clarity:<\/strong> Teams know what data can be activated and what must be restricted.<\/li>\n
  • Better partner discipline:<\/strong> \u201cDo Not Sell\u201d pushes vendors and agencies toward cleaner data handling.<\/li>\n
  • Reduced rework:<\/strong> Fixing tag and data flows after the fact is far more expensive than designing for Privacy & Consent<\/strong> upfront.<\/li>\n<\/ul>\n\n\n\n

    Marketing outcomes can improve as well. When preference signals are respected, engagement and opt-in rates for other channels (email, SMS, loyalty) often become more stable because users feel in control\u2014an indirect but real competitive advantage.<\/p>\n\n\n\n

    How Do Not Sell Works<\/h2>\n\n\n\n

    \u201cDo Not Sell\u201d is conceptual, but it becomes practical when you translate it into a workflow that your marketing stack can enforce.<\/p>\n\n\n\n

      \n
    1. \n

      Input \/ trigger<\/strong>\n The user submits a \u201cDo Not Sell\u201d request via a footer link, a privacy preference center, an in-app setting, or a recognized signal (such as a browser-based preference signal, where applicable). The request may be user-authenticated or device\/browser-specific depending on your system design.<\/p>\n<\/li>\n

    2. \n

      Analysis \/ decisioning<\/strong>\n Your organization determines what the request applies to: which identifiers, which properties (web\/app), which data categories, and which downstream \u201csale-like\u201d disclosures. This is where Privacy & Consent<\/strong> meets data mapping: you must know which tags, SDKs, APIs, and exports involve third parties.<\/p>\n<\/li>\n

    3. \n

      Execution \/ enforcement<\/strong>\n Systems apply the preference across:\n – Tag firing rules (block or alter third-party calls)\n – Data sharing settings in ad and analytics integrations\n – Vendor routing (e.g., suppress exports to certain partners)\n – Internal use rules (e.g., limit audience syncing)<\/p>\n<\/li>\n

    4. \n

      Output \/ outcome<\/strong>\n The user\u2019s data is no longer disclosed in ways that constitute \u201cselling.\u201d The business retains proof of the preference, can demonstrate enforcement, and updates reporting to reflect reduced third-party sharing. A mature Privacy & Consent<\/strong> program also confirms the change is persistent and auditable.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      Key Components of Do Not Sell<\/h2>\n\n\n\n

      A strong \u201cDo Not Sell\u201d program is built from coordinated components\u2014not a single page link.<\/p>\n\n\n\n

      Data inventory and mapping<\/h3>\n\n\n\n

      You need a living map of:\n– Data collected (events, identifiers, attributes)\n– Collection points (web, app, offline)\n– Destinations (analytics, ad platforms, CRM, vendors)\n– Purposes (measurement, targeting, personalization)<\/p>\n\n\n\n

      This is foundational to Privacy & Consent<\/strong> because you can\u2019t restrict a \u201csale\u201d if you don\u2019t know where disclosures occur.<\/p>\n\n\n\n

      Preference capture and storage<\/h3>\n\n\n\n

      \u201cDo Not Sell\u201d choices should be stored in a reliable system of record:\n– Preference center database\n– Consent\/preference management layer\n– CRM profile fields (with careful scoping)<\/p>\n\n\n\n

      Tagging and integration controls<\/h3>\n\n\n\n

      Enforcement typically requires:\n– Tag management rules\n– SDK configuration (mobile)\n– Server-side routing decisions\n– Partner configuration (limited data use settings where applicable)<\/p>\n\n\n\n

      Governance and responsibilities<\/h3>\n\n\n\n

      Clear ownership prevents gaps:\n– Legal\/privacy interprets obligations and definitions\n– Marketing ops implements tag and platform settings\n– Data engineering enforces pipelines and exports\n– Analytics updates measurement plans\nThis cross-functional model is core to sustainable Privacy & Consent<\/strong>.<\/p>\n\n\n\n

      Types of Do Not Sell<\/h2>\n\n\n\n

      \u201cDo Not Sell\u201d does not have universal \u201ctypes\u201d like a marketing channel would, but there are meaningful distinctions in how it is implemented and scoped.<\/p>\n\n\n\n

      1) Identity scope: account-level vs device-level<\/h3>\n\n\n\n
        \n
      • Account-level:<\/strong> Applies across devices when a user is authenticated. Stronger user experience, but requires identity resolution.<\/li>\n
      • Device\/browser-level:<\/strong> Applies only to the browser or device where the preference was set. Easier technically, but can be less consistent.<\/li>\n<\/ul>\n\n\n\n

        2) Coverage scope: sale-only vs sale-and-share operationalization<\/h3>\n\n\n\n

        Some businesses implement \u201cDo Not Sell\u201d narrowly, while others treat it as \u201cdo not sell or share\u201d to address broader third-party ad disclosures. In Privacy & Consent<\/strong> practice, broader coverage often reduces ambiguity and lowers operational risk, but it must match your disclosures and policies.<\/p>\n\n\n\n

        3) Control scope: tag blocking vs data minimization<\/h3>\n\n\n\n
          \n
        • Blocking:<\/strong> Prevent third-party tags\/SDKs from firing.<\/li>\n
        • Minimization:<\/strong> Allow limited functionality but remove identifiers (e.g., no ad IDs, truncated IP, no cross-site identifiers).\nMature programs often use both, depending on the tool and purpose.<\/li>\n<\/ul>\n\n\n\n

          Real-World Examples of Do Not Sell<\/h2>\n\n\n\n

          Example 1: Retargeting suppression on an ecommerce site<\/h3>\n\n\n\n

          A retailer runs remarketing through multiple ad partners. When a user selects \u201cDo Not Sell,\u201d the site stops firing retargeting pixels and disables audience syncing that sends hashed identifiers to third parties. The result is fewer third-party disclosures while keeping first-party analytics intact. This is a classic Privacy & Consent<\/strong> scenario where marketing must adapt targeting strategy to honor \u201cDo Not Sell.\u201d<\/p>\n\n\n\n

          Example 2: Mobile app SDK governance<\/h3>\n\n\n\n

          A subscription app uses analytics and attribution SDKs. A \u201cDo Not Sell\u201d toggle in settings updates server-side configuration so the app does not share advertising identifiers and restricts certain partner SDK calls. The team also updates event schemas to avoid sending sensitive attributes. This ties \u201cDo Not Sell\u201d to Privacy & Consent<\/strong> engineering controls, not just UI.<\/p>\n\n\n\n

          Example 3: B2B lead gen with third-party enrichment<\/h3>\n\n\n\n

          A SaaS company enriches form leads using external data vendors. If a user opts into a \u201cDo Not Sell\u201d preference, the company suppresses enrichment and blocks exporting lead records to certain partners. Sales still receives the lead, but the downstream sharing is limited. This demonstrates how \u201cDo Not Sell\u201d affects data operations beyond ad tech\u2014an important Privacy & Consent<\/strong> lesson.<\/p>\n\n\n\n

          Benefits of Using Do Not Sell<\/h2>\n\n\n\n

          When implemented well, \u201cDo Not Sell\u201d delivers benefits beyond compliance.<\/p>\n\n\n\n

            \n
          • Reduced risk and fewer escalations:<\/strong> Clear enforcement lowers the likelihood of complaints and regulatory scrutiny.<\/li>\n
          • Higher-quality first-party strategy:<\/strong> Teams invest in consented, first-party data instead of fragile third-party dependence.<\/li>\n
          • Cleaner measurement foundations:<\/strong> Fewer uncontrolled tags and data leaks improves data hygiene and attribution integrity.<\/li>\n
          • Better customer experience:<\/strong> Preference controls demonstrate respect, which can improve long-term retention and engagement.<\/li>\n<\/ul>\n\n\n\n

            In many organizations, \u201cDo Not Sell\u201d becomes a forcing function that strengthens the entire Privacy & Consent<\/strong> operating model.<\/p>\n\n\n\n

            Challenges of Do Not Sell<\/h2>\n\n\n\n

            \u201cDo Not Sell\u201d can be deceptively hard because it touches many systems and definitions.<\/p>\n\n\n\n

            Technical challenges<\/h3>\n\n\n\n
              \n
            • Identifying all third-party calls (including those loaded indirectly)<\/li>\n
            • Enforcing preferences across web, app, and server environments<\/li>\n
            • Handling identity resolution without reintroducing prohibited sharing<\/li>\n
            • Maintaining persistence across browsers, devices, and sessions<\/li>\n<\/ul>\n\n\n\n

              Strategic and operational risks<\/h3>\n\n\n\n
                \n
              • Misclassifying what constitutes a \u201csale\u201d in your specific context<\/li>\n
              • Overblocking and harming measurement or site functionality<\/li>\n
              • Underblocking and failing to honor user choice<\/li>\n
              • Vendor contract misalignment (partners reusing data for their purposes)<\/li>\n<\/ul>\n\n\n\n

                Data and measurement limitations<\/h3>\n\n\n\n

                As \u201cDo Not Sell\u201d adoption grows, you may see smaller addressable audiences and less deterministic attribution for ad campaigns. A resilient Privacy & Consent<\/strong> plan anticipates this and shifts toward modeled measurement, aggregated reporting, and stronger first-party channels.<\/p>\n\n\n\n

                Best Practices for Do Not Sell<\/h2>\n\n\n\n
                  \n
                1. \n

                  Start with data mapping, then implement controls<\/strong>\n Document where personal data goes before changing tags. This is the fastest path to enforceable Privacy & Consent<\/strong>.<\/p>\n<\/li>\n

                2. \n

                  Make the choice easy to find and understand<\/strong>\n Use plain language. The user should know what \u201cDo Not Sell\u201d affects (e.g., third-party disclosures) without reading legal text.<\/p>\n<\/li>\n

                3. \n

                  Enforce at multiple layers<\/strong>\n Combine tag rules, server-side controls, vendor settings, and export suppression. Relying on only one layer is brittle.<\/p>\n<\/li>\n

                4. \n

                  Design for persistence and auditability<\/strong>\n Store timestamps, scope (web\/app), and how the preference was captured. Audit logs help demonstrate your Privacy & Consent<\/strong> discipline.<\/p>\n<\/li>\n

                5. \n

                  Align contracts and partner configurations<\/strong>\n Ensure vendors support your restrictions and that your team knows which integrations are allowed after a \u201cDo Not Sell\u201d opt-out.<\/p>\n<\/li>\n

                6. \n

                  Test like a marketer and like an engineer<\/strong>\n Validate that tags don\u2019t fire, but also verify downstream data warehouses, CRM syncs, and ad platform connectors.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                  Tools Used for Do Not Sell<\/h2>\n\n\n\n

                  \u201cDo Not Sell\u201d is operationalized through tool categories rather than a single product type. Common tool groups include:<\/p>\n\n\n\n

                    \n
                  • Consent and preference management tools:<\/strong> Capture and store \u201cDo Not Sell\u201d choices, manage UI, and pass signals to downstream systems\u2014central to Privacy & Consent<\/strong> execution.<\/li>\n
                  • Tag management systems:<\/strong> Conditionally fire or block third-party tags based on the \u201cDo Not Sell\u201d state.<\/li>\n
                  • Analytics tools:<\/strong> Configure data collection and sharing features to align with user preferences; adjust identity features and data retention.<\/li>\n
                  • Customer data platforms (CDP) and data pipelines:<\/strong> Control event routing, audience exports, and identity stitching based on \u201cDo Not Sell.\u201d<\/li>\n
                  • CRM systems and marketing automation:<\/strong> Store preference fields, enforce suppression rules, and ensure downstream campaigns respect the preference.<\/li>\n
                  • Ad platforms and activation connectors:<\/strong> Manage audience syncing settings and limit sharing; confirm partner-side controls match your intent.<\/li>\n
                  • Reporting dashboards and governance workflows:<\/strong> Monitor preference rates, enforcement coverage, and data-flow exceptions as part of Privacy & Consent<\/strong> monitoring.<\/li>\n<\/ul>\n\n\n\n

                    Metrics Related to Do Not Sell<\/h2>\n\n\n\n

                    Measuring \u201cDo Not Sell\u201d is about adoption, coverage, and business impact\u2014not just conversions.<\/p>\n\n\n\n

                      \n
                    • Preference rate:<\/strong> Percentage of visitors\/users who select \u201cDo Not Sell.\u201d<\/li>\n
                    • Enforcement coverage:<\/strong> Share of tags\/partners\/data exports governed by the preference (a control metric for Privacy & Consent<\/strong> maturity).<\/li>\n
                    • Data leakage checks:<\/strong> Instances where third-party calls occur despite the preference (often found via tag audits).<\/li>\n
                    • Addressable audience size:<\/strong> Impact on retargeting or lookalike pools after applying \u201cDo Not Sell.\u201d<\/li>\n
                    • Opt-in and retention signals:<\/strong> Changes in email\/SMS opt-in rates, repeat purchase, churn, or subscription renewal\u2014useful for understanding trust effects.<\/li>\n
                    • Operational SLAs:<\/strong> Time to apply the preference across systems and time to resolve exceptions.<\/li>\n<\/ul>\n\n\n\n

                      Future Trends of Do Not Sell<\/h2>\n\n\n\n

                      \u201cDo Not Sell\u201d is evolving as privacy expectations, browser changes, and platform policies reshape marketing.<\/p>\n\n\n\n

                        \n
                      • Automation and policy-based controls:<\/strong> More stacks will enforce Privacy & Consent<\/strong> decisions via centralized policy engines that propagate rules across tools.<\/li>\n
                      • Server-side and first-party architectures:<\/strong> As third-party cookies decline, more tracking moves server-side, increasing the need to enforce \u201cDo Not Sell\u201d at the routing layer\u2014not only in the browser.<\/li>\n
                      • AI-driven personalization with guardrails:<\/strong> AI can improve relevance using first-party data, but it also increases governance pressure to ensure models and features respect \u201cDo Not Sell\u201d restrictions.<\/li>\n
                      • Preference signals and interoperability:<\/strong> Expect more standardized ways to communicate opt-out signals across systems, reducing inconsistent enforcement.<\/li>\n
                      • Measurement shifts:<\/strong> Aggregated reporting, modeled attribution, and privacy-preserving analytics will become more common in Privacy & Consent<\/strong> programs as direct identifiers become less available.<\/li>\n<\/ul>\n\n\n\n

                        Do Not Sell vs Related Terms<\/h2>\n\n\n\n

                        Do Not Sell vs cookie consent<\/h3>\n\n\n\n

                        Cookie consent focuses on permission to store\/read information on a device (often for analytics or advertising cookies). \u201cDo Not Sell\u201d focuses on restricting certain disclosures of personal information to third parties. In Privacy & Consent<\/strong>, you may need both: one governs device storage; the other governs downstream sharing.<\/p>\n\n\n\n

                        Do Not Sell vs opt-out of targeted advertising<\/h3>\n\n\n\n

                        Opt-out of targeted advertising is broader and may cover personalization based on cross-site or cross-app behavior, even if no \u201csale\u201d occurs. \u201cDo Not Sell\u201d is specifically about selling\/disclosing data in a way that meets a defined threshold. Operationally, many teams align them because the same ad tech data flows are involved, but the legal triggers can differ.<\/p>\n\n\n\n

                        Do Not Sell vs Do Not Track<\/h3>\n\n\n\n

                        Do Not Track was a browser signal that many organizations did not universally honor. \u201cDo Not Sell\u201d is tied to explicit privacy rights and enforcement expectations in certain jurisdictions. For Privacy & Consent<\/strong> teams, \u201cDo Not Sell\u201d should be treated as a formal preference with auditable enforcement, not a best-effort header.<\/p>\n\n\n\n

                        Who Should Learn Do Not Sell<\/h2>\n\n\n\n
                          \n
                        • Marketers:<\/strong> To understand how audience building, retargeting, and partner integrations change when \u201cDo Not Sell\u201d is enabled.<\/li>\n
                        • Analysts:<\/strong> To interpret shifts in attribution, audience sizes, and reporting when data sharing is restricted under Privacy & Consent<\/strong> rules.<\/li>\n
                        • Agencies:<\/strong> To plan campaigns that respect client privacy requirements and avoid risky data-sharing practices.<\/li>\n
                        • Business owners and founders:<\/strong> To balance growth with trust, and to make informed decisions about martech vendors and data partnerships.<\/li>\n
                        • Developers and data engineers:<\/strong> To implement preference propagation, tag controls, and data pipeline governance that make \u201cDo Not Sell\u201d enforceable.<\/li>\n<\/ul>\n\n\n\n

                          Summary of Do Not Sell<\/h2>\n\n\n\n

                          \u201cDo Not Sell\u201d is a user preference that restricts selling\u2014or operationally, certain third-party disclosures\u2014of personal information. It matters because today\u2019s marketing stacks frequently share identifiers and behavioral data with partners. Implementing \u201cDo Not Sell\u201d well requires more than a footer link: it needs data mapping, preference storage, enforcement across tags and pipelines, vendor alignment, and ongoing monitoring.<\/p>\n\n\n\n

                          Within Privacy & Consent<\/strong>, \u201cDo Not Sell\u201d supports transparent user choice and strengthens governance. When integrated thoughtfully, it helps organizations build sustainable first-party marketing while reducing risk and improving customer trust.<\/p>\n\n\n\n

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

                          1) What does \u201cDo Not Sell\u201d mean for my website analytics?<\/h3>\n\n\n\n

                          It means you may need to limit or reconfigure analytics features that share data with third parties or use data for their own purposes. In Privacy & Consent<\/strong> practice, many teams keep essential first-party analytics while disabling partner sharing and certain advertising features when \u201cDo Not Sell\u201d is enabled.<\/p>\n\n\n\n

                          2) Is Do Not Sell the same as opting out of all advertising?<\/h3>\n\n\n\n

                          No. \u201cDo Not Sell\u201d typically targets specific kinds of data disclosures. You can still run advertising, but you may need to rely more on contextual targeting, first-party audiences built under appropriate permissions, and privacy-preserving measurement approaches aligned with Privacy & Consent<\/strong>.<\/p>\n\n\n\n

                          3) Do I need a \u201cDo Not Sell\u201d link if I don\u2019t think I sell data?<\/h3>\n\n\n\n

                          You need to evaluate your data flows and partner relationships carefully. Some ad tech disclosures can be treated as a \u201csale\u201d depending on definitions and context. A solid Privacy & Consent<\/strong> assessment includes vendor contracts, tag behavior, and how value is exchanged.<\/p>\n\n\n\n

                          4) How should \u201cDo Not Sell\u201d affect my remarketing and audience syncing?<\/h3>\n\n\n\n

                          If a user opts out, you should suppress sending their identifiers or events to partners for cross-site targeting. That often means blocking pixels, limiting server-side forwarding, and preventing CRM-to-ad-platform audience exports for those users\u2014core enforcement steps for \u201cDo Not Sell.\u201d<\/p>\n\n\n\n

                          5) What\u2019s the difference between Privacy & Consent and just having a privacy policy?<\/h3>\n\n\n\n

                          A privacy policy explains what you do; Privacy & Consent<\/strong> is the operational system that makes your promises true. \u201cDo Not Sell\u201d is one of the preference controls that must be implemented and enforced, not merely described.<\/p>\n\n\n\n

                          6) How do I prove that I honored a Do Not Sell request?<\/h3>\n\n\n\n

                          Maintain records of when the preference was captured, how it was applied, and what systems it affected. Use tag audits, routing logs, and suppression checks to demonstrate enforcement. This kind of evidence is a practical pillar of Privacy & Consent<\/strong> governance.<\/p>\n\n\n\n

                          7) Will Do Not Sell reduce my marketing performance?<\/h3>\n\n\n\n

                          It can reduce addressable audience size for certain tactics, especially third-party retargeting. However, many organizations offset this by improving first-party data programs, increasing on-site conversion efficiency, and using aggregated or modeled measurement\u2014often resulting in more durable growth within Privacy & Consent<\/strong> constraints.<\/p>\n","protected":false},"excerpt":{"rendered":"

                          \u201cDo Not Sell\u201d is a consumer choice signal that tells a business not to sell (and, in many real-world implementations, not to share) a person\u2019s personal information with third parties in ways that trigger privacy obligations. In **Privacy & Consent** programs, \u201cDo Not Sell\u201d is less about a single button on a website and more about a durable operational promise: the individual\u2019s data must not be routed into data flows that constitute a sale under applicable rules.<\/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-11534","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\/11534","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=11534"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/11534\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=11534"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=11534"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=11534"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}