{"id":8224,"date":"2026-03-25T19:24:36","date_gmt":"2026-03-25T19:24:36","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/badge-count\/"},"modified":"2026-03-25T19:24:36","modified_gmt":"2026-03-25T19:24:36","slug":"badge-count","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/badge-count\/","title":{"rendered":"Badge Count: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Push Notification Marketing"},"content":{"rendered":"\n

Badge Count is one of the most overlooked levers in Direct & Retention Marketing<\/strong>\u2014not because it\u2019s unimportant, but because it feels \u201csmall.\u201d In reality, the number (or indicator) displayed on an app icon can strongly influence whether users return, what they do next, and how they feel about your brand\u2019s relevance.<\/p>\n\n\n\n

In Push Notification Marketing<\/strong>, Badge Count often becomes the persistent, always-visible reminder that something is waiting inside the app\u2014an unread message, a pending task, a delivery update, or an offer that expires soon. When it\u2019s accurate and intentional, it supports retention and repeat engagement. When it\u2019s wrong or excessive, it creates irritation, distrust, and even uninstall risk.<\/p>\n\n\n\n

This article explains Badge Count from both a marketing and implementation perspective so teams can use it responsibly and effectively in modern Direct & Retention Marketing<\/strong>.<\/p>\n\n\n\n

What Is Badge Count?<\/h2>\n\n\n\n

Badge Count<\/strong> is the numeric value (or badge indicator) shown on an app\u2019s icon that represents how many items require attention\u2014commonly unread notifications, unread messages, pending actions, or new content. In most implementations, it\u2019s a per-user state that should reflect the user\u2019s actual \u201cto-do\u201d or \u201cunseen\u201d items inside the app.<\/p>\n\n\n\n

At its core, Badge Count is a behavioral prompt<\/strong>. It sits outside the app experience and nudges a user to re-open the app. That makes it a natural fit for Direct & Retention Marketing<\/strong>, where the goal is to increase repeat sessions, reduce churn, and drive lifecycle actions.<\/p>\n\n\n\n

Within Push Notification Marketing<\/strong>, Badge Count is often set or updated when a push notification is delivered (or when the app syncs). It can reinforce urgency and relevance\u2014especially when the badge number matches what the user finds after tapping through.<\/p>\n\n\n\n

Business-wise, Badge Count is not just decoration. It\u2019s a retention signal that shapes user expectations. If your app icon says \u201c7,\u201d the user assumes there are seven meaningful things worth checking. Meeting that expectation is critical to trust and long-term engagement.<\/p>\n\n\n\n

Why Badge Count Matters in Direct & Retention Marketing<\/h2>\n\n\n\n

Badge Count matters because it turns a one-time touchpoint into a persistent reminder. A push notification can disappear from the lock screen, but the badge can remain until the user takes action. That persistence can improve outcomes that Direct & Retention Marketing<\/strong> teams care about, including:<\/p>\n\n\n\n

    \n
  • More return sessions<\/strong>: A visible badge creates a low-effort prompt to open the app.<\/li>\n
  • Higher completion of lifecycle actions<\/strong>: Users are more likely to complete tasks (verify email, review order, respond to a message) when they see an outstanding count.<\/li>\n
  • Stronger habit formation<\/strong>: Consistent, accurate Badge Count can encourage \u201cchecking behavior\u201d similar to inbox or messaging apps.<\/li>\n
  • Better competitive positioning<\/strong>: In crowded categories, subtle cues that create routine usage can compound over time.<\/li>\n<\/ul>\n\n\n\n

    In Push Notification Marketing<\/strong>, Badge Count also acts as a quality filter. If you send pushes but never update or clear the badge correctly, users learn that your notifications are noisy or misleading. Conversely, a well-managed Badge Count makes pushes feel coherent and purposeful.<\/p>\n\n\n\n

    How Badge Count Works<\/h2>\n\n\n\n

    Badge Count is partly technical state management and partly experience design. In practice, it works like a lifecycle loop:<\/p>\n\n\n\n

      \n
    1. \n

      Input or trigger<\/strong>\n – A new event occurs: message received, order status updated, comment reply, new content published, subscription renewal due, etc.\n – A Push Notification Marketing<\/strong> campaign may also intentionally generate the event (for example, \u201cYour weekly summary is ready\u201d).<\/p>\n<\/li>\n

    2. \n

      Processing and decisioning<\/strong>\n – Your backend or messaging service determines whether this event should increase or change the Badge Count.\n – Rules may include eligibility (opt-in status), frequency caps, relevance, and whether the event is already seen.<\/p>\n<\/li>\n

    3. \n

      Execution or application<\/strong>\n – The app badge is updated in one of two common ways:<\/p>\n

        \n
      • Server-to-device update<\/strong> (often via push payloads where supported).<\/li>\n
      • App-side sync<\/strong> when the app opens, resumes, or receives background updates.<\/li>\n
      • The Badge Count may be set to a specific number (recommended for accuracy) or incremented (riskier if events are missed).<\/li>\n<\/ul>\n<\/li>\n
      • \n

        Output or outcome<\/strong>\n – Users see the updated Badge Count on the home screen.\n – They may open the app, clear items, or ignore it.\n – Your system should then decrement or reset the Badge Count based on what the user actually viewed or completed.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        For Direct & Retention Marketing<\/strong>, the key is not just \u201cshow a number,\u201d but \u201cmaintain a truthful, user-aligned count that maps to real value.\u201d<\/p>\n\n\n\n

        Key Components of Badge Count<\/h2>\n\n\n\n

        A reliable Badge Count depends on multiple components working together:<\/p>\n\n\n\n

        Data inputs and event sources<\/h3>\n\n\n\n
          \n
        • Message events (chat, support replies, social interactions)<\/li>\n
        • Content drops (news, lessons, recommendations)<\/li>\n
        • Transactional events (shipping updates, payment status)<\/li>\n
        • Task systems (approvals, reminders, assignments)<\/li>\n<\/ul>\n\n\n\n

          State model (what does the number mean?)<\/h3>\n\n\n\n

          Teams must define what Badge Count represents:\n– Unread notifications?\n– Unread messages?\n– Unseen content?\n– Pending tasks?\n– A combined count across categories?<\/p>\n\n\n\n

          In Direct & Retention Marketing<\/strong>, a clear definition prevents inflated numbers and conflicting user experiences.<\/p>\n\n\n\n

          Delivery and synchronization<\/h3>\n\n\n\n
            \n
          • Push-triggered updates where applicable<\/li>\n
          • App-side reconciliation to correct drift (missed pushes, device restrictions, multi-device usage)<\/li>\n<\/ul>\n\n\n\n

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

            Badge Count works best when ownership is explicit:\n– Product defines what counts and when it clears.\n– Marketing defines the lifecycle moments and messaging strategy.\n– Engineering ensures accurate counting, syncing, and edge-case handling.\n– Analytics validates impact and monitors negative signals.<\/p>\n\n\n\n

            Types of Badge Count<\/h2>\n\n\n\n

            Badge Count doesn\u2019t have \u201cformal\u201d industry types, but there are practical distinctions that change how it behaves and how users perceive it:<\/p>\n\n\n\n

            Absolute vs. incremental counts<\/h3>\n\n\n\n
              \n
            • Absolute Badge Count<\/strong>: set the badge to the true total (for example, 3 unread items). This is typically more accurate across devices and missed events.<\/li>\n
            • Incremental Badge Count<\/strong>: add +1 per event. This is simpler but can drift if events are dropped, duplicated, or cleared elsewhere.<\/li>\n<\/ul>\n\n\n\n

              Single-purpose vs. aggregated counts<\/h3>\n\n\n\n
                \n
              • Single-purpose<\/strong>: only unread messages, only pending tasks, etc. Clearer and easier to trust.<\/li>\n
              • Aggregated<\/strong>: combines multiple sources into one number. Powerful but easier to confuse (users may not know what the \u201c9\u201d represents).<\/li>\n<\/ul>\n\n\n\n

                Persistent vs. time-bound counts<\/h3>\n\n\n\n
                  \n
                • Persistent<\/strong>: remains until cleared by the user.<\/li>\n
                • Time-bound<\/strong>: decays or resets (for example, daily). This can reduce anxiety but must be explained through UX to avoid confusion.<\/li>\n<\/ul>\n\n\n\n

                  Numeric badge vs. indicator badge<\/h3>\n\n\n\n

                  Some platforms show a numeric badge; others may show a dot\/indicator depending on device settings. In Push Notification Marketing<\/strong>, you should design expectations around \u201cattention needed,\u201d not only a precise number.<\/p>\n\n\n\n

                  Real-World Examples of Badge Count<\/h2>\n\n\n\n

                  1) E-commerce: cart and order updates<\/h3>\n\n\n\n

                  A retail app uses Badge Count to reflect actionable updates<\/strong>, not promotions:\n– Badge increases when an order status changes (shipped, delivered) or when a return requires action.\n– The badge clears when the user opens the order detail and the update is marked as seen.\nIn Direct & Retention Marketing<\/strong>, this supports repeat sessions and post-purchase engagement without overusing discount-driven pushes.<\/p>\n\n\n\n

                  2) B2B SaaS: tasks and approvals<\/h3>\n\n\n\n

                  A workflow app sets Badge Count to the number of pending approvals assigned to the user:\n– A Push Notification Marketing<\/strong> message announces, \u201c2 approvals need your review.\u201d\n– Badge Count is set to \u201c2\u201d (absolute), and decrements as each item is completed.\nThis aligns the badge with productivity value, improving retention and reducing time-to-action.<\/p>\n\n\n\n

                  3) Media app: personalized content queue<\/h3>\n\n\n\n

                  A news or learning app uses Badge Count for \u201cnew items since last visit,\u201d but caps it:\n– Badge Count increases up to a maximum threshold to avoid overwhelming users.\n– When the user opens the app, the feed highlights what\u2019s new and then resets.\nIn Direct & Retention Marketing<\/strong>, this creates a routine without turning the badge into an anxiety generator.<\/p>\n\n\n\n

                  Benefits of Using Badge Count<\/h2>\n\n\n\n

                  When implemented thoughtfully, Badge Count can deliver measurable benefits:<\/p>\n\n\n\n

                    \n
                  • Improved engagement efficiency<\/strong>: It can lift return visits without sending more messages, which matters when notification fatigue is high.<\/li>\n
                  • Higher perceived relevance<\/strong>: A truthful badge is a promise that the app contains something worth opening.<\/li>\n
                  • Cost savings and deliverability resilience<\/strong>: If users re-engage from the badge, you may rely less on repeated sends and reduce opt-outs.<\/li>\n
                  • Better user experience<\/strong>: Badge Count can reduce \u201chunt time\u201d by signaling that there\u2019s something new and guiding users to the right screen.<\/li>\n
                  • Stronger lifecycle performance<\/strong>: In Push Notification Marketing<\/strong>, the badge can reinforce the message and extend the window of influence beyond the moment of delivery.<\/li>\n<\/ul>\n\n\n\n

                    Challenges of Badge Count<\/h2>\n\n\n\n

                    Badge Count is deceptively easy to get wrong. Common pitfalls include:<\/p>\n\n\n\n

                      \n
                    • Count drift and inaccuracies<\/strong>: Missed pushes, delayed sync, multi-device usage, and offline states can cause mismatches between the icon and in-app reality.<\/li>\n
                    • Overcounting low-value items<\/strong>: If marketing counts every promo or minor update, users stop trusting the badge.<\/li>\n
                    • Platform variability<\/strong>: Badge behavior differs across operating systems, device manufacturers, and user settings. Some users disable badges entirely.<\/li>\n
                    • Clearing logic complexity<\/strong>: \u201cRead,\u201d \u201cseen,\u201d and \u201ccompleted\u201d are different states. Poor definitions lead to badges that never clear.<\/li>\n
                    • Negative brand impact<\/strong>: An always-high Badge Count can feel like pressure, creating stress rather than motivation\u2014hurting Direct & Retention Marketing<\/strong> goals.<\/li>\n<\/ul>\n\n\n\n

                      Best Practices for Badge Count<\/h2>\n\n\n\n

                      Make the badge truthful and user-centered<\/h3>\n\n\n\n

                      Treat Badge Count as a contract: the number should correspond to real, valuable items. If users tap in and don\u2019t see what the badge promised, you lose trust fast.<\/p>\n\n\n\n

                      Prefer absolute counts over increments<\/h3>\n\n\n\n

                      If possible, set Badge Count to the current total from a source of truth. This reduces drift and makes cross-device behavior more consistent.<\/p>\n\n\n\n

                      Define \u201cwhat counts\u201d and \u201cwhat clears\u201d<\/h3>\n\n\n\n

                      Document rules such as:\n– Which event types increment the count\n– When items are considered \u201cseen\u201d vs. \u201ccompleted\u201d\n– Whether the badge clears on app open or only after viewing specific screens<\/p>\n\n\n\n

                      Cap or bucket when appropriate<\/h3>\n\n\n\n

                      For high-volume apps, consider caps (for example, \u201c9+\u201d) or design strategies that prevent giant numbers from becoming discouraging.<\/p>\n\n\n\n

                      Coordinate Push Notification Marketing with badge logic<\/h3>\n\n\n\n

                      If the push says \u201c3 new messages,\u201d the Badge Count should be 3 (not 17). Align copy, deep links, and badge updates so the experience is coherent.<\/p>\n\n\n\n

                      Monitor and iterate<\/h3>\n\n\n\n

                      In Direct & Retention Marketing<\/strong>, treat Badge Count as an optimization surface:\n– Test which event categories should contribute\n– Evaluate whether badge persistence helps or harms different segments\n– Watch for rising opt-outs or uninstalls after badge strategy changes<\/p>\n\n\n\n

                      Tools Used for Badge Count<\/h2>\n\n\n\n

                      Badge Count is implemented and managed through a stack rather than a single tool. Common tool groups include:<\/p>\n\n\n\n

                        \n
                      • Push notification platforms and messaging services<\/strong>: to send notifications and (where supported) update badge values as part of message payloads.<\/li>\n
                      • Mobile app analytics<\/strong>: to measure how badge exposure correlates with opens, sessions, and conversions.<\/li>\n
                      • Customer data platforms (CDPs) and CRM systems<\/strong>: to segment users (for example, \u201chigh intent,\u201d \u201cat-risk\u201d) and coordinate Direct & Retention Marketing<\/strong> triggers.<\/li>\n
                      • Event pipelines and data warehouses<\/strong>: to maintain a reliable source of truth for unread\/pending items and to audit badge accuracy.<\/li>\n
                      • Experimentation and feature flag systems<\/strong>: to test badge rules (what counts, caps, clearing behavior) safely.<\/li>\n
                      • QA and device testing workflows<\/strong>: to validate badge behavior across OS versions, settings, and edge cases.<\/li>\n<\/ul>\n\n\n\n

                        If your Push Notification Marketing<\/strong> program is mature, Badge Count should be part of the same orchestration and measurement discipline as frequency capping and personalization.<\/p>\n\n\n\n

                        Metrics Related to Badge Count<\/h2>\n\n\n\n

                        Badge Count itself is an on-device indicator, so you typically measure its impact indirectly through behavior and quality signals. Useful metrics include:<\/p>\n\n\n\n

                          \n
                        • App open rate after notification delivery<\/strong>: whether pushes that update Badge Count lead to more sessions.<\/li>\n
                        • Time-to-open<\/strong>: how quickly users open the app after the badge appears (especially for urgent events).<\/li>\n
                        • Session frequency and retention<\/strong>: day 1\/day 7\/day 30 retention trends after introducing or changing Badge Count logic.<\/li>\n
                        • Conversion rate on targeted actions<\/strong>: approvals completed, carts recovered, messages replied to, renewals paid.<\/li>\n
                        • Opt-out and uninstall indicators<\/strong>: notification opt-out rate, churn, and app uninstalls after badge-heavy strategies.<\/li>\n
                        • Badge accuracy audits<\/strong> (operational metric): sampled comparisons of Badge Count vs. server-side unread totals.<\/li>\n
                        • User support\/contact rate<\/strong>: complaints like \u201cbadge won\u2019t clear\u201d are a leading indicator of broken logic.<\/li>\n<\/ul>\n\n\n\n

                          In Direct & Retention Marketing<\/strong>, pair outcome metrics (retention, revenue) with guardrail metrics (opt-outs, complaints) to avoid short-term gains that damage trust.<\/p>\n\n\n\n

                          Future Trends of Badge Count<\/h2>\n\n\n\n

                          Badge Count is evolving as operating systems and user expectations shift:<\/p>\n\n\n\n

                            \n
                          • AI-driven personalization<\/strong>: More teams will personalize which items count toward the badge based on predicted value (for example, only \u201chigh priority\u201d events contribute).<\/li>\n
                          • Automation with stricter relevance standards<\/strong>: As users become more selective with notifications, Badge Count will be used more carefully\u2014favoring fewer, more meaningful counts.<\/li>\n
                          • Privacy and measurement constraints<\/strong>: With tighter platform rules and reduced tracking signals, teams will lean more on first-party event quality to maintain accurate badge state.<\/li>\n
                          • Unified lifecycle orchestration<\/strong>: Badge Count will increasingly be coordinated with in-app inboxes, email, and SMS so Direct & Retention Marketing<\/strong> stays consistent across channels.<\/li>\n
                          • User-control experiences<\/strong>: Expect more emphasis on preference centers that let users decide what contributes to Badge Count (messages only, orders only, etc.).<\/li>\n<\/ul>\n\n\n\n

                            In Push Notification Marketing<\/strong>, the winners will be teams that treat Badge Count as part of respectful attention management, not merely a growth hack.<\/p>\n\n\n\n

                            Badge Count vs Related Terms<\/h2>\n\n\n\n

                            Badge Count vs notification badge<\/h3>\n\n\n\n

                            A notification badge<\/strong> is the visual element (dot or number) shown on the app icon. Badge Count<\/strong> is the specific numeric value that badge may display. In practice people use these interchangeably, but separating \u201cvisual badge\u201d from \u201ccount value\u201d helps clarify requirements.<\/p>\n\n\n\n

                            Badge Count vs unread count<\/h3>\n\n\n\n

                            An unread count<\/strong> is a backend or in-app metric representing unread items in a specific feed (messages, notifications, etc.). Badge Count may mirror an unread count, but it can also represent pending tasks or aggregated categories. The key difference is where it appears (icon vs. in-app) and how carefully it must be synchronized.<\/p>\n\n\n\n

                            Badge Count vs in-app notification center\/inbox<\/h3>\n\n\n\n

                            An in-app inbox stores messages and can provide history. Badge Count is only the attention signal on the home screen. In Direct & Retention Marketing<\/strong>, the best experience often pairs both: the badge prompts the open; the inbox provides continuity and reduces reliance on ephemeral push delivery.<\/p>\n\n\n\n

                            Who Should Learn Badge Count<\/h2>\n\n\n\n
                              \n
                            • Marketers and lifecycle managers<\/strong>: to align Badge Count with Push Notification Marketing<\/strong> strategy, segmentation, and user experience outcomes.<\/li>\n
                            • Analysts<\/strong>: to measure incremental impact, identify negative signals, and validate badge accuracy vs. engagement.<\/li>\n
                            • Agencies and consultants<\/strong>: to audit retention programs and recommend governance around notification and badge logic.<\/li>\n
                            • Business owners and founders<\/strong>: to understand why \u201csmall UX signals\u201d can materially affect retention and brand trust.<\/li>\n
                            • Developers and product teams<\/strong>: to implement correct syncing, clearing rules, and cross-device consistency that make Direct & Retention Marketing<\/strong> efforts reliable.<\/li>\n<\/ul>\n\n\n\n

                              Summary of Badge Count<\/h2>\n\n\n\n

                              Badge Count<\/strong> is the number (or indicator) displayed on an app icon to represent pending, unread, or unseen items that need attention. In Direct & Retention Marketing<\/strong>, it\u2019s a persistent nudge that can increase return sessions, improve lifecycle completion, and strengthen habits\u2014when it remains accurate and meaningful. In Push Notification Marketing<\/strong>, Badge Count should reinforce the message and match what users find in-app, creating a coherent and trustworthy experience.<\/p>\n\n\n\n

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

                              1) What is Badge Count used for in marketing?<\/h3>\n\n\n\n

                              Badge Count is used to prompt re-engagement by showing users they have something pending in the app (messages, tasks, updates). In Direct & Retention Marketing<\/strong>, it supports repeat sessions without requiring constant message sends.<\/p>\n\n\n\n

                              2) How does Badge Count affect Push Notification Marketing performance?<\/h3>\n\n\n\n

                              In Push Notification Marketing<\/strong>, an updated Badge Count can extend the impact of a push beyond the moment it appears. If the badge aligns with real in-app value, it can lift opens and conversions; if it\u2019s inaccurate, it can increase opt-outs.<\/p>\n\n\n\n

                              3) Should Badge Count be cleared when the app opens?<\/h3>\n\n\n\n

                              Not always. Clearing on open is simple but can be misleading if the user didn\u2019t actually view or resolve the items. Many teams clear Badge Count only after the user visits the relevant screen or marks items as read\/completed.<\/p>\n\n\n\n

                              4) What\u2019s better: incrementing the badge or setting an exact number?<\/h3>\n\n\n\n

                              Setting an exact Badge Count (absolute value) is usually more reliable because it reduces drift caused by missed messages, multiple devices, or background restrictions.<\/p>\n\n\n\n

                              5) Can Badge Count hurt retention?<\/h3>\n\n\n\n

                              Yes. If Badge Count is constantly high, counts low-value items, or won\u2019t clear, users can feel nagged or mistrustful. That can undermine Direct & Retention Marketing<\/strong> goals and lead to notification disabling or uninstalling.<\/p>\n\n\n\n

                              6) How do you measure whether Badge Count is working?<\/h3>\n\n\n\n

                              Track changes in return sessions, time-to-open, action completion rates, and retention cohorts after badge logic changes. Also watch guardrails like opt-out rates, uninstalls, and \u201cbadge won\u2019t clear\u201d support complaints.<\/p>\n\n\n\n

                              7) Do all users see Badge Count the same way?<\/h3>\n\n\n\n

                              No. Visibility depends on device type, OS behavior, launcher variations, and user settings (some disable badges). For Push Notification Marketing<\/strong>, plan for variability and ensure the in-app experience still works even when Badge Count isn\u2019t shown.<\/p>\n","protected":false},"excerpt":{"rendered":"

                              Badge Count is one of the most overlooked levers in **Direct & Retention Marketing**\u2014not because it\u2019s unimportant, but because it feels \u201csmall.\u201d In reality, the number (or indicator) displayed on an app icon can strongly influence whether users return, what they do next, and how they feel about your brand\u2019s relevance.<\/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":[1895],"tags":[],"class_list":["post-8224","post","type-post","status-publish","format-standard","hentry","category-push-notification-marketing"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8224","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=8224"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8224\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=8224"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=8224"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=8224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}