{"id":6916,"date":"2026-03-23T17:30:35","date_gmt":"2026-03-23T17:30:35","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/product-qualified-event\/"},"modified":"2026-03-23T17:30:35","modified_gmt":"2026-03-23T17:30:35","slug":"product-qualified-event","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/product-qualified-event\/","title":{"rendered":"Product-qualified Event: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Analytics"},"content":{"rendered":"\n

A Product-qualified Event<\/strong> is a measurable in-product action that signals a user has experienced meaningful value and is therefore more likely to convert, expand, or retain. In Conversion & Measurement<\/strong>, it shifts the focus from \u201cdid someone click?\u201d to \u201cdid someone reach a moment of product value?\u201d In Analytics<\/strong>, it becomes a defined event you can track, segment, attribute, and optimize across channels and lifecycle stages.<\/p>\n\n\n\n

This concept matters because modern growth is increasingly product-led: trials, freemium tiers, self-serve onboarding, and in-app upgrades all create conversion paths that don\u2019t map cleanly to traditional lead forms. By designing and instrumenting a Product-qualified Event, teams gain a shared, evidence-based way to identify high-intent users, prioritize follow-up, and measure marketing\u2019s real contribution to revenue.<\/p>\n\n\n\n

What Is Product-qualified Event?<\/h2>\n\n\n\n

A Product-qualified Event<\/strong> is a specific product interaction\u2014captured as an event in your tracking stack\u2014that indicates a user has crossed a meaningful threshold of engagement or success. It is \u201cqualified\u201d because it is intentionally chosen to correlate with downstream outcomes like paid conversion, activation, retention, or expansion.<\/p>\n\n\n\n

At its core, the concept is simple:<\/p>\n\n\n\n

    \n
  • Event<\/strong>: a discrete action (e.g., \u201ccreated project,\u201d \u201cinvited teammate,\u201d \u201cpublished report\u201d).<\/li>\n
  • Product-qualified<\/strong>: the action reflects real product value, not just curiosity.<\/li>\n<\/ul>\n\n\n\n

    The business meaning is even more important than the technical definition: a Product-qualified Event is a decision point<\/strong>. It informs how you prioritize users, how you trigger lifecycle messaging, and how you evaluate channel performance. In Conversion & Measurement<\/strong>, it often sits between acquisition metrics (traffic, sign-ups) and revenue metrics (paid plans, renewals). In Analytics<\/strong>, it is a cornerstone event used for cohorts, funnels, attribution analysis, experimentation, and forecasting.<\/p>\n\n\n\n

    Why Product-qualified Event Matters in Conversion & Measurement<\/h2>\n\n\n\n

    A well-chosen Product-qualified Event improves Conversion & Measurement<\/strong> because it connects marketing activity to product usage\u2014where real intent and value are revealed. This reduces the gap between \u201cmarketing-generated activity\u201d and \u201cbusiness outcomes.\u201d<\/p>\n\n\n\n

    Key reasons it matters:<\/p>\n\n\n\n

      \n
    • Stronger signal than surface metrics<\/strong>: Pageviews, clicks, or even sign-ups can be noisy. A Product-qualified Event is usually closer to the \u201caha moment,\u201d making it more predictive of conversion.<\/li>\n
    • Better budget decisions<\/strong>: When Analytics<\/strong> ties channels to product-qualified behaviors, you can invest in sources that produce users who actually activate.<\/li>\n
    • Higher-quality lifecycle marketing<\/strong>: Messaging triggered after a Product-qualified Event tends to be more relevant (e.g., upsell after a user hits a usage limit).<\/li>\n
    • Competitive advantage<\/strong>: Teams that measure product value moments can iterate faster\u2014improving onboarding, reducing churn, and tuning acquisition to the right audiences.<\/li>\n<\/ul>\n\n\n\n

      How Product-qualified Event Works<\/h2>\n\n\n\n

      A Product-qualified Event is conceptual, but it becomes operational through a practical workflow that links product instrumentation to decision-making in Conversion & Measurement<\/strong> and Analytics<\/strong>.<\/p>\n\n\n\n

        \n
      1. \n

        Input \/ Trigger: user performs a meaningful action<\/strong>\n A user completes an in-app step aligned with value (e.g., \u201cconnected data source,\u201d \u201ccreated first automation,\u201d \u201cadded billing details,\u201d \u201cinvited 2+ teammates\u201d).<\/p>\n<\/li>\n

      2. \n

        Analysis \/ Processing: event is captured, enriched, and evaluated<\/strong>\n Your tracking setup logs the event with relevant properties (plan type, account size, source\/medium, device, role). In Analytics<\/strong>, you validate event quality, deduplicate, and ensure it\u2019s consistently defined across platforms.<\/p>\n<\/li>\n

      3. \n

        Execution \/ Application: event drives actions and measurement<\/strong>\n The Product-qualified Event can trigger workflows (emails, in-app tips, sales outreach) and can be used as a conversion point in reporting. This is where Conversion & Measurement<\/strong> becomes actionable.<\/p>\n<\/li>\n

      4. \n

        Output \/ Outcome: improved conversion, expansion, and insight<\/strong>\n Over time, you quantify how strongly the event predicts outcomes and refine it. A mature program may use multiple Product-qualified Events mapped to different lifecycle stages.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        Key Components of Product-qualified Event<\/h2>\n\n\n\n

        To make a Product-qualified Event reliable and useful, you need alignment across product, marketing, data, and revenue teams. The key components typically include:<\/p>\n\n\n\n

        Event definition and criteria<\/h3>\n\n\n\n
          \n
        • A clear name and description<\/li>\n
        • The qualifying threshold (e.g., \u201cinvited at least 1 teammate,\u201d \u201ccompleted 3 tasks,\u201d \u201cused feature X within 7 days\u201d)<\/li>\n
        • The business rationale (why this indicates value)<\/li>\n<\/ul>\n\n\n\n

          Instrumentation and data inputs<\/h3>\n\n\n\n
            \n
          • Event tracking in the product (web\/app)<\/li>\n
          • Event properties (account ID, user role, plan, workspace size, feature flags)<\/li>\n
          • Identity resolution (anonymous-to-known user mapping)<\/li>\n<\/ul>\n\n\n\n

            Analytics and reporting design<\/h3>\n\n\n\n
              \n
            • Funnel and cohort setup around the Product-qualified Event<\/li>\n
            • Attribution rules (how channels get credit)<\/li>\n
            • Dashboards for Conversion & Measurement<\/strong> stakeholders<\/li>\n<\/ul>\n\n\n\n

              Governance and ownership<\/h3>\n\n\n\n
                \n
              • Who defines and changes the event (often product + growth + data)<\/li>\n
              • Documentation standards and versioning<\/li>\n
              • QA processes to prevent breaking changes<\/li>\n<\/ul>\n\n\n\n

                Types of Product-qualified Event<\/h2>\n\n\n\n

                There isn\u2019t one universal taxonomy, but in practice you\u2019ll see several useful distinctions. These \u201ctypes\u201d help teams apply the concept consistently in Conversion & Measurement<\/strong> and Analytics<\/strong>.<\/p>\n\n\n\n

                Activation events vs. monetization events<\/h3>\n\n\n\n
                  \n
                • Activation Product-qualified Event<\/strong>: signals first value realization (e.g., \u201cpublished first project\u201d).<\/li>\n
                • Monetization Product-qualified Event<\/strong>: signals readiness to pay or upgrade (e.g., \u201chit usage cap,\u201d \u201cadded second workspace,\u201d \u201crequested invoice\u201d).<\/li>\n<\/ul>\n\n\n\n

                  Single-step vs. composite events<\/h3>\n\n\n\n
                    \n
                  • Single-step<\/strong>: one action (e.g., \u201cintegrated Slack\u201d).<\/li>\n
                  • Composite<\/strong>: a rule based on multiple actions and thresholds (e.g., \u201ccompleted onboarding + created 2 projects + invited teammate\u201d).<\/li>\n<\/ul>\n\n\n\n

                    User-level vs. account-level events (B2B especially)<\/h3>\n\n\n\n
                      \n
                    • User-level<\/strong>: individual adoption (good for self-serve).<\/li>\n
                    • Account-level<\/strong>: team adoption (better predictor for larger deals), like \u201c3+ active users in workspace.\u201d<\/li>\n<\/ul>\n\n\n\n

                      Time-bound events<\/h3>\n\n\n\n
                        \n
                      • Qualification within a window (e.g., \u201cdid X within first 7 days\u201d), helpful for onboarding and lifecycle measurement.<\/li>\n<\/ul>\n\n\n\n

                        Real-World Examples of Product-qualified Event<\/h2>\n\n\n\n

                        Example 1: B2B SaaS trial activation<\/h3>\n\n\n\n

                        A project management tool defines a Product-qualified Event as \u201ccreated first project and assigned at least 3 tasks\u201d<\/strong>.<\/p>\n\n\n\n

                          \n
                        • Conversion & Measurement<\/strong> use: measure trial-to-paid conversion rates for users who hit the event vs. those who don\u2019t.<\/li>\n
                        • Analytics<\/strong> use: identify which channels produce more users reaching this milestone, then optimize campaigns and landing pages accordingly.<\/li>\n<\/ul>\n\n\n\n

                          Example 2: Freemium product expansion trigger<\/h3>\n\n\n\n

                          A design collaboration app uses \u201cinvited 2 teammates\u201d<\/strong> as the Product-qualified Event.<\/p>\n\n\n\n

                            \n
                          • Conversion & Measurement<\/strong> use: treat this as a leading indicator for team plan upgrades.<\/li>\n
                          • Analytics<\/strong> use: cohort analysis shows that accounts with teammate invites retain longer, guiding onboarding improvements and referral prompts.<\/li>\n<\/ul>\n\n\n\n

                            Example 3: Developer tool \u201caha moment\u201d<\/h3>\n\n\n\n

                            A developer platform defines a Product-qualified Event as \u201csuccessful API call from production environment\u201d<\/strong>.<\/p>\n\n\n\n

                              \n
                            • Conversion & Measurement<\/strong> use: align nurture emails and in-app docs prompts to get users to first production success.<\/li>\n
                            • Analytics<\/strong> use: segment by language\/framework to see which onboarding paths produce the highest rate of the event.<\/li>\n<\/ul>\n\n\n\n

                              Benefits of Using Product-qualified Event<\/h2>\n\n\n\n

                              A strong Product-qualified Event improves outcomes across the funnel and across teams:<\/p>\n\n\n\n

                                \n
                              • Higher conversion rates<\/strong>: by focusing optimization on reaching value moments, not just driving sign-ups.<\/li>\n
                              • More efficient spend<\/strong>: channels and creatives can be evaluated by product-qualified outcomes, strengthening Conversion & Measurement<\/strong> rigor.<\/li>\n
                              • Better prioritization<\/strong>: sales or success teams can focus on accounts that have demonstrated product value.<\/li>\n
                              • Improved onboarding and UX<\/strong>: if users stall before the Product-qualified Event, product teams know where to reduce friction.<\/li>\n
                              • More credible reporting<\/strong>: Analytics<\/strong> grounded in product behavior reduces debates about \u201cvanity metrics.\u201d<\/li>\n<\/ul>\n\n\n\n

                                Challenges of Product-qualified Event<\/h2>\n\n\n\n

                                Implementing a Product-qualified Event is powerful, but not trivial. Common challenges include:<\/p>\n\n\n\n

                                  \n
                                • Choosing the wrong event<\/strong>: an action may be easy to reach but not predictive (false positives), or too hard to reach (false negatives).<\/li>\n
                                • Instrumentation gaps<\/strong>: incomplete tracking, inconsistent event naming, or missing properties can undermine Analytics<\/strong> validity.<\/li>\n
                                • Identity and attribution issues<\/strong>: cross-device behavior, ad blockers, and privacy constraints can break user stitching and channel crediting.<\/li>\n
                                • Team misalignment<\/strong>: marketing, product, and sales may disagree on what \u201cqualified\u201d means, causing inconsistent Conversion & Measurement<\/strong>.<\/li>\n
                                • Gaming and edge cases<\/strong>: users may trigger an event without real intent (e.g., inviting teammates as a test), requiring refinement.<\/li>\n<\/ul>\n\n\n\n

                                  Best Practices for Product-qualified Event<\/h2>\n\n\n\n

                                  To make your Product-qualified Event durable and scalable, apply these best practices:<\/p>\n\n\n\n

                                    \n
                                  1. \n

                                    Start with outcomes and work backward<\/strong>\n Choose events that correlate with paid conversion, retention, or expansion\u2014not just activity.<\/p>\n<\/li>\n

                                  2. \n

                                    Define the event precisely and document it<\/strong>\n Include thresholds, time windows, and exclusions. Treat definitions like product specs.<\/p>\n<\/li>\n

                                  3. \n

                                    Validate with historical analysis<\/strong>\n In Analytics<\/strong>, compare conversion and retention for users who hit the event vs. those who don\u2019t. Look for lift and consistency across segments.<\/p>\n<\/li>\n

                                  4. \n

                                    Use a small set of canonical events<\/strong>\n Too many \u201cqualified\u201d milestones creates confusion. Maintain a core set aligned to lifecycle stages.<\/p>\n<\/li>\n

                                  5. \n

                                    Instrument properties that enable action<\/strong>\n Capture the context needed for Conversion & Measurement<\/strong> decisions: plan, persona, source, account size, feature usage.<\/p>\n<\/li>\n

                                  6. \n

                                    Monitor data quality continuously<\/strong>\n Set checks for drops\/spikes, schema changes, and missing properties\u2014especially after releases.<\/p>\n<\/li>\n

                                  7. \n

                                    Iterate thoughtfully, not constantly<\/strong>\n Changes break reporting continuity. Version your Product-qualified Event definitions and maintain mapping for trend lines.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                                    Tools Used for Product-qualified Event<\/h2>\n\n\n\n

                                    A Product-qualified Event is not a single tool; it\u2019s a workflow across systems supporting Conversion & Measurement<\/strong> and Analytics<\/strong>. Common tool categories include:<\/p>\n\n\n\n

                                      \n
                                    • Analytics tools<\/strong>: event-based product analytics and web analytics to build funnels, cohorts, and retention views around the Product-qualified Event.<\/li>\n
                                    • Tag management and event pipelines<\/strong>: systems that standardize event collection, manage schemas, and route events to multiple destinations.<\/li>\n
                                    • Customer data platforms (CDPs) \/ identity tools<\/strong>: unify users across devices and connect anonymous sessions to known accounts.<\/li>\n
                                    • CRM systems<\/strong>: store account context and enable handoffs when a Product-qualified Event indicates sales readiness.<\/li>\n
                                    • Marketing automation tools<\/strong>: trigger lifecycle emails or in-app messaging when the event occurs.<\/li>\n
                                    • Experimentation and feature flag tools<\/strong>: test onboarding changes designed to increase the Product-qualified Event rate.<\/li>\n
                                    • Reporting dashboards \/ BI<\/strong>: unify product events with revenue data for executive-grade Conversion & Measurement<\/strong> reporting.<\/li>\n
                                    • SEO tools and content measurement<\/strong>: evaluate whether organic acquisition drives users who reach the Product-qualified Event, not just visits.<\/li>\n<\/ul>\n\n\n\n

                                      Metrics Related to Product-qualified Event<\/h2>\n\n\n\n

                                      To operationalize a Product-qualified Event, track metrics that measure both volume and quality. Useful indicators include:<\/p>\n\n\n\n

                                        \n
                                      • Product-qualified Event rate<\/strong>: percent of sign-ups or activated users who reach the event within a defined window.<\/li>\n
                                      • Time to Product-qualified Event<\/strong>: median time from sign-up to the event; a strong onboarding metric in Conversion & Measurement<\/strong>.<\/li>\n
                                      • Downstream conversion rate<\/strong>: trial-to-paid or freemium-to-paid conversion among users who hit the event vs. those who don\u2019t.<\/li>\n
                                      • Retention and expansion lift<\/strong>: difference in 30\/90-day retention or expansion revenue for qualified vs. non-qualified cohorts.<\/li>\n
                                      • Cost per product-qualified user<\/strong>: ad spend divided by number of users reaching the Product-qualified Event; more meaningful than CPA on sign-ups.<\/li>\n
                                      • Channel mix quality<\/strong>: share of product-qualified users by channel, campaign, landing page, or content cluster (SEO, paid, partnerships).<\/li>\n
                                      • Sales efficiency metrics (if applicable)<\/strong>: outreach-to-close rate for accounts that triggered an account-level Product-qualified Event.<\/li>\n<\/ul>\n\n\n\n

                                        Future Trends of Product-qualified Event<\/h2>\n\n\n\n

                                        Several trends are shaping how Product-qualified Event strategies evolve within Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

                                          \n
                                        • AI-assisted qualification<\/strong>: teams increasingly use modeling to discover which combinations of events best predict conversion or churn, complementing human-defined milestones.<\/li>\n
                                        • More automation across lifecycle<\/strong>: once a Product-qualified Event is detected, automated routing to nurture, in-app guidance, or sales sequences becomes more real-time.<\/li>\n
                                        • Deeper personalization<\/strong>: event properties enable personalized onboarding paths, feature recommendations, and content based on what a user has or hasn\u2019t done.<\/li>\n
                                        • Privacy and measurement constraints<\/strong>: as tracking becomes more restricted, first-party product events remain valuable. Analytics<\/strong> strategies will lean more on server-side tracking, consent-aware designs, and aggregated reporting.<\/li>\n
                                        • Revenue + product data unification<\/strong>: Conversion & Measurement<\/strong> reporting is moving toward blended datasets where product events, billing, and CRM outcomes are analyzed together.<\/li>\n<\/ul>\n\n\n\n

                                          Product-qualified Event vs Related Terms<\/h2>\n\n\n\n

                                          Product-qualified Event vs Product-qualified Lead (PQL)<\/h3>\n\n\n\n

                                          A Product-qualified Lead is typically a person or account deemed sales-ready based on product usage signals. A Product-qualified Event<\/strong> is the underlying behavioral milestone. In Analytics<\/strong>, you track events; in sales operations, you often convert those signals into a lead or account status.<\/p>\n\n\n\n

                                          Product-qualified Event vs Activation event<\/h3>\n\n\n\n

                                          Activation is a lifecycle stage or metric; an activation event is often the milestone used to define it. A Product-qualified Event may be the activation event, but it can also represent monetization readiness or expansion behavior. In Conversion & Measurement<\/strong>, activation events focus on initial value, while product-qualified milestones can exist later in the journey.<\/p>\n\n\n\n

                                          Product-qualified Event vs Conversion event<\/h3>\n\n\n\n

                                          A conversion event is any action you choose to count as a conversion (newsletter signup, purchase, demo request). A Product-qualified Event is specifically rooted in product usage<\/strong>, not just marketing interactions. In Analytics<\/strong>, this distinction helps separate \u201cmarketing conversions\u201d from \u201cproduct value milestones.\u201d<\/p>\n\n\n\n

                                          Who Should Learn Product-qualified Event<\/h2>\n\n\n\n
                                            \n
                                          • Marketers<\/strong>: to connect acquisition and lifecycle campaigns to real product outcomes, improving Conversion & Measurement<\/strong> credibility.<\/li>\n
                                          • Analysts<\/strong>: to define event schemas, validate predictive power, and build dashboards that link behavior to revenue in Analytics<\/strong>.<\/li>\n
                                          • Agencies<\/strong>: to prove impact beyond traffic and leads by optimizing toward product-qualified outcomes.<\/li>\n
                                          • Business owners and founders<\/strong>: to understand what truly drives conversion and retention, and to align teams on measurable product value.<\/li>\n
                                          • Developers and product teams<\/strong>: to instrument events correctly, maintain data quality, and enable experimentation tied to Product-qualified Event rates.<\/li>\n<\/ul>\n\n\n\n

                                            Summary of Product-qualified Event<\/h2>\n\n\n\n

                                            A Product-qualified Event<\/strong> is a tracked in-product action that signals a user has reached meaningful value and is more likely to convert, retain, or expand. It matters because it strengthens Conversion & Measurement<\/strong> by focusing optimization on product value\u2014where intent becomes visible. When implemented well, it becomes a reliable anchor in Analytics<\/strong> for funnels, cohorts, attribution, and lifecycle automation, helping teams invest in the channels and experiences that produce real business results.<\/p>\n\n\n\n

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

                                            1) What is a Product-qualified Event in simple terms?<\/h3>\n\n\n\n

                                            A Product-qualified Event is a specific action inside your product that indicates a user has gotten real value (or is close to paying), such as creating a first project or inviting a teammate.<\/p>\n\n\n\n

                                            2) How do I choose the right Product-qualified Event for my product?<\/h3>\n\n\n\n

                                            Start with the outcomes you care about (paid conversion, retention, expansion), then use Analytics<\/strong> to find which in-product actions strongly correlate with those outcomes. Prefer events that are meaningful, repeatable, and hard to trigger by accident.<\/p>\n\n\n\n

                                            3) Can a Product-qualified Event be different for different customer segments?<\/h3>\n\n\n\n

                                            Yes. SMB users and enterprise accounts may reach value through different paths. Many teams define a primary Product-qualified Event plus segment-specific variants, while keeping governance tight so Conversion & Measurement<\/strong> reporting stays consistent.<\/p>\n\n\n\n

                                            4) How is a Product-qualified Event used in Conversion & Measurement reporting?<\/h3>\n\n\n\n

                                            It can serve as a mid-funnel conversion point (e.g., \u201cactivated\u201d) that you optimize campaigns toward, and it can be used to calculate metrics like cost per product-qualified user and conversion lift to paid plans.<\/p>\n\n\n\n

                                            5) What if my product has a long time-to-value\u2014does Product-qualified Event still apply?<\/h3>\n\n\n\n

                                            It does, but you may need staged milestones (early engagement event, activation event, expansion readiness event). This creates a clearer Conversion & Measurement<\/strong> ladder and avoids waiting weeks for a single signal.<\/p>\n\n\n\n

                                            6) Do I need a CRM to benefit from Product-qualified Events?<\/h3>\n\n\n\n

                                            Not necessarily. You can use Product-qualified Event tracking purely for Analytics<\/strong> and lifecycle marketing. A CRM becomes more important if you route qualified accounts to sales or manage complex pipelines.<\/p>\n\n\n\n

                                            7) How often should we revisit our Product-qualified Event definition?<\/h3>\n\n\n\n

                                            Review it on a regular cadence (quarterly or biannually) or when the product changes significantly. Version changes carefully so trend lines in Analytics<\/strong> and Conversion & Measurement<\/strong> remain interpretable.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                            A **Product-qualified Event** is a measurable in-product action that signals a user has experienced meaningful value and is therefore more likely to convert, expand, or retain. In **Conversion & Measurement**, it shifts the focus from \u201cdid someone click?\u201d to \u201cdid someone reach a moment of product value?\u201d In **Analytics**, it becomes a defined event you can track, segment, attribute, and optimize across channels and lifecycle stages.<\/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":[1887],"tags":[],"class_list":["post-6916","post","type-post","status-publish","format-standard","hentry","category-analytics"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6916","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=6916"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6916\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=6916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=6916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=6916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}