{"id":8113,"date":"2026-03-25T15:08:51","date_gmt":"2026-03-25T15:08:51","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/dedupe-key\/"},"modified":"2026-03-25T15:08:51","modified_gmt":"2026-03-25T15:08:51","slug":"dedupe-key","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/dedupe-key\/","title":{"rendered":"Dedupe Key: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Marketing Automation"},"content":{"rendered":"\n

A Dedupe Key<\/strong> is a deliberate identifier used to detect and prevent duplicates across customer records, events, and campaign actions. In Direct & Retention Marketing<\/strong>, where the goal is to build durable customer relationships through email, SMS, push, and lifecycle messaging, duplicates are more than a data nuisance\u2014they create wasted spend, inflated metrics, and poor customer experiences.<\/p>\n\n\n\n

In Marketing Automation<\/strong>, a Dedupe Key becomes the \u201crule of identity\u201d that decides whether two things should be treated as the same: two profiles, two sign-ups, two purchases, or two triggered messages. When you implement a strong Dedupe Key strategy, you reduce double-sends, improve segmentation accuracy, and make attribution and reporting more trustworthy\u2014without relying on guesswork.<\/p>\n\n\n\n

What Is Dedupe Key?<\/h2>\n\n\n\n

A Dedupe Key<\/strong> is a field (or combination of fields) used to determine uniqueness so you can merge, suppress, or ignore duplicates. Think of it as the consistent \u201cfingerprint\u201d your systems use to answer: Is this the same person or the same event we already have?<\/em><\/p>\n\n\n\n

At its core, a Dedupe Key is:<\/p>\n\n\n\n

    \n
  • A decision rule<\/strong>: what counts as the \u201csame\u201d record or action?<\/li>\n
  • A technical mechanism<\/strong>: a column, ID, or computed value used for matching.<\/li>\n
  • A business safeguard<\/strong>: it protects budget, customer trust, and measurement integrity.<\/li>\n<\/ul>\n\n\n\n

    In Direct & Retention Marketing<\/strong>, a Dedupe Key typically supports identity and frequency control\u2014ensuring each customer receives the right message, once, through the right channel. Inside Marketing Automation<\/strong>, it\u2019s commonly used in three places:<\/p>\n\n\n\n

      \n
    1. Profile deduplication<\/strong> (one customer, one profile)<\/li>\n
    2. Event deduplication<\/strong> (one purchase, one event)<\/li>\n
    3. Send\/action deduplication<\/strong> (one intended message, one delivery attempt)<\/li>\n<\/ol>\n\n\n\n

      Why Dedupe Key Matters in Direct & Retention Marketing<\/h2>\n\n\n\n

      Duplicates quietly degrade performance. Two records for the same person can split engagement history, causing personalization to fail and segments to misfire. In Direct & Retention Marketing<\/strong>, that shows up as customers receiving redundant onboarding emails, conflicting offers, or an \u201cexisting customer\u201d being treated like a prospect.<\/p>\n\n\n\n

      A well-designed Dedupe Key<\/strong> creates business value by:<\/p>\n\n\n\n

        \n
      • Protecting deliverability and reputation<\/strong>: repeated messages can increase complaints, unsubscribes, and spam signals.<\/li>\n
      • Reducing operational waste<\/strong>: fewer duplicate sends means lower messaging costs and less support overhead.<\/li>\n
      • Improving measurement<\/strong>: cleaner data makes attribution, incrementality testing, and cohort analysis more credible.<\/li>\n
      • Enabling better lifecycle decisions<\/strong>: if purchase events are duplicated, your automation might trigger cross-sell too early\u2014or suppress win-back incorrectly.<\/li>\n<\/ul>\n\n\n\n

        Organizations that treat deduplication as part of their competitive advantage generally run more precise Marketing Automation<\/strong>, with fewer \u201cmystery spikes\u201d and more reliable personalization at scale.<\/p>\n\n\n\n

        How Dedupe Key Works<\/h2>\n\n\n\n

        A Dedupe Key<\/strong> is both a concept and an operational pattern. In practice, it works as a repeatable workflow:<\/p>\n\n\n\n

          \n
        1. \n

          Input or trigger<\/strong>\n Data arrives from forms, ecommerce platforms, POS systems, apps, call centers, ad leads, or partner uploads\u2014often with inconsistencies (different emails, missing IDs, formatting differences).<\/p>\n<\/li>\n

        2. \n

          Analysis or processing<\/strong>\n Your data pipeline or Marketing Automation<\/strong> platform evaluates a Dedupe Key to decide whether the incoming item is new or already known. This may involve:\n – Normalization (lowercasing emails, stripping spaces, standardizing phone formats)\n – Exact matching (same customer_id)\n – Composite matching (email + country, phone + last name, etc.)\n – Event uniqueness logic (order_id + event_name + timestamp window)<\/p>\n<\/li>\n

        3. \n

          Execution or application<\/strong>\n Depending on the result, the system will:\n – Merge<\/strong> records (combine attributes and history)\n – Suppress<\/strong> duplicates (ignore the new item)\n – Update<\/strong> existing records (keep one \u201cgolden\u201d profile)\n – Prevent duplicate actions<\/strong> (don\u2019t send the same message twice)<\/p>\n<\/li>\n

        4. \n

          Output or outcome<\/strong>\n The customer gets a consistent experience, segments become more accurate, and reports reflect reality\u2014key requirements for high-performing Direct & Retention Marketing<\/strong>.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

          Key Components of Dedupe Key<\/h2>\n\n\n\n

          A strong Dedupe Key<\/strong> implementation is rarely \u201cjust one field.\u201d It\u2019s a set of components spanning systems, process, and governance:<\/p>\n\n\n\n

          Data inputs and identifiers<\/h3>\n\n\n\n

          Common inputs used to build a Dedupe Key include:\n– Customer ID from a transactional system\n– Email address (normalized)\n– Phone number (normalized to a standard format)\n– Loyalty ID or membership number\n– Order ID \/ invoice ID (for event dedupe)\n– Device or app instance identifiers (use cautiously; they can change)<\/p>\n\n\n\n

          Systems involved<\/h3>\n\n\n\n

          In Direct & Retention Marketing<\/strong>, dedupe decisions often happen across:\n– CRM or customer database\n– ESP\/SMS\/push platforms\n– CDP or customer data layer\n– Data warehouse and ETL\/ELT pipelines\n– Web\/app analytics and event collectors<\/p>\n\n\n\n

          Business rules and governance<\/h3>\n\n\n\n

          A Dedupe Key is only as good as its rules. You need clear ownership for:\n– Which identifiers are \u201cauthoritative\u201d\n– When to merge vs. when to keep separate (e.g., shared family email)\n– Conflict resolution (which value wins when fields disagree)\n– Audit trails (what changed and why)<\/p>\n\n\n\n

          Monitoring and quality checks<\/h3>\n\n\n\n

          You also need ongoing validation: match rates, duplicate rates, and anomaly detection to ensure Marketing Automation<\/strong> continues to behave correctly as sources change.<\/p>\n\n\n\n

          Types of Dedupe Key (Practical Distinctions)<\/h2>\n\n\n\n

          \u201cTypes\u201d of Dedupe Key<\/strong> are less about formal categories and more about matching approaches and contexts:<\/p>\n\n\n\n

          1) Deterministic Dedupe Key<\/h3>\n\n\n\n

          Uses an exact, stable identifier (e.g., customer_id, loyalty_id). This is the gold standard for Direct & Retention Marketing<\/strong> because it\u2019s predictable and auditable.<\/p>\n\n\n\n

          2) Composite Dedupe Key<\/h3>\n\n\n\n

          Combines multiple fields to approximate uniqueness (e.g., normalized_email + brand, phone + country_code). Composite keys are common when a single universal ID doesn\u2019t exist.<\/p>\n\n\n\n

          3) Hashed or tokenized Dedupe Key<\/h3>\n\n\n\n

          Transforms identifiers (like email) into a hashed value for safer handling across systems. This can help with privacy and data sharing, but it requires consistent hashing rules and careful governance.<\/p>\n\n\n\n

          4) Event-level Dedupe Key<\/h3>\n\n\n\n

          Designed for actions (purchase, signup, subscription change) rather than people. A typical pattern is order_id + event_type, sometimes with a time-based guardrail.<\/p>\n\n\n\n

          5) Channel-specific Dedupe Key<\/h3>\n\n\n\n

          Used to prevent duplicate sends across channels or within a channel (e.g., suppress duplicate SMS sends when an email and SMS are triggered by the same event).<\/p>\n\n\n\n

          Real-World Examples of Dedupe Key<\/h2>\n\n\n\n

          Example 1: Preventing duplicate welcome emails<\/h3>\n\n\n\n

          A customer signs up via a website form and then again via a checkout opt-in. Without a Dedupe Key<\/strong>, Marketing Automation<\/strong> may create two profiles and trigger two welcome journeys.<\/p>\n\n\n\n

            \n
          • Dedupe Key approach<\/strong>: normalized email (and optionally email + brand\/region)<\/li>\n
          • Outcome in Direct & Retention Marketing<\/strong>: one customer, one welcome series, cleaner engagement history.<\/li>\n<\/ul>\n\n\n\n

            Example 2: Deduplicating purchase events to stop repeated post-purchase flows<\/h3>\n\n\n\n

            Some ecommerce systems resend order events during retries or partial failures. If each event triggers a post-purchase cross-sell, customers may receive repeated messages.<\/p>\n\n\n\n

              \n
            • Dedupe Key approach<\/strong>: order_id + event_name (plus a reasonable timestamp window)<\/li>\n
            • Outcome<\/strong>: accurate revenue attribution, fewer complaints, more reliable lifecycle timing.<\/li>\n<\/ul>\n\n\n\n

              Example 3: Merging offline and online customers for unified retention targeting<\/h3>\n\n\n\n

              A retailer collects phone numbers in-store and emails online. Over time, the same person appears twice.<\/p>\n\n\n\n

                \n
              • Dedupe Key approach<\/strong>: loyalty_id when available; otherwise a composite rule (phone + last name) with cautious merge thresholds<\/li>\n
              • Outcome in Direct & Retention Marketing<\/strong>: unified frequency capping and better personalization across channels.<\/li>\n<\/ul>\n\n\n\n

                Benefits of Using Dedupe Key<\/h2>\n\n\n\n

                Implementing a thoughtful Dedupe Key<\/strong> delivers benefits that compound over time:<\/p>\n\n\n\n

                  \n
                • Higher campaign efficiency<\/strong>: fewer redundant sends and less spend on messaging volume.<\/li>\n
                • Better personalization<\/strong>: one profile holds the full preference and engagement history.<\/li>\n
                • Improved deliverability signals<\/strong>: reduced spam complaints and fewer \u201cwhy did I get this twice?\u201d moments.<\/li>\n
                • More trustworthy analytics<\/strong>: cleaner cohorts, more accurate conversion rates, and fewer inflated counts.<\/li>\n
                • Stronger customer experience<\/strong>: consistent journeys and reduced friction, a core goal of Direct & Retention Marketing<\/strong>.<\/li>\n
                • More reliable automation<\/strong>: triggers behave predictably, reducing firefighting in Marketing Automation<\/strong> operations.<\/li>\n<\/ul>\n\n\n\n

                  Challenges of Dedupe Key<\/h2>\n\n\n\n

                  A Dedupe Key<\/strong> strategy also comes with real constraints:<\/p>\n\n\n\n

                    \n
                  • Identifier instability<\/strong>: emails change, phone numbers get recycled, devices reset, and cookies expire.<\/li>\n
                  • Shared identifiers<\/strong>: family emails or shared phones can cause incorrect merges if rules are too aggressive.<\/li>\n
                  • Cross-system inconsistency<\/strong>: different platforms may normalize data differently (spacing, casing, country codes).<\/li>\n
                  • Latency and ordering<\/strong>: events can arrive out of order; retries can create duplicates without careful event-level keys.<\/li>\n
                  • Merge conflicts<\/strong>: which consent status wins, which address is current, which name is correct?<\/li>\n
                  • Measurement side effects<\/strong>: changing dedupe logic can shift reported totals, so you need change management.<\/li>\n<\/ul>\n\n\n\n

                    In Direct & Retention Marketing<\/strong>, the biggest risk is usually not \u201chaving duplicates,\u201d but merging incorrectly\u2014because the wrong merge can violate consent choices and damage trust.<\/p>\n\n\n\n

                    Best Practices for Dedupe Key<\/h2>\n\n\n\n

                    These practices help teams implement a Dedupe Key<\/strong> that scales:<\/p>\n\n\n\n

                      \n
                    1. \n

                      Start with authoritative IDs where possible<\/strong>\n Prefer transactional customer IDs or loyalty IDs over softer identifiers like device IDs.<\/p>\n<\/li>\n

                    2. \n

                      Normalize before you match<\/strong>\n Apply consistent rules (lowercase emails, standard phone formatting, trim whitespace) upstream so every system interprets the Dedupe Key the same way.<\/p>\n<\/li>\n

                    3. \n

                      Separate person dedupe from event dedupe<\/strong>\n Use a profile-level Dedupe Key<\/strong> for identity and an event-level key for transactions and behavioral events.<\/p>\n<\/li>\n

                    4. \n

                      Define merge policies explicitly<\/strong>\n Document:\n – Which source wins for each field (CRM vs. ecommerce vs. support)\n – How consent is handled (opt-in should be treated carefully and audited)\n – When to block merges (e.g., same email but different countries may need review)<\/p>\n<\/li>\n

                    5. \n

                      Use \u201csoft merges\u201d when uncertain<\/strong>\n Instead of merging everything, link identities with confidence levels. This reduces risky merges while still improving targeting in Marketing Automation<\/strong>.<\/p>\n<\/li>\n

                    6. \n

                      Monitor for drift<\/strong>\n Track duplicate rate over time and investigate spikes after form changes, app releases, or new integrations.<\/p>\n<\/li>\n

                    7. \n

                      Test automation edge cases<\/strong>\n In Direct & Retention Marketing<\/strong>, run QA scenarios like: re-subscribes, checkout retries, returns, cancellations, and multi-device sign-ins.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                      Tools Used for Dedupe Key<\/h2>\n\n\n\n

                      A Dedupe Key<\/strong> is implemented through workflows across several tool categories:<\/p>\n\n\n\n

                        \n
                      • CRM systems<\/strong>: often store the \u201csystem of record\u201d ID and support merge rules, field-level priorities, and audit logs.<\/li>\n
                      • Customer data platforms (CDPs) \/ identity resolution layers<\/strong>: unify profiles from multiple sources and apply matching logic; often central to Direct & Retention Marketing<\/strong> identity.<\/li>\n
                      • Marketing Automation platforms<\/strong>: execute journey logic, suppression rules, frequency caps, and trigger dedupe for sends.<\/li>\n
                      • Data warehouses + ETL\/ELT<\/strong>: enforce dedupe in pipelines, build event-level keys, and create curated \u201cgolden\u201d tables for analytics and activation.<\/li>\n
                      • Analytics and event collection tools<\/strong>: help validate whether event dedupe is working by exposing duplicates and retry patterns.<\/li>\n
                      • Reporting dashboards \/ BI<\/strong>: monitor duplicate rates, merge volume, and downstream campaign impact.<\/li>\n<\/ul>\n\n\n\n

                        The key is consistency: whichever layer computes the Dedupe Key must align with how your activation tools interpret identity and events.<\/p>\n\n\n\n

                        Metrics Related to Dedupe Key<\/h2>\n\n\n\n

                        You can\u2019t manage what you don\u2019t measure. Useful metrics include:<\/p>\n\n\n\n

                          \n
                        • Duplicate profile rate<\/strong>: percentage of profiles that share the same identifier (e.g., email) beyond expected thresholds.<\/li>\n
                        • Match\/merge rate<\/strong>: how often new records are matched to an existing profile vs. created as new.<\/li>\n
                        • Event duplicate rate<\/strong>: ratio of raw incoming events to deduplicated events (by event type).<\/li>\n
                        • Send suppression count<\/strong>: number of messages prevented due to dedupe rules.<\/li>\n
                        • Deliverability and list health indicators<\/strong>: complaint rate, unsubscribe rate, bounce rate\u2014often improve when Dedupe Key logic reduces repeated sends.<\/li>\n
                        • Frequency distribution<\/strong>: how many users receive X messages per week; dedupe often reduces extreme tails.<\/li>\n
                        • Revenue and attribution stability<\/strong>: fewer unexplained swings after pipeline retries or integration changes.<\/li>\n<\/ul>\n\n\n\n

                          In Marketing Automation<\/strong>, pair dedupe metrics with journey-level KPIs to see whether changes improve real outcomes, not just data cleanliness.<\/p>\n\n\n\n

                          Future Trends of Dedupe Key<\/h2>\n\n\n\n

                          Several shifts are shaping how Dedupe Key<\/strong> evolves in Direct & Retention Marketing<\/strong>:<\/p>\n\n\n\n

                            \n
                          • AI-assisted identity resolution<\/strong>: machine learning can propose matches based on patterns, but deterministic rules and audits remain important for consent-sensitive use cases.<\/li>\n
                          • Privacy-driven identifier changes<\/strong>: fewer persistent identifiers and more user-controlled consent push teams toward first-party IDs and transparent governance.<\/li>\n
                          • Real-time dedupe requirements<\/strong>: streaming data and instant triggers increase the need for low-latency event-level Dedupe Key logic.<\/li>\n
                          • Composable stacks<\/strong>: as teams mix best-of-breed tools, the Dedupe Key increasingly lives in shared data layers (warehouse\/CDP) to keep Marketing Automation<\/strong> consistent.<\/li>\n
                          • Preference and consent complexity<\/strong>: identity isn\u2019t just \u201cwho is this,\u201d but \u201cwhat are we allowed to do,\u201d making safe merge policies a strategic priority.<\/li>\n<\/ul>\n\n\n\n

                            Dedupe Key vs Related Terms<\/h2>\n\n\n\n

                            Dedupe Key vs Unique ID<\/h3>\n\n\n\n

                            A Unique ID<\/strong> is a single identifier meant to be unique (like a customer_id). A Dedupe Key<\/strong> is the rule you use for uniqueness\u2014sometimes it is a unique ID, but often it\u2019s composite or contextual.<\/p>\n\n\n\n

                            Dedupe Key vs Identity Resolution<\/h3>\n\n\n\n

                            Identity resolution<\/strong> is the broader practice of recognizing and connecting customer identifiers across systems and devices. The Dedupe Key<\/strong> is one of the mechanisms identity resolution uses to decide matches and merges.<\/p>\n\n\n\n

                            Dedupe Key vs Frequency Capping<\/h3>\n\n\n\n

                            Frequency capping<\/strong> limits how often someone can receive messages. A Dedupe Key<\/strong> ensures you know who \u201csomeone\u201d is and prevents duplicate actions. In Direct & Retention Marketing<\/strong>, you often need both: dedupe to prevent accidental duplicates and caps to manage intentional volume.<\/p>\n\n\n\n

                            Who Should Learn Dedupe Key<\/h2>\n\n\n\n

                            Understanding Dedupe Key<\/strong> pays off across roles:<\/p>\n\n\n\n

                              \n
                            • Marketers<\/strong>: to prevent double-sends, improve segmentation, and protect brand trust in Direct & Retention Marketing<\/strong>.<\/li>\n
                            • Analysts<\/strong>: to improve data quality, attribution reliability, and experimental integrity.<\/li>\n
                            • Agencies<\/strong>: to onboard clients faster, diagnose performance issues, and standardize Marketing Automation<\/strong> implementations.<\/li>\n
                            • Business owners and founders<\/strong>: to reduce wasted spend and ensure customer communications feel coordinated.<\/li>\n
                            • Developers and data engineers<\/strong>: to design robust pipelines, event schemas, and merge logic that won\u2019t break when systems change.<\/li>\n<\/ul>\n\n\n\n

                              Summary of Dedupe Key<\/h2>\n\n\n\n

                              A Dedupe Key<\/strong> is the practical rule that determines uniqueness across customer profiles, events, and campaign actions. It matters because duplicates undermine personalization, inflate metrics, and harm customer experience\u2014especially in Direct & Retention Marketing<\/strong>, where consistent lifecycle messaging is essential. Implemented thoughtfully, a Dedupe Key strengthens Marketing Automation<\/strong> by making triggers more reliable, segmentation more accurate, and reporting more trustworthy.<\/p>\n\n\n\n

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

                              1) What is a Dedupe Key in plain language?<\/h3>\n\n\n\n

                              A Dedupe Key<\/strong> is the identifier (or combination of identifiers) your system uses to decide whether something is new or a duplicate, so you can merge, suppress, or update instead of creating repeats.<\/p>\n\n\n\n

                              2) Where should deduplication happen: CRM, warehouse, or Marketing Automation?<\/h3>\n\n\n\n

                              Ideally in multiple layers with clear ownership: the warehouse\/CDP can standardize identity and events, while Marketing Automation<\/strong> enforces send-level dedupe and suppression for real-time journeys.<\/p>\n\n\n\n

                              3) Is email address a good Dedupe Key?<\/h3>\n\n\n\n

                              Often yes for many Direct & Retention Marketing<\/strong> programs, but it\u2019s not perfect. People change emails, share addresses, or mistype them. When possible, prefer a stable customer ID and use email as a secondary key.<\/p>\n\n\n\n

                              4) How do I dedupe events like purchases or signups?<\/h3>\n\n\n\n

                              Use an event-level Dedupe Key<\/strong> such as order_id + event_type. Add a timestamp-based safeguard for systems that retry events or send partial updates.<\/p>\n\n\n\n

                              5) Can a Dedupe Key hurt performance if implemented incorrectly?<\/h3>\n\n\n\n

                              Yes. Over-aggressive matching can merge different people into one profile, causing wrong personalization and consent mistakes. Under-aggressive matching leaves duplicates that degrade Marketing Automation<\/strong> outcomes.<\/p>\n\n\n\n

                              6) What\u2019s the relationship between Dedupe Key and consent management?<\/h3>\n\n\n\n

                              When profiles merge, consent and preferences must be reconciled safely. Your Dedupe Key policy should include explicit rules for which consent states win and how changes are audited.<\/p>\n\n\n\n

                              7) How often should I review my dedupe logic?<\/h3>\n\n\n\n

                              Review whenever you add a new data source, change forms, launch a new channel, or see unexpected shifts in metrics. For mature Direct & Retention Marketing<\/strong> programs, a quarterly review plus ongoing monitoring is a practical baseline.<\/p>\n","protected":false},"excerpt":{"rendered":"

                              A **Dedupe Key** is a deliberate identifier used to detect and prevent duplicates across customer records, events, and campaign actions. In **Direct & Retention Marketing**, where the goal is to build durable customer relationships through email, SMS, push, and lifecycle messaging, duplicates are more than a data nuisance\u2014they create wasted spend, inflated metrics, and poor customer experiences.<\/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":[1894],"tags":[],"class_list":["post-8113","post","type-post","status-publish","format-standard","hentry","category-marketing-automation"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8113","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=8113"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8113\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=8113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=8113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=8113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}