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

A Contact Property<\/strong> is a single piece of information stored about an individual contact in your customer database\u2014such as email address, lifecycle stage, last purchase date, consent status, or product interest. In Direct & Retention Marketing<\/strong>, these properties are the levers that turn generic outreach into timely, relevant messages across email, SMS, push, and other owned channels. In CRM Marketing<\/strong>, they act as the structured profile data that makes segmentation, automation, and measurement possible.<\/p>\n\n\n\n

As acquisition costs rise and privacy reduces easy third\u2011party targeting, modern Direct & Retention Marketing<\/strong> increasingly depends on first\u2011party data you can trust. A well-designed Contact Property<\/strong> model helps teams personalize at scale, coordinate across channels, and prove ROI\u2014without relying on guesswork or brittle spreadsheets.<\/p>\n\n\n\n

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

A Contact Property<\/strong> is a named field tied to a person\u2019s record in a CRM or marketing database. Think of it as \u201cprofile data\u201d that describes who a contact is, what they\u2019ve done, what they prefer, and what they\u2019re eligible to receive. Unlike one-off notes, a Contact Property is structured so systems can filter, trigger, and personalize communications automatically.<\/p>\n\n\n\n

At its core, the concept is simple: store consistent, queryable facts about each contact<\/strong>. The business meaning is bigger: these facts determine eligibility (can we message them?), relevance (what should we say?), and timing (when should we say it?).<\/p>\n\n\n\n

Where it fits in Direct & Retention Marketing<\/strong>:\n– Powers segmentation (e.g., \u201cVIP customers in the UK who opted into SMS\u201d)\n– Fuels automation triggers (e.g., \u201cabandoned cart\u201d or \u201crenewal due\u201d)\n– Enables personalization tokens (e.g., first name, plan type, renewal date)<\/p>\n\n\n\n

Its role inside CRM Marketing<\/strong> is foundational: most journeys, reports, and lifecycle programs depend on reliable Contact Property values to function correctly.<\/p>\n\n\n\n

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

In Direct & Retention Marketing<\/strong>, the difference between \u201cnoise\u201d and \u201cvalue\u201d is often a handful of fields stored on the contact record. A strong Contact Property strategy creates measurable business advantages:<\/p>\n\n\n\n

    \n
  • Higher relevance, higher engagement:<\/strong> When you target based on accurate properties (plan tier, last activity, preferences), open and click rates generally improve because messages match intent.<\/li>\n
  • Better lifecycle orchestration:<\/strong> Properties like lifecycle stage, onboarding status, and renewal date allow CRM Marketing<\/strong> teams to coordinate sequences without manual work.<\/li>\n
  • Lower operational cost:<\/strong> Clean, standardized properties reduce time spent exporting lists, fixing errors, and rebuilding segments.<\/li>\n
  • Competitive advantage through speed:<\/strong> Teams that can confidently launch segments and journeys faster will test more, learn more, and improve retention.<\/li>\n<\/ul>\n\n\n\n

    Most importantly, Contact Property quality becomes a compounding asset: every campaign and customer interaction can enrich the record and improve future Direct & Retention Marketing<\/strong> performance.<\/p>\n\n\n\n

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

    A Contact Property<\/strong> is more practical than theoretical. In real operations, it \u201cworks\u201d as an always-available input for targeting, personalization, and automation.<\/p>\n\n\n\n

      \n
    1. \n

      Input or trigger (data creation)<\/strong>\n – A user submits a form (country, role)\n – A purchase happens (last order date, total spend)\n – A product event fires (feature used, last login)\n – A preference is set (email frequency, categories)\n – Consent is captured or updated (opt-in timestamp)<\/p>\n<\/li>\n

    2. \n

      Processing (validation and rules)<\/strong>\n – Normalize values (e.g., \u201cUnited States\u201d vs \u201cUS\u201d)\n – Apply rules (e.g., set lifecycle stage to \u201cCustomer\u201d after first paid invoice)\n – Resolve identity (merge duplicates; choose system of record)\n – Enforce governance (required fields, allowed values)<\/p>\n<\/li>\n

    3. \n

      Execution (marketing application)<\/strong>\n – Segment contacts (filters using properties)\n – Trigger journeys (if\/then based on property changes)\n – Personalize content (dynamic blocks and tokens)\n – Suppress messages (exclude unsubscribed or ineligible contacts)<\/p>\n<\/li>\n

    4. \n

      Output (outcome)<\/strong>\n – Better engagement and conversion\n – Reduced churn through timely retention flows\n – More accurate reporting for CRM Marketing<\/strong>\n – Improved customer experience across Direct & Retention Marketing<\/strong> channels<\/p>\n<\/li>\n<\/ol>\n\n\n\n

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

      A durable Contact Property framework includes more than fields in a database. The most effective programs align data, systems, process, and accountability.<\/p>\n\n\n\n

      Core elements<\/h3>\n\n\n\n
        \n
      • Data model and naming conventions:<\/strong> Clear definitions (what it means, format, allowed values).<\/li>\n
      • Data sources:<\/strong> Web forms, product analytics, billing systems, support tools, point-of-sale, and surveys.<\/li>\n
      • Identity resolution:<\/strong> Matching rules to connect events and purchases to the correct person.<\/li>\n
      • Governance and ownership:<\/strong> Who creates, approves, and maintains properties; how changes are documented.<\/li>\n
      • Quality controls:<\/strong> Validation rules, deduplication processes, and regular audits.<\/li>\n
      • Activation pathways:<\/strong> Where properties can be used\u2014segments, journeys, personalization, and suppression.<\/li>\n
      • Security and compliance:<\/strong> Permissioning, retention policies, and consent handling that support compliant CRM Marketing<\/strong>.<\/li>\n<\/ul>\n\n\n\n

        Team responsibilities<\/h3>\n\n\n\n
          \n
        • Marketing defines use cases and required fields.<\/li>\n
        • Data\/engineering ensures reliable pipelines and standards.<\/li>\n
        • CRM ops manages field hygiene, documentation, and lifecycle logic.<\/li>\n
        • Legal\/privacy ensures consent-related properties are collected and used appropriately.<\/li>\n<\/ul>\n\n\n\n

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

          \u201cTypes\u201d aren\u2019t always formalized the same way across platforms, but these distinctions are highly practical in Direct & Retention Marketing<\/strong> and CRM Marketing<\/strong>:<\/p>\n\n\n\n

            \n
          1. \n

            Identity properties<\/strong>\n – Email, phone number, customer ID, device ID (where appropriate)\n – Used for matching, deduping, and deliverability<\/p>\n<\/li>\n

          2. \n

            Demographic and firmographic properties<\/strong>\n – Country, language, age range; or company size\/industry (B2B)\n – Useful for localization and persona-based messaging<\/p>\n<\/li>\n

          3. \n

            Behavioral properties<\/strong>\n – Last login date, last site visit, feature usage tier\n – Drives engagement-based triggers and reactivation flows<\/p>\n<\/li>\n

          4. \n

            Transactional properties<\/strong>\n – Last purchase date, order count, total spend, subscription status\n – Essential for revenue-based segmentation and retention programs<\/p>\n<\/li>\n

          5. \n

            Preference properties<\/strong>\n – Product interests, content topics, channel preference, frequency preference\n – Enables respectful personalization and reduces fatigue<\/p>\n<\/li>\n

          6. \n

            Consent and compliance properties<\/strong>\n – Opt-in status per channel, source, timestamp, lawful basis (where needed)\n – Critical for compliant Direct & Retention Marketing<\/strong><\/p>\n<\/li>\n

          7. \n

            Derived or computed properties<\/strong>\n – Lead score, RFM segment, predicted churn risk (when available)\n – Created via rules or models to simplify activation in CRM Marketing<\/strong><\/p>\n<\/li>\n<\/ol>\n\n\n\n

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

            Example 1: Win-back sequence for lapsed customers<\/h3>\n\n\n\n

            A retail brand sets a Contact Property called \u201cdays_since_last_purchase\u201d and another called \u201cpreferred_category.\u201d When \u201cdays_since_last_purchase\u201d exceeds 90, Direct & Retention Marketing<\/strong> automation enrolls the contact into a win-back journey. Email content uses \u201cpreferred_category\u201d to display relevant products, while suppression rules exclude anyone whose consent status indicates they opted out. This is classic CRM Marketing<\/strong>: lifecycle + personalization + compliance.<\/p>\n\n\n\n

            Example 2: B2B onboarding based on role and activation<\/h3>\n\n\n\n

            A SaaS company stores \u201cjob_role\u201d from a signup form and \u201cactivated_feature_X\u201d from product events as Contact Property values. If \u201cjob_role = Admin\u201d and \u201cactivated_feature_X = false\u201d after 7 days, a targeted onboarding email explains setup steps and invites a guided webinar. If the feature becomes true, the journey pivots to advanced tips. This improves time-to-value and reduces early churn in Direct & Retention Marketing<\/strong> programs.<\/p>\n\n\n\n

            Example 3: Multichannel preference-driven messaging<\/h3>\n\n\n\n

            A subscription service records \u201csms_opt_in,\u201d \u201cemail_opt_in,\u201d and \u201cmessage_frequency.\u201d Customers who choose \u201cweekly\u201d receive a digest email, while \u201creal-time\u201d customers receive push notifications for account events. The Contact Property set prevents over-messaging, keeps channel use compliant, and makes CRM Marketing<\/strong> reporting clearer because messaging aligns to declared preferences.<\/p>\n\n\n\n

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

            A strong Contact Property practice creates benefits that show up in both performance and operations:<\/p>\n\n\n\n

              \n
            • Higher conversion and retention:<\/strong> Better targeting and timing improve downstream revenue metrics.<\/li>\n
            • Lower messaging waste:<\/strong> Suppression and eligibility properties reduce sends to uninterested or ineligible audiences.<\/li>\n
            • Faster campaign execution:<\/strong> Teams reuse standard segments instead of rebuilding lists each time.<\/li>\n
            • More consistent customer experience:<\/strong> Customers see coherent messaging across email, SMS, and in-app\u2014key to Direct & Retention Marketing<\/strong> trust.<\/li>\n
            • Improved measurement:<\/strong> Properties enable clean cohorting (e.g., by plan, region, lifecycle stage), strengthening CRM Marketing<\/strong> attribution and learning loops.<\/li>\n<\/ul>\n\n\n\n

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

              Contact properties also introduce real risks when managed casually:<\/p>\n\n\n\n

                \n
              • Data quality issues:<\/strong> Missing values, inconsistent formats, and outdated fields lead to broken segments and irrelevant personalization.<\/li>\n
              • Duplicate contacts and identity conflicts:<\/strong> Multiple records for the same person can cause double-sends or incorrect lifecycle status.<\/li>\n
              • Over-collection and privacy risk:<\/strong> Capturing more than you need increases compliance burden and security exposure\u2014especially in Direct & Retention Marketing<\/strong>.<\/li>\n
              • Misleading \u201csingle source of truth\u201d:<\/strong> Different systems may disagree (billing vs product vs CRM), requiring clear ownership and reconciliation rules.<\/li>\n
              • Change management:<\/strong> Renaming or repurposing a Contact Property can silently break automations and dashboards in CRM Marketing<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                Best Practices for Contact Property<\/h2>\n\n\n\n
                  \n
                1. \n

                  Start from use cases, not curiosity<\/strong>\n – Define what segmentation or automation you need, then map the minimum properties required.<\/p>\n<\/li>\n

                2. \n

                  Document every Contact Property<\/strong>\n – Include definition, format, allowed values, source system, update frequency, and owner.<\/p>\n<\/li>\n

                3. \n

                  Standardize naming and values<\/strong>\n – Use consistent conventions (snake_case or camelCase) and controlled lists for categorical fields.<\/p>\n<\/li>\n

                4. \n

                  Separate raw vs derived fields<\/strong>\n – Keep original inputs (raw) and add computed properties (derived) to avoid losing detail.<\/p>\n<\/li>\n

                5. \n

                  Implement lifecycle logic carefully<\/strong>\n – Properties like \u201clifecycle_stage\u201d should have explicit rules, conflict resolution, and audit trails to support trustworthy CRM Marketing<\/strong>.<\/p>\n<\/li>\n

                6. \n

                  Build privacy and consent into the model<\/strong>\n – Store channel-level consent and timestamps; use them for suppression in every Direct & Retention Marketing<\/strong> workflow.<\/p>\n<\/li>\n

                7. \n

                  Monitor drift and decay<\/strong>\n – Audit critical properties monthly\/quarterly: fill rates, invalid values, and last-updated recency.<\/p>\n<\/li>\n

                8. \n

                  Design for scalability<\/strong>\n – Prefer a smaller set of high-quality properties over an uncontrolled sprawl of near-duplicates.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

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

                  You don\u2019t \u201cbuy\u201d a Contact Property\u2014your stack manages and activates it. Common tool categories include:<\/p>\n\n\n\n

                    \n
                  • CRM systems:<\/strong> Store contact records, field definitions, lifecycle stages, and ownership.<\/li>\n
                  • Marketing automation platforms:<\/strong> Use Contact Property values for journeys, branching logic, suppression, and personalization in Direct & Retention Marketing<\/strong>.<\/li>\n
                  • Customer data platforms (CDPs) and data integration tools:<\/strong> Ingest events, unify identities, and sync properties between systems for consistent CRM Marketing<\/strong> activation.<\/li>\n
                  • Product analytics and event tracking tools:<\/strong> Generate behavioral inputs that become properties (last activity, feature adoption).<\/li>\n
                  • Data warehouses and transformation tools:<\/strong> Centralize data, compute derived fields (RFM, LTV), and govern definitions.<\/li>\n
                  • Reporting dashboards \/ BI tools:<\/strong> Visualize cohorts and performance by property values.<\/li>\n
                  • Data quality and monitoring tools:<\/strong> Track anomalies, missing values, and pipeline breakages.<\/li>\n<\/ul>\n\n\n\n

                    The key is alignment: your tools must agree on definitions and syncing rules, or Contact Property values become unreliable.<\/p>\n\n\n\n

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

                    To evaluate Contact Property health and impact, track metrics in two groups: data quality and marketing outcomes.<\/p>\n\n\n\n

                    Data quality metrics<\/h3>\n\n\n\n
                      \n
                    • Fill rate (completeness):<\/strong> % of contacts with a non-null value for a critical property<\/li>\n
                    • Validity rate:<\/strong> % of values matching allowed formats (e.g., country codes)<\/li>\n
                    • Freshness\/recency:<\/strong> how recently properties were updated (especially behavioral fields)<\/li>\n
                    • Duplicate rate:<\/strong> % of contacts likely representing the same person<\/li>\n
                    • Sync success rate:<\/strong> % of updates successfully propagated across systems<\/li>\n<\/ul>\n\n\n\n

                      Direct & Retention Marketing<\/strong> performance metrics influenced by properties<\/h3>\n\n\n\n
                        \n
                      • Segment-level open\/click rates<\/strong> and conversion rate<\/strong><\/li>\n
                      • Unsubscribe\/spam complaint rate<\/strong> (often improves with better targeting)<\/li>\n
                      • Revenue per recipient<\/strong> \/ incremental revenue<\/strong> by cohort<\/li>\n
                      • Retention rate<\/strong> and churn rate<\/strong> by lifecycle stage or plan<\/li>\n
                      • Time-to-first-value<\/strong> for onboarding programs (SaaS)<\/li>\n<\/ul>\n\n\n\n

                        These help CRM Marketing<\/strong> teams connect data model investments to measurable outcomes.<\/p>\n\n\n\n

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

                        Several trends are reshaping how Contact Property strategies evolve within Direct & Retention Marketing<\/strong>:<\/p>\n\n\n\n

                          \n
                        • AI-assisted segmentation and personalization:<\/strong> Models can recommend audiences or content, but they still depend on high-quality properties and clear definitions.<\/li>\n
                        • More real-time updates:<\/strong> Businesses are moving from nightly syncs to event-driven updates so journeys can respond immediately to behavior.<\/li>\n
                        • Privacy-first design:<\/strong> Expect greater emphasis on consent properties, data minimization, and configurable retention windows.<\/li>\n
                        • Preference-centric marketing:<\/strong> More brands will treat preferences as first-class properties to reduce fatigue and improve trust.<\/li>\n
                        • From static fields to \u201cprofile + events\u201d:<\/strong> Teams will combine Contact Property profiles with event streams for richer CRM Marketing<\/strong> decisioning, while keeping activation simple through derived fields.<\/li>\n<\/ul>\n\n\n\n

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

                          Contact Property vs Event Property<\/h3>\n\n\n\n
                            \n
                          • A Contact Property<\/strong> is persistent profile data tied to a person (e.g., \u201cplan_tier\u201d).<\/li>\n
                          • An event property<\/strong> describes a specific action (e.g., \u201cbutton_color\u201d on a click event).\nIn Direct & Retention Marketing<\/strong>, you often convert event signals into stable Contact Property values like \u201clast_clicked_date.\u201d<\/li>\n<\/ul>\n\n\n\n

                            Contact Property vs Account\/Company Property<\/h3>\n\n\n\n
                              \n
                            • A Contact Property applies to an individual.<\/li>\n
                            • An account\/company property applies to an organization (industry, ARR, employee count).\nIn B2B CRM Marketing<\/strong>, both matter: you might target contacts based on company tier plus individual role.<\/li>\n<\/ul>\n\n\n\n

                              Contact Property vs Custom Field<\/h3>\n\n\n\n

                              \u201cCustom field\u201d is a generic term for a user-created field in a system. A Contact Property is the same idea, but specifically scoped to the contact profile and used broadly for segmentation, personalization, and automation in Direct & Retention Marketing<\/strong>.<\/p>\n\n\n\n

                              Who Should Learn Contact Property<\/h2>\n\n\n\n
                                \n
                              • Marketers:<\/strong> To build segments, personalization, and lifecycle programs that perform consistently in Direct & Retention Marketing<\/strong>.<\/li>\n
                              • CRM and lifecycle specialists:<\/strong> To design scalable journeys and ensure CRM Marketing<\/strong> operations remain reliable as the database grows.<\/li>\n
                              • Analysts:<\/strong> To define cohorts, validate data quality, and measure how properties correlate with retention and revenue.<\/li>\n
                              • Agencies and consultants:<\/strong> To audit client stacks, fix deliverability\/segmentation issues, and create repeatable growth systems.<\/li>\n
                              • Business owners and founders:<\/strong> To understand what data is required for retention growth and where to invest.<\/li>\n
                              • Developers and data engineers:<\/strong> To implement event tracking, identity resolution, and syncing so Contact Property values are accurate and timely.<\/li>\n<\/ul>\n\n\n\n

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

                                A Contact Property<\/strong> is a structured field on a person\u2019s record that describes identity, behavior, transactions, preferences, or consent. It matters because it\u2019s the core mechanism that enables segmentation, personalization, automation, and suppression across Direct & Retention Marketing<\/strong> channels. Within CRM Marketing<\/strong>, contact properties provide the profile layer that makes lifecycle programs measurable, scalable, and compliant.<\/p>\n\n\n\n

                                When defined clearly, governed well, and kept accurate, Contact Property data becomes a durable competitive advantage\u2014powering better customer experiences and stronger retention outcomes.<\/p>\n\n\n\n

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

                                1) What is a Contact Property in practical terms?<\/h3>\n\n\n\n

                                A Contact Property is a specific field on a contact record\u2014like \u201ccountry,\u201d \u201clifecycle_stage,\u201d or \u201clast_purchase_date\u201d\u2014that can be used to segment audiences, trigger automations, and personalize messages.<\/p>\n\n\n\n

                                2) How many contact properties should a business have?<\/h3>\n\n\n\n

                                Enough to support your Direct & Retention Marketing<\/strong> use cases, but not so many that quality declines. Many teams succeed with a small \u201ccore set\u201d (identity, consent, lifecycle, key behavioral and transactional fields) plus a controlled process for adding new ones.<\/p>\n\n\n\n

                                3) How does Contact Property data improve CRM Marketing performance?<\/h3>\n\n\n\n

                                In CRM Marketing<\/strong>, properties make automation and reporting reliable. You can build stable cohorts (by plan, stage, region), personalize content, and measure retention or revenue impact without rebuilding lists for every campaign.<\/p>\n\n\n\n

                                4) What\u2019s the difference between a Contact Property and a tag?<\/h3>\n\n\n\n

                                A tag is often a flexible label that may lack strict definitions or formats. A Contact Property is typically more structured (type, allowed values, source), which makes it safer for automation and analytics.<\/p>\n\n\n\n

                                5) What are the most important Contact Property fields to start with?<\/h3>\n\n\n\n

                                Common starters include: email\/phone (identity), channel consent, country\/language, lifecycle stage, last activity date, last purchase date (or subscription status), and a small set of preferences relevant to your offers.<\/p>\n\n\n\n

                                6) How do you prevent broken automations when properties change?<\/h3>\n\n\n\n

                                Use documentation and change control: define owners, keep a property dictionary, test updates in a safe environment, and monitor key journeys after any field rename, repurpose, or sync-rule change\u2014especially in CRM Marketing<\/strong> environments.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                A **Contact Property** is a single piece of information stored about an individual contact in your customer database\u2014such as email address, lifecycle stage, last purchase date, consent status, or product interest. In **Direct & Retention Marketing**, these properties are the levers that turn generic outreach into timely, relevant messages across email, SMS, push, and other owned channels. In **CRM Marketing**, they act as the structured profile data that makes segmentation, automation, and measurement possible.<\/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-7695","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\/7695","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=7695"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7695\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7695"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7695"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7695"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}