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

Modern marketing is no longer just about finding the right people\u2014it\u2019s about targeting the right people in the right way<\/strong>, based on what data you\u2019re allowed to use and how individuals want their data handled. That\u2019s where Privacy Target Audience<\/strong> comes in: an audience definition built around privacy choices, consent status, and permitted data uses within Privacy & Consent<\/strong> programs.<\/p>\n\n\n\n

In a world of tighter regulation, browser restrictions, and rising customer expectations, Privacy Target Audience<\/strong> has become a core capability. It helps teams align acquisition, personalization, analytics, and retention with Privacy & Consent<\/strong> requirements\u2014without sacrificing marketing effectiveness or customer trust.<\/p>\n\n\n\n

What Is Privacy Target Audience?<\/h2>\n\n\n\n

Privacy Target Audience<\/strong> is a way of defining and activating marketing audiences based on privacy permissions and consent signals<\/strong>, not just demographics, interests, or behaviors. In simple terms, it answers: \u201cWho can we target, through which channels, using what data, for which purposes, and under which legal or policy constraints?\u201d<\/em><\/p>\n\n\n\n

The core concept is permission-aware segmentation<\/strong>. Instead of building an audience purely from available identifiers (email, cookies, device IDs), you build it from what\u2019s allowed<\/strong>\u2014including consent state, opt-out flags, communication preferences, jurisdictional rules, and data retention limits.<\/p>\n\n\n\n

From a business perspective, Privacy Target Audience<\/strong> turns privacy from a blocker into an operational marketing system. It reduces wasted spend on unreachable users, limits compliance risk, and improves customer experience by honoring preferences consistently across touchpoints.<\/p>\n\n\n\n

Within Privacy & Consent<\/strong>, Privacy Target Audience<\/strong> sits at the intersection of:\n– consent and preference collection (what a person agreed to)\n– data governance (what the business is allowed to store and use)\n– activation (where and how campaigns run)<\/p>\n\n\n\n

Inside Privacy & Consent<\/strong>, it functions as the \u201cgo\/no-go\u201d logic that determines whether someone should be included in targeting, excluded, or placed into a limited-data experience.<\/p>\n\n\n\n

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

Privacy Target Audience<\/strong> matters because targeting without clear permission has become both riskier and less effective. As third-party tracking declines, first-party relationships and transparent consent become the foundation of sustainable growth in Privacy & Consent<\/strong> initiatives.<\/p>\n\n\n\n

Strategically, it helps organizations:\n– Protect trust and brand reputation<\/strong> by respecting user choices consistently\n– Reduce regulatory exposure<\/strong> by preventing unauthorized processing and outreach\n– Improve marketing efficiency<\/strong> by focusing on addressable, consented segments\n– Increase conversion quality<\/strong> because users who opted in are typically more engaged<\/p>\n\n\n\n

From a performance angle, Privacy Target Audience<\/strong> can be a competitive advantage. Teams that operationalize privacy well often see better list health, stronger retention, and more stable measurement\u2014even as signal loss increases across the ecosystem. In mature Privacy & Consent<\/strong> programs, audience strategy and privacy strategy become the same thing.<\/p>\n\n\n\n

How Privacy Target Audience Works<\/h2>\n\n\n\n

Privacy Target Audience<\/strong> is both conceptual and operational. In practice, it works as a workflow that converts privacy choices into executable audience rules.<\/p>\n\n\n\n

    \n
  1. \n

    Input or trigger: collect privacy signals<\/strong>\n – Consent (opt-in\/opt-out) for purposes like marketing, analytics, personalization\n – Communication preferences (email, SMS, push notifications)\n – Region\/jurisdiction (which rules apply)\n – Account status and age gating where relevant<\/p>\n<\/li>\n

  2. \n

    Analysis or processing: interpret what\u2019s permitted<\/strong>\n – Map each signal to allowed data uses (e.g., \u201ccan send promotional email\u201d)\n – Apply policy logic (data minimization, retention windows, purpose limitation)\n – Resolve identity across systems (while respecting constraints)<\/p>\n<\/li>\n

  3. \n

    Execution or application: build segments and activate<\/strong>\n – Create inclusion\/exclusion rules in CRM, marketing automation, analytics, and ad platforms\n – Suppress users who opted out or lack a lawful basis for certain outreach\n – Personalize only where permitted, and fall back to contextual or generic experiences when not<\/p>\n<\/li>\n

  4. \n

    Output or outcome: compliant reach and measurable results<\/strong>\n – Campaigns run against audiences you\u2019re allowed to target\n – Auditability improves because criteria are explicit\n – Performance becomes more stable because audiences are cleaner and more intentional<\/p>\n<\/li>\n<\/ol>\n\n\n\n

    Done well, Privacy Target Audience<\/strong> becomes a repeatable system embedded into daily marketing operations within Privacy & Consent<\/strong>.<\/p>\n\n\n\n

    Key Components of Privacy Target Audience<\/h2>\n\n\n\n

    A reliable Privacy Target Audience<\/strong> setup typically includes:<\/p>\n\n\n\n

      \n
    • Consent and preference capture<\/strong><\/li>\n
    • Consent banners, preference centers, subscription forms, in-app prompts<\/li>\n
    • Consent storage and audit trail<\/strong><\/li>\n
    • Timestamp, source, version of notice, purpose-level choices, proof of change<\/li>\n
    • Identity and data hygiene<\/strong><\/li>\n
    • Deduplication, suppression logic, and safe join keys between systems<\/li>\n
    • Purpose-based governance<\/strong><\/li>\n
    • Clear rules for what data can be used for which purpose under Privacy & Consent<\/strong><\/li>\n
    • Activation pipelines<\/strong><\/li>\n
    • Mechanisms to sync audiences to email\/SMS tools, on-site personalization, and ad platforms<\/li>\n
    • Measurement controls<\/strong><\/li>\n
    • Tagging rules that respect consent (e.g., only firing certain tags when allowed)<\/li>\n
    • Team responsibilities<\/strong><\/li>\n
    • Marketing owns execution, legal\/privacy defines constraints, data\/engineering operationalizes enforcement, analytics validates outcomes<\/li>\n<\/ul>\n\n\n\n

      The strongest programs treat Privacy Target Audience<\/strong> as a shared system, not a single tool configuration.<\/p>\n\n\n\n

      Types of Privacy Target Audience<\/h2>\n\n\n\n

      \u201cTypes\u201d aren\u2019t always formalized, but there are practical distinctions teams use to implement Privacy Target Audience<\/strong> effectively:<\/p>\n\n\n\n

      1. Consent-status audiences<\/h3>\n\n\n\n
        \n
      • Fully opted-in (marketing + analytics allowed)<\/li>\n
      • Partial consent (analytics allowed, marketing not allowed)<\/li>\n
      • Opted-out \/ do-not-sell \/ do-not-share<\/li>\n
      • Unknown \/ not yet decided (requiring conservative defaults depending on context)<\/li>\n<\/ul>\n\n\n\n

        2. Purpose-based audiences<\/h3>\n\n\n\n

        Segmentation based on what processing purpose is allowed:\n– marketing outreach\n– personalization\n– analytics measurement\n– customer support communications<\/p>\n\n\n\n

        3. Channel-permission audiences<\/h3>\n\n\n\n

        A user may permit one channel but not another:\n– email subscribed vs unsubscribed\n– SMS opted-in vs not opted-in\n– app push allowed vs disabled at device level<\/p>\n\n\n\n

        4. Jurisdiction-aware audiences<\/h3>\n\n\n\n

        Rules vary by geography and policy:\n– stricter handling for certain regions\n– different disclosure and opt-out requirements\nThis is often essential in Privacy & Consent<\/strong> programs spanning multiple markets.<\/p>\n\n\n\n

        5. First-party vs partner-activated audiences<\/h3>\n\n\n\n
          \n
        • first-party audiences used on owned channels<\/li>\n
        • privacy-safe partner activation (where allowed), often with additional controls<\/li>\n<\/ul>\n\n\n\n

          These distinctions help turn Privacy Target Audience<\/strong> into implementable, testable logic rather than a vague principle.<\/p>\n\n\n\n

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

          Example 1: Ecommerce promotional email vs loyalty updates<\/h3>\n\n\n\n

          An ecommerce brand separates audiences into:\n– customers who opted into promotional email\n– customers who opted out of marketing but still receive transactional and loyalty balance updates\nThis Privacy Target Audience<\/strong> approach protects deliverability and reduces complaint rates, while keeping essential communications intact under Privacy & Consent<\/strong> rules.<\/p>\n\n\n\n

          Example 2: SaaS retargeting with partial consent<\/h3>\n\n\n\n

          A SaaS company allows analytics cookies for some users but not marketing cookies. The team builds a Privacy Target Audience<\/strong> that:\n– includes only users who consented to marketing for retargeting\n– uses aggregated reporting for those who only allowed analytics\nThis reduces wasted ad spend and aligns tracking\/activation with Privacy & Consent<\/strong> requirements.<\/p>\n\n\n\n

          Example 3: Publisher personalization with conservative defaults<\/h3>\n\n\n\n

          A publisher personalizes content for logged-in users who allowed personalization, while showing contextual recommendations to users who declined. The Privacy Target Audience<\/strong> logic determines:\n– who gets personalized modules\n– who gets generic modules\n– which measurement tags can fire\nThis preserves user experience while honoring Privacy & Consent<\/strong> choices.<\/p>\n\n\n\n

          Benefits of Using Privacy Target Audience<\/h2>\n\n\n\n

          Implementing Privacy Target Audience<\/strong> delivers benefits beyond compliance:<\/p>\n\n\n\n

            \n
          • Performance improvements<\/strong><\/li>\n
          • Higher engagement from opted-in segments<\/li>\n
          • Cleaner lists and audiences, improving conversion rates<\/li>\n
          • Cost savings<\/strong><\/li>\n
          • Fewer impressions and messages sent to users you cannot legally or ethically target<\/li>\n
          • Reduced operational waste from repeatedly fixing consent-related errors<\/li>\n
          • Efficiency gains<\/strong><\/li>\n
          • Standardized rules reduce ad-hoc decision-making across teams<\/li>\n
          • Faster campaign launches because constraints are pre-modeled<\/li>\n
          • Better customer experience<\/strong><\/li>\n
          • Preferences are respected, reducing frustration and churn<\/li>\n
          • More relevant messaging where permission exists, less intrusive outreach where it doesn\u2019t<\/li>\n<\/ul>\n\n\n\n

            In mature Privacy & Consent<\/strong> operations, Privacy Target Audience<\/strong> becomes a growth lever because it improves signal quality and trust simultaneously.<\/p>\n\n\n\n

            Challenges of Privacy Target Audience<\/h2>\n\n\n\n

            Despite the upside, Privacy Target Audience<\/strong> can be difficult to execute well:<\/p>\n\n\n\n

              \n
            • Signal propagation issues<\/strong><\/li>\n
            • Consent captured in one place doesn\u2019t always reach every system reliably<\/li>\n
            • Identity fragmentation<\/strong><\/li>\n
            • Users appear as multiple profiles across devices, browsers, and platforms<\/li>\n
            • Complex policy logic<\/strong><\/li>\n
            • Purpose limitation and retention rules require careful mapping and documentation<\/li>\n
            • Measurement limitations<\/strong><\/li>\n
            • Less trackable inventory can reduce user-level attribution and increase reliance on modeled or aggregated reporting<\/li>\n
            • Organizational friction<\/strong><\/li>\n
            • Marketing, legal, and engineering may interpret Privacy & Consent<\/strong> requirements differently without shared definitions<\/li>\n
            • Over-segmentation risk<\/strong><\/li>\n
            • Too many micro-audiences can make activation and reporting unmanageable<\/li>\n<\/ul>\n\n\n\n

              These challenges are solvable, but they require treating Privacy Target Audience<\/strong> as a system with governance, not a one-time setup.<\/p>\n\n\n\n

              Best Practices for Privacy Target Audience<\/h2>\n\n\n\n

              To build a durable Privacy Target Audience<\/strong> strategy within Privacy & Consent<\/strong>, focus on operational clarity:<\/p>\n\n\n\n

                \n
              1. \n

                Define purposes and allowed uses in plain language<\/strong>\n – Write internal definitions of \u201cmarketing,\u201d \u201canalytics,\u201d \u201cpersonalization,\u201d and map them to systems and tags.<\/p>\n<\/li>\n

              2. \n

                Build consent-aware suppression as a default<\/strong>\n – Make \u201cdo not contact \/ do not target\u201d lists first-class citizens in CRM and ad workflows.<\/p>\n<\/li>\n

              3. \n

                Keep audience rules transparent and auditable<\/strong>\n – Document inclusion criteria and data sources for each Privacy Target Audience<\/strong> segment.<\/p>\n<\/li>\n

              4. \n

                Design for partial consent<\/strong>\n – Plan experiences that work when personalization or marketing tracking is not allowed.<\/p>\n<\/li>\n

              5. \n

                Minimize data, maximize usefulness<\/strong>\n – Prefer data that is necessary and permissioned; reduce brittle dependencies on sensitive or low-value signals.<\/p>\n<\/li>\n

              6. \n

                Monitor drift<\/strong>\n – Regularly check that consent states match across systems (CMP, CRM, automation, analytics).<\/p>\n<\/li>\n

              7. \n

                Train teams<\/strong>\n – Ensure campaign managers, analysts, and developers understand how Privacy & Consent<\/strong> rules translate into audience logic.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                Tools Used for Privacy Target Audience<\/h2>\n\n\n\n

                Privacy Target Audience<\/strong> is usually operationalized through a stack of complementary tool categories:<\/p>\n\n\n\n

                  \n
                • Consent management and preference systems<\/strong><\/li>\n
                • Capture, store, and update consent and communication preferences<\/li>\n
                • Tag management and measurement controls<\/strong><\/li>\n
                • Control which tags fire based on consent state, supporting Privacy & Consent<\/strong> enforcement<\/li>\n
                • Analytics tools<\/strong><\/li>\n
                • Measure performance with consent-aware configurations and aggregated reporting options<\/li>\n
                • CRM systems<\/strong><\/li>\n
                • Maintain customer records, subscription status, suppression lists, and lifecycle stages<\/li>\n
                • Marketing automation platforms<\/strong><\/li>\n
                • Execute consent-aware journeys and enforce channel-level permissions<\/li>\n
                • Ad platform audience managers<\/strong><\/li>\n
                • Activate only eligible segments and exclude opt-outs<\/li>\n
                • Data warehouses and reporting dashboards<\/strong><\/li>\n
                • Centralize logs, validate compliance rules, and track audience health over time<\/li>\n<\/ul>\n\n\n\n

                  The key is not any single tool, but consistent logic: Privacy Target Audience<\/strong> rules must be aligned end-to-end across Privacy & Consent<\/strong> workflows.<\/p>\n\n\n\n

                  Metrics Related to Privacy Target Audience<\/h2>\n\n\n\n

                  To evaluate Privacy Target Audience<\/strong>, combine compliance-health metrics with performance metrics:<\/p>\n\n\n\n

                    \n
                  • Opt-in rate (by channel and purpose)<\/strong><\/li>\n
                  • How many users grant marketing permission vs analytics-only consent<\/li>\n
                  • Consented reach<\/strong><\/li>\n
                  • Size and growth rate of eligible audiences over time<\/li>\n
                  • Suppression rate<\/strong><\/li>\n
                  • Percentage excluded due to opt-out, missing consent, or jurisdiction rules<\/li>\n
                  • Match\/activation rate<\/strong><\/li>\n
                  • How many consented profiles can be activated in a given channel (email, ads, onsite)<\/li>\n
                  • Complaint and unsubscribe rates<\/strong><\/li>\n
                  • Leading indicators that your targeting is misaligned with expectations<\/li>\n
                  • Conversion rate and CPA\/ROAS (for eligible segments)<\/strong><\/li>\n
                  • Performance measured on privacy-permitted audiences<\/li>\n
                  • Consent-state consistency<\/strong><\/li>\n
                  • Percentage of records where consent matches across CMP, CRM, and automation systems<\/li>\n<\/ul>\n\n\n\n

                    These metrics make Privacy Target Audience<\/strong> measurable, not just policy-driven.<\/p>\n\n\n\n

                    Future Trends of Privacy Target Audience<\/h2>\n\n\n\n

                    Several shifts are shaping how Privacy Target Audience<\/strong> evolves inside Privacy & Consent<\/strong>:<\/p>\n\n\n\n

                      \n
                    • AI-driven personalization with tighter constraints<\/strong><\/li>\n
                    • More on-device and privacy-preserving approaches will emerge to reduce reliance on raw identifiers.<\/li>\n
                    • Automation of consent-to-activation<\/strong><\/li>\n
                    • Expect stronger rule engines that automatically translate consent states into audience eligibility across channels.<\/li>\n
                    • Growth of contextual and cohort-like strategies<\/strong><\/li>\n
                    • When individual targeting is limited, contextual signals and aggregated insights will complement Privacy Target Audience<\/strong>.<\/li>\n
                    • Increased use of privacy-safe collaboration<\/strong><\/li>\n
                    • Clean-room-style workflows and aggregated matching will expand where organizations need shared insights without sharing raw data.<\/li>\n
                    • Standardized preference signals<\/strong><\/li>\n
                    • Broader adoption of global privacy signals and simplified preference management will push teams to make Privacy Target Audience<\/strong> logic more dynamic and user-controlled.<\/li>\n<\/ul>\n\n\n\n

                      In short, Privacy Target Audience<\/strong> will increasingly define not only who you market to, but also how you measure and learn within Privacy & Consent<\/strong> constraints.<\/p>\n\n\n\n

                      Privacy Target Audience vs Related Terms<\/h2>\n\n\n\n

                      Privacy Target Audience vs Audience Segmentation<\/h3>\n\n\n\n

                      Audience segmentation groups people by attributes or behavior (e.g., \u201ccart abandoners\u201d). Privacy Target Audience<\/strong> adds the permission layer: it\u2019s segmentation constrained by consent, purposes, and allowed processing within Privacy & Consent<\/strong>.<\/p>\n\n\n\n

                      Privacy Target Audience vs Consent Management<\/h3>\n\n\n\n

                      Consent management focuses on collecting and storing user choices. Privacy Target Audience<\/strong> focuses on using those choices operationally<\/em> to build eligible audiences and suppress ineligible ones across marketing execution.<\/p>\n\n\n\n

                      Privacy Target Audience vs First-Party Data Strategy<\/h3>\n\n\n\n

                      First-party data strategy is about collecting and using your own customer data. Privacy Target Audience<\/strong> governs which parts of that data can be used, for which purposes, and for whom<\/em>, based on Privacy & Consent<\/strong>.<\/p>\n\n\n\n

                      Who Should Learn Privacy Target Audience<\/h2>\n\n\n\n
                        \n
                      • Marketers<\/strong> need Privacy Target Audience<\/strong> to run campaigns that are both effective and permission-aware across channels.<\/li>\n
                      • Analysts<\/strong> need it to interpret performance correctly when tracking differs by consent state and to avoid misleading attribution.<\/li>\n
                      • Agencies<\/strong> need it to design targeting and measurement plans that won\u2019t break when privacy rules or platform capabilities change.<\/li>\n
                      • Business owners and founders<\/strong> need it to reduce risk while building trust-based growth loops (email, subscriptions, loyalty).<\/li>\n
                      • Developers<\/strong> need it to implement consent-aware tagging, data flows, suppression logic, and preference synchronization within Privacy & Consent<\/strong> systems.<\/li>\n<\/ul>\n\n\n\n

                        Summary of Privacy Target Audience<\/h2>\n\n\n\n

                        Privacy Target Audience<\/strong> is the practice of defining and activating marketing audiences based on consent, privacy preferences, and permitted data uses. It matters because it protects trust, reduces compliance risk, and improves efficiency by focusing spend and personalization on audiences you are allowed to engage. Within Privacy & Consent<\/strong>, it acts as the operational bridge between user choices and real campaign execution\u2014supporting sustainable measurement and respectful marketing at scale.<\/p>\n\n\n\n

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

                        1) What does Privacy Target Audience mean in practical marketing terms?<\/h3>\n\n\n\n

                        It means your targeting lists are built with permission logic\u2014only including people you\u2019re allowed to reach for a specific purpose and channel, and excluding those who opted out or lack the required consent.<\/p>\n\n\n\n

                        2) How is Privacy Target Audience different from a normal remarketing audience?<\/h3>\n\n\n\n

                        A normal remarketing audience is often based on behavior (site visits, product views). A Privacy Target Audience<\/strong> includes behavior only when the relevant consent and permitted processing are in place under Privacy & Consent<\/strong> rules.<\/p>\n\n\n\n

                        3) Does Privacy Target Audience reduce campaign reach?<\/h3>\n\n\n\n

                        Often yes, at first\u2014because you stop targeting people you shouldn\u2019t. Over time, it can increase effective<\/em> reach by improving opt-in rates, list quality, and customer trust.<\/p>\n\n\n\n

                        4) What systems typically \u201cown\u201d Privacy Target Audience rules?<\/h3>\n\n\n\n

                        Usually multiple systems share ownership: consent and preference tools capture choices, CRM and automation enforce messaging permissions, analytics enforces measurement rules, and ad platforms enforce activation eligibility.<\/p>\n\n\n\n

                        5) What are the most important metrics to track for Privacy Target Audience?<\/h3>\n\n\n\n

                        Opt-in rate, consented reach, suppression rate, activation\/match rate, unsubscribe\/complaint rate, and performance metrics (conversion rate, CPA\/ROAS) for eligible segments.<\/p>\n\n\n\n

                        6) How does Privacy & Consent affect analytics and reporting for these audiences?<\/h3>\n\n\n\n

                        Privacy & Consent<\/strong> can limit which tags fire and which identifiers are available, shifting reporting toward aggregated, modeled, or consented-only datasets. That makes it important to analyze results by consent state rather than assuming one unified dataset.<\/p>\n\n\n\n

                        7) Can small businesses benefit from Privacy Target Audience, or is it only for enterprises?<\/h3>\n\n\n\n

                        Small businesses benefit significantly. Even simple rules\u2014like separating promotional vs transactional email audiences and honoring opt-outs consistently\u2014are foundational Privacy Target Audience<\/strong> practices that improve deliverability, trust, and efficiency.<\/p>\n","protected":false},"excerpt":{"rendered":"

                        Modern marketing is no longer just about finding the right people\u2014it\u2019s about targeting the right people **in the right way**, based on what data you\u2019re allowed to use and how individuals want their data handled. That\u2019s where **Privacy Target Audience** comes in: an audience definition built around privacy choices, consent status, and permitted data uses within **Privacy & Consent** programs.<\/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-11621","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\/11621","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=11621"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/11621\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=11621"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=11621"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=11621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}