{"id":7698,"date":"2026-03-24T23:02:56","date_gmt":"2026-03-24T23:02:56","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/custom-property\/"},"modified":"2026-03-24T23:02:56","modified_gmt":"2026-03-24T23:02:56","slug":"custom-property","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/custom-property\/","title":{"rendered":"Custom Property: What It Is, Key Features, Benefits, Use Cases, and How It Fits in CRM Marketing"},"content":{"rendered":"\n

A Custom Property<\/strong> is one of the simplest ideas in data-driven marketing\u2014and one of the most powerful. In Direct & Retention Marketing<\/strong>, a Custom Property is a field you create to store information about a customer, lead, account, or interaction that your default CRM or analytics schema doesn\u2019t include. In CRM Marketing<\/strong>, it\u2019s how you capture the details that make your audience unique, measurable, and actionable for segmentation, personalization, lifecycle automation, and reporting.<\/p>\n\n\n\n

Custom Property design matters because modern Direct & Retention Marketing<\/strong> is built on relevance at scale: the right message, to the right person, at the right time, on the right channel. Without the right properties, your CRM becomes a contact list instead of an intelligence engine\u2014and your campaigns default to generic blasts rather than retention-focused programs.<\/p>\n\n\n\n

What Is Custom Property?<\/h2>\n\n\n\n

A Custom Property<\/strong> is a user-defined attribute added to a marketing, CRM, or customer data system to represent information that is specific to your business model. Unlike standard fields (like email, name, country, or company size), a Custom Property reflects what you<\/em> need to know to market effectively\u2014such as \u201cpreferred category,\u201d \u201ccustomer tier,\u201d \u201ctrial start date,\u201d \u201cplan renewal month,\u201d or \u201clast support sentiment.\u201d<\/p>\n\n\n\n

The core concept is straightforward: you choose the data points that explain customer intent, value, and context, then store them in a structured way so tools can segment, trigger, and personalize experiences.<\/p>\n\n\n\n

From a business perspective, a Custom Property turns informal knowledge (\u201cthis person is a high-value customer\u201d or \u201cthey only buy in winter\u201d) into data that your Direct & Retention Marketing<\/strong> programs can use consistently.<\/p>\n\n\n\n

Inside CRM Marketing<\/strong>, Custom Property fields become the backbone for:\n– audience segmentation (who to target)\n– message tailoring (what to say)\n– timing logic (when to send)\n– performance analysis (what worked and why)<\/p>\n\n\n\n

Why Custom Property Matters in Direct & Retention Marketing<\/h2>\n\n\n\n

In Direct & Retention Marketing<\/strong>, most performance gains come from relevance, not volume. A well-chosen Custom Property<\/strong> improves relevance by letting you target based on behaviors, lifecycle stages, and preferences\u2014not just demographics.<\/p>\n\n\n\n

Strategically, Custom Property enables:\n– Lifecycle precision:<\/strong> Different rules for new users, activated users, churn risks, and loyal customers.\n– Offer alignment:<\/strong> Promotions based on what customers actually buy or use.\n– Channel coordination:<\/strong> Email, SMS, push, and in-app experiences that are consistent and context-aware.<\/p>\n\n\n\n

The business value is measurable. When CRM Marketing<\/strong> teams use Custom Property fields to refine targeting and personalization, they commonly see improvements in:\n– conversion rate and repeat purchase rate\n– retention and reactivation\n– reduced unsubscribe rates and complaint rates\n– higher customer lifetime value (CLV)<\/p>\n\n\n\n

It also creates competitive advantage. Competitors can copy your creative; they can\u2019t easily copy your data model and the operational discipline behind a strong Custom Property strategy in Direct & Retention Marketing<\/strong>.<\/p>\n\n\n\n

How Custom Property Works<\/h2>\n\n\n\n

A Custom Property<\/strong> is conceptually simple, but it becomes powerful when it flows through a practical workflow:<\/p>\n\n\n\n

    \n
  1. \n

    Input (collection or creation)<\/strong>\n – The value is captured from a form, checkout, onboarding flow, product event, customer support tool, sales notes, or enrichment process.\n – Example: \u201cIndustry = Healthcare\u201d from a lead form, or \u201cLast purchase category = Running shoes\u201d from ecommerce data.<\/p>\n<\/li>\n

  2. \n

    Processing (validation and transformation)<\/strong>\n – Values are cleaned and standardized (e.g., \u201cHealth care\u201d vs \u201cHealthcare\u201d).\n – Some Custom Property values are calculated (e.g., \u201cdays since last purchase\u201d).\n – Governance ensures the field has a single meaning and consistent allowed values.<\/p>\n<\/li>\n

  3. \n

    Execution (activation in campaigns and journeys)<\/strong>\n – CRM Marketing<\/strong> uses the Custom Property to build segments, suppression rules, and personalization tokens.\n – Direct & Retention Marketing<\/strong> automation uses it for triggers (renewal reminders, replenishment flows, win-back sequences).<\/p>\n<\/li>\n

  4. \n

    Output (measurement and optimization)<\/strong>\n – Reporting shows performance by property value (e.g., retention by \u201cplan type\u201d).\n – Insights lead to improvements in segmentation, messaging, and data quality.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

    In practice, a Custom Property is only valuable if it is reliably populated, consistently defined, and actively used.<\/p>\n\n\n\n

    Key Components of Custom Property<\/h2>\n\n\n\n

    A sustainable Custom Property<\/strong> approach in CRM Marketing<\/strong> typically includes these components:<\/p>\n\n\n\n

    Data inputs<\/h3>\n\n\n\n
      \n
    • forms (lead capture, preference center)<\/li>\n
    • transactional systems (billing, orders, subscriptions)<\/li>\n
    • product usage and event tracking<\/li>\n
    • support and feedback systems (tickets, CSAT, NPS)<\/li>\n
    • manual updates by sales or success teams<\/li>\n<\/ul>\n\n\n\n

      Systems and storage<\/h3>\n\n\n\n
        \n
      • CRM (contacts, companies, deals)<\/li>\n
      • customer data platform or data warehouse (optional but helpful)<\/li>\n
      • marketing automation and messaging platforms<\/li>\n<\/ul>\n\n\n\n

        Processes and responsibilities<\/h3>\n\n\n\n
          \n
        • Data stewardship:<\/strong> who can create\/modify a Custom Property, and when<\/li>\n
        • Schema documentation:<\/strong> definitions, allowed values, owner, and usage examples<\/li>\n
        • Change control:<\/strong> what happens when a property is renamed, merged, or deprecated<\/li>\n<\/ul>\n\n\n\n

          Governance and quality checks<\/h3>\n\n\n\n
            \n
          • validation rules (formats, enums, required fields)<\/li>\n
          • monitoring for null rates and unexpected values<\/li>\n
          • periodic audits to remove unused or duplicate properties<\/li>\n<\/ul>\n\n\n\n

            Metrics and reporting layer<\/h3>\n\n\n\n
              \n
            • dashboards segmented by Custom Property values<\/li>\n
            • cohort analysis tied to lifecycle properties<\/li>\n
            • deliverability and engagement reporting by preference properties<\/li>\n<\/ul>\n\n\n\n

              Types of Custom Property<\/h2>\n\n\n\n

              \u201cTypes\u201d can mean different things depending on the system, but these distinctions are the most useful across Direct & Retention Marketing<\/strong> and CRM Marketing<\/strong>:<\/p>\n\n\n\n

              By object level (what the property describes)<\/h3>\n\n\n\n
                \n
              • Contact\/Lead properties:<\/strong> attributes about a person (role, preferences, lifecycle stage)<\/li>\n
              • Account\/Company properties:<\/strong> attributes about an organization (industry, revenue band)<\/li>\n
              • Transaction\/Order properties:<\/strong> purchase details (AOV band, last SKU category)<\/li>\n
              • Subscription properties:<\/strong> plan type, renewal date, billing cadence<\/li>\n
              • Event\/Behavior properties:<\/strong> last feature used, sessions in last 7 days<\/li>\n<\/ul>\n\n\n\n

                By origin (how the property is produced)<\/h3>\n\n\n\n
                  \n
                • Collected properties:<\/strong> captured directly from user input or system events<\/li>\n
                • Derived properties:<\/strong> computed from other fields (e.g., \u201cVIP = true if spend > $500\u201d)<\/li>\n
                • Enriched properties:<\/strong> appended via internal or partner data (used carefully due to privacy and accuracy concerns)<\/li>\n<\/ul>\n\n\n\n

                  By structure (how values are stored)<\/h3>\n\n\n\n
                    \n
                  • Single-select (enumerated):<\/strong> best for stable categories (e.g., tier: bronze\/silver\/gold)<\/li>\n
                  • Multi-select:<\/strong> preferences that can be multiple (e.g., interest categories)<\/li>\n
                  • Numeric\/date:<\/strong> ideal for scoring, recency, renewal logic<\/li>\n
                  • Text:<\/strong> flexible, but often harder to govern and report on consistently<\/li>\n<\/ul>\n\n\n\n

                    Real-World Examples of Custom Property<\/h2>\n\n\n\n

                    Example 1: Ecommerce retention and replenishment<\/h3>\n\n\n\n

                    A retailer adds Custom Property<\/strong> fields like \u201cpreferred category,\u201d \u201clast purchased size,\u201d and \u201cpurchase frequency band.\u201d In Direct & Retention Marketing<\/strong>, they trigger replenishment emails based on frequency and personalize recommendations using category and size. In CRM Marketing<\/strong>, they analyze repeat rate and unsubscribe rate by frequency band to avoid over-mailing infrequent buyers.<\/p>\n\n\n\n

                    Example 2: SaaS onboarding and expansion<\/h3>\n\n\n\n

                    A SaaS team tracks Custom Property values such as \u201cactivation milestone reached,\u201d \u201ckey feature adopted,\u201d and \u201cseats purchased.\u201d Their Direct & Retention Marketing<\/strong> journeys send help content until a milestone is reached, then shift to expansion prompts based on feature adoption. In CRM Marketing<\/strong>, they measure trial-to-paid conversion by milestone status and prioritize lifecycle improvements.<\/p>\n\n\n\n

                    Example 3: B2B lead routing and nurture relevance<\/h3>\n\n\n\n

                    A B2B organization defines Custom Property fields like \u201cprimary use case,\u201d \u201cimplementation timeframe,\u201d and \u201ccompliance requirement.\u201d These properties tailor nurture streams and route leads to the right teams. Direct & Retention Marketing<\/strong> benefits because follow-ups are timely and context-aware, while CRM Marketing<\/strong> gains clearer attribution and better pipeline quality reporting by use case.<\/p>\n\n\n\n

                    Benefits of Using Custom Property<\/h2>\n\n\n\n

                    When implemented well, Custom Property<\/strong> fields create compounding returns:<\/p>\n\n\n\n

                      \n
                    • Higher campaign performance:<\/strong> better segmentation typically increases conversion and reduces fatigue.<\/li>\n
                    • Lower costs:<\/strong> fewer wasted sends and fewer irrelevant paid retargeting impressions when audiences are cleaner.<\/li>\n
                    • Operational efficiency:<\/strong> teams stop rebuilding one-off lists and instead reuse standardized properties.<\/li>\n
                    • Better customer experience:<\/strong> messaging aligns with preferences and lifecycle, which improves trust and engagement.<\/li>\n
                    • More reliable reporting:<\/strong> CRM Marketing<\/strong> can compare cohorts and outcomes using consistent definitions rather than ad hoc filters.<\/li>\n<\/ul>\n\n\n\n

                      In Direct & Retention Marketing<\/strong>, the biggest benefit is durable personalization\u2014built on data that reflects real customer context.<\/p>\n\n\n\n

                      Challenges of Custom Property<\/h2>\n\n\n\n

                      A Custom Property<\/strong> strategy can fail for predictable reasons:<\/p>\n\n\n\n

                        \n
                      • Schema sprawl:<\/strong> too many fields, duplicates, or unclear naming conventions make the CRM hard to use.<\/li>\n
                      • Inconsistent values:<\/strong> free-text entries and unstandardized labels break segmentation and reporting.<\/li>\n
                      • Low data completeness:<\/strong> properties exist but are rarely populated, creating false confidence.<\/li>\n
                      • Misaligned ownership:<\/strong> marketing creates fields but sales\/support own the inputs, or vice versa.<\/li>\n
                      • Privacy and consent risk:<\/strong> collecting sensitive attributes without clear purpose, consent, or retention policies can create compliance exposure.<\/li>\n
                      • Measurement gaps:<\/strong> if properties aren\u2019t passed through to reporting systems, CRM Marketing<\/strong> can\u2019t prove impact.<\/li>\n<\/ul>\n\n\n\n

                        The most common issue in Direct & Retention Marketing<\/strong> is building journeys that rely on a Custom Property that isn\u2019t reliably updated.<\/p>\n\n\n\n

                        Best Practices for Custom Property<\/h2>\n\n\n\n

                        Design for action, not curiosity<\/h3>\n\n\n\n

                        Only create a Custom Property<\/strong> if you can name at least one of these:\n– the segment it enables\n– the trigger it powers\n– the personalization it improves\n– the report it will be used in<\/p>\n\n\n\n

                        Use consistent naming and definitions<\/h3>\n\n\n\n

                        Adopt conventions like:\n– lifecycle_stage<\/code>, preferred_category<\/code>, renewal_date<\/code>\n– avoid ambiguous names like status<\/code> or type<\/code>\nDocument each Custom Property with definition, allowed values, owner, and where it\u2019s populated.<\/p>\n\n\n\n

                        Prefer enumerated values over free text<\/h3>\n\n\n\n

                        Single-select options are easier to govern and analyze in CRM Marketing<\/strong>. If free text is unavoidable, add normalization rules downstream.<\/p>\n\n\n\n

                        Build data quality monitoring<\/h3>\n\n\n\n

                        Track:\n– null rate by property\n– top values and \u201cunknown\/other\u201d\n– value drift over time\nThis is essential for stable Direct & Retention Marketing<\/strong> automation.<\/p>\n\n\n\n

                        Plan for lifecycle changes<\/h3>\n\n\n\n

                        Customers change. Ensure your Custom Property model supports updates (e.g., preference changes) and doesn\u2019t lock people into stale segments.<\/p>\n\n\n\n

                        Treat deprecation as normal<\/h3>\n\n\n\n

                        Retire unused or redundant properties quarterly. Map old fields to new ones to protect reporting and automations.<\/p>\n\n\n\n

                        Tools Used for Custom Property<\/h2>\n\n\n\n

                        You don\u2019t need a specific vendor to use Custom Property<\/strong> fields, but most teams rely on a stack that includes:<\/p>\n\n\n\n

                          \n
                        • CRM systems:<\/strong> store contact\/account properties and support sales-to-marketing alignment for CRM Marketing<\/strong>.<\/li>\n
                        • Marketing automation tools:<\/strong> use Custom Property values in segments, journeys, suppression, and personalization for Direct & Retention Marketing<\/strong>.<\/li>\n
                        • Analytics tools:<\/strong> connect behavioral events to user profiles, enabling derived properties like recency or feature adoption.<\/li>\n
                        • Data warehouses and ELT\/ETL pipelines:<\/strong> centralize data definitions, compute derived properties, and support advanced cohort reporting.<\/li>\n
                        • Reporting dashboards\/BI tools:<\/strong> visualize outcomes by Custom Property values (retention by tier, conversion by use case).<\/li>\n
                        • Consent and preference management systems:<\/strong> ensure preference-related properties are captured lawfully and applied consistently across channels.<\/li>\n<\/ul>\n\n\n\n

                          The key is integration: a Custom Property is only useful if it flows to the systems that execute and measure Direct & Retention Marketing<\/strong> and CRM Marketing<\/strong> outcomes.<\/p>\n\n\n\n

                          Metrics Related to Custom Property<\/h2>\n\n\n\n

                          Custom Property success isn\u2019t a single KPI; it\u2019s a combination of data quality and marketing impact metrics:<\/p>\n\n\n\n

                          Data quality metrics<\/h3>\n\n\n\n
                            \n
                          • Population rate:<\/strong> % of records with the property filled<\/li>\n
                          • Validity rate:<\/strong> % of values that match allowed formats\/options<\/li>\n
                          • Freshness:<\/strong> how recently the property was updated<\/li>\n
                          • Uniqueness\/duplication:<\/strong> whether multiple properties represent the same concept<\/li>\n<\/ul>\n\n\n\n

                            Campaign and lifecycle performance metrics<\/h3>\n\n\n\n
                              \n
                            • conversion rate by segment\/property value<\/li>\n
                            • retention rate, churn rate, and reactivation rate by cohort<\/li>\n
                            • revenue per recipient, CLV by tier\/use case<\/li>\n
                            • email\/SMS engagement (open\/click where applicable, CTR, reply rate)<\/li>\n
                            • deliverability indicators (bounce, complaint rate) by preference properties<\/li>\n<\/ul>\n\n\n\n

                              In CRM Marketing<\/strong>, the best indicator is whether reporting and decision-making meaningfully improve because the Custom Property exists.<\/p>\n\n\n\n

                              Future Trends of Custom Property<\/h2>\n\n\n\n

                              Several trends are reshaping how Custom Property<\/strong> is used in Direct & Retention Marketing<\/strong>:<\/p>\n\n\n\n

                                \n
                              • First-party data becomes central:<\/strong> as tracking constraints increase, teams lean more on CRM-held properties collected via direct relationships.<\/li>\n
                              • AI-assisted segmentation and scoring:<\/strong> AI can recommend new derived properties (propensity, predicted churn) but governance remains essential to avoid opaque or biased fields.<\/li>\n
                              • Real-time personalization:<\/strong> streaming events update properties quickly (e.g., \u201ccurrently browsing category\u201d), enabling faster journey branching.<\/li>\n
                              • Privacy-by-design schemas:<\/strong> fewer sensitive properties, clearer consent mapping, shorter retention windows, and more purpose limitation.<\/li>\n
                              • Composable data stacks:<\/strong> more teams compute derived Custom Property values in a warehouse and sync them back to CRM Marketing<\/strong> tools for activation.<\/li>\n<\/ul>\n\n\n\n

                                The direction is clear: Custom Property strategy is evolving from \u201cadd a field\u201d to \u201cbuild an operational data product\u201d for Direct & Retention Marketing<\/strong>.<\/p>\n\n\n\n

                                Custom Property vs Related Terms<\/h2>\n\n\n\n

                                Custom Property vs Standard Property<\/h3>\n\n\n\n

                                A standard property is provided by default (email, created date). A Custom Property<\/strong> is created by your team to match your business. Standard properties are universally understood; custom ones require documentation and governance.<\/p>\n\n\n\n

                                Custom Property vs Tag<\/h3>\n\n\n\n

                                Tags are often flexible labels used for quick grouping. A Custom Property is typically more structured (type, allowed values, validation) and is better for consistent CRM Marketing<\/strong> reporting. Tags can be useful, but they can become messy without rules.<\/p>\n\n\n\n

                                Custom Property vs Custom Dimension \/ Event Parameter<\/h3>\n\n\n\n

                                Custom dimensions and event parameters are common in analytics for describing events or users. A Custom Property<\/strong> usually refers to a CRM\/profile attribute used for activation. In mature Direct & Retention Marketing<\/strong>, teams often connect the two: event parameters inform derived properties (e.g., \u201clast feature used\u201d).<\/p>\n\n\n\n

                                Who Should Learn Custom Property<\/h2>\n\n\n\n
                                  \n
                                • Marketers:<\/strong> to build precise segments, personalization, and lifecycle automation in Direct & Retention Marketing<\/strong>.<\/li>\n
                                • Analysts:<\/strong> to define clean metrics, cohorts, and reports that explain performance drivers in CRM Marketing<\/strong>.<\/li>\n
                                • Agencies:<\/strong> to standardize client implementations and avoid brittle, one-off campaign logic.<\/li>\n
                                • Business owners and founders:<\/strong> to understand what customer data to capture early so retention and monetization improve over time.<\/li>\n
                                • Developers and data engineers:<\/strong> to implement reliable collection, transformation, and syncing that keeps Custom Property values accurate and usable.<\/li>\n<\/ul>\n\n\n\n

                                  Anyone responsible for growth, retention, or customer communications benefits from understanding Custom Property fundamentals.<\/p>\n\n\n\n

                                  Summary of Custom Property<\/h2>\n\n\n\n

                                  A Custom Property<\/strong> is a user-defined field that stores meaningful customer, account, or behavior data beyond default system fields. It matters because Direct & Retention Marketing<\/strong> depends on accurate segmentation, triggers, and personalization\u2014capabilities that require the right data attributes. Within CRM Marketing<\/strong>, Custom Property fields power lifecycle reporting, automation logic, and performance analysis. When designed with governance and clear use cases, they turn customer data into repeatable growth and retention outcomes.<\/p>\n\n\n\n

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

                                  1) What is a Custom Property and when should I create one?<\/h3>\n\n\n\n

                                  A Custom Property<\/strong> is a custom field that represents a business-specific attribute you want to use for segmentation, personalization, automation, or reporting. Create one when you can clearly state how it will be used in Direct & Retention Marketing<\/strong> (journeys, targeting, suppression) or in CRM Marketing<\/strong> reporting.<\/p>\n\n\n\n

                                  2) How many Custom Property fields is too many?<\/h3>\n\n\n\n

                                  There\u2019s no universal number, but \u201ctoo many\u201d is when teams can\u2019t find the right field, values become inconsistent, or properties are rarely used. A smaller set of well-governed, widely adopted Custom Property fields usually outperforms a large, messy schema.<\/p>\n\n\n\n

                                  3) Should Custom Property values be free text or standardized options?<\/h3>\n\n\n\n

                                  Use standardized options (single-select) whenever possible because they are easier to segment and report on in CRM Marketing<\/strong>. Free text is harder to analyze and often creates duplicates (e.g., \u201cUSA,\u201d \u201cUS,\u201d \u201cUnited States\u201d).<\/p>\n\n\n\n

                                  4) How does Custom Property help CRM Marketing specifically?<\/h3>\n\n\n\n

                                  In CRM Marketing<\/strong>, Custom Property fields enable consistent lifecycle definitions, cohort reporting, and attribution analysis. They also improve audience quality by making segmentation rules clear, repeatable, and measurable.<\/p>\n\n\n\n

                                  5) What\u2019s the difference between a Custom Property and a segment?<\/h3>\n\n\n\n

                                  A Custom Property<\/strong> is a data field (an attribute). A segment is a group of records defined by rules, often using one or more Custom Property values (e.g., \u201ctier = gold\u201d and \u201cdays since purchase < 30\u201d).<\/p>\n\n\n\n

                                  6) What are common data quality checks for Custom Property?<\/h3>\n\n\n\n

                                  Track population rate, validity rate (allowed values), freshness (last updated), and drift (new unexpected values). These checks keep Direct & Retention Marketing<\/strong> automations from breaking due to missing or inconsistent data.<\/p>\n\n\n\n

                                  7) Can Custom Property fields support personalization across channels?<\/h3>\n\n\n\n

                                  Yes. If your messaging tools have access to the Custom Property, you can personalize email, SMS, push, and in-app content consistently\u2014an essential capability for scalable Direct & Retention Marketing<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                  A **Custom Property** is one of the simplest ideas in data-driven marketing\u2014and one of the most powerful. In **Direct & Retention Marketing**, a Custom Property is a field you create to store information about a customer, lead, account, or interaction that your default CRM or analytics schema doesn\u2019t include. In **CRM Marketing**, it\u2019s how you capture the details that make your audience unique, measurable, and actionable for segmentation, personalization, lifecycle automation, and reporting.<\/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":[1893],"tags":[],"class_list":["post-7698","post","type-post","status-publish","format-standard","hentry","category-crm-marketing"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7698","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=7698"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7698\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7698"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7698"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7698"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}