{"id":7004,"date":"2026-03-23T20:49:59","date_gmt":"2026-03-23T20:49:59","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/analytics-naming-convention\/"},"modified":"2026-03-23T20:49:59","modified_gmt":"2026-03-23T20:49:59","slug":"analytics-naming-convention","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/analytics-naming-convention\/","title":{"rendered":"Analytics Naming Convention: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Analytics"},"content":{"rendered":"\n

An Analytics Naming Convention<\/strong> is the set of rules your team uses to name campaigns, traffic sources, events, conversions, audiences, and reporting dimensions so they stay consistent over time. In Conversion & Measurement<\/strong>, naming is not \u201cadministrative work\u201d\u2014it\u2019s the foundation that determines whether your reporting is clear, comparable, and actionable. When naming is inconsistent, the same channel shows up under five different labels, conversions can\u2019t be reliably attributed, and teams waste hours reconciling \u201cwhat this means.\u201d<\/p>\n\n\n\n

In modern Analytics<\/strong>, organizations are dealing with more channels, more creative variations, more landing pages, and more privacy constraints than ever. A strong Analytics Naming Convention<\/strong> brings order to that complexity. It improves decision-making, speeds reporting, and helps teams trust the numbers\u2014especially when multiple people and tools touch the data.<\/p>\n\n\n\n

What Is Analytics Naming Convention?<\/h2>\n\n\n\n

An Analytics Naming Convention<\/strong> is a documented standard that defines how you label marketing and measurement data<\/strong> so it can be aggregated, filtered, and compared reliably. It typically covers:<\/p>\n\n\n\n

    \n
  • Acquisition identifiers (source\/medium, campaign names, content names)<\/li>\n
  • On-site or in-app interactions (events, parameters, conversion actions)<\/li>\n
  • Internal taxonomy (product lines, regions, funnel stages, audiences)<\/li>\n<\/ul>\n\n\n\n

    The core concept is simple: names become data<\/strong>. In Conversion & Measurement<\/strong>, you need names that are stable enough to support reporting trends (week-over-week, year-over-year) and flexible enough to reflect real-world campaign changes. In Analytics<\/strong>, consistent naming is what turns raw tracking into insights you can scale across teams.<\/p>\n\n\n\n

    Business-wise, an Analytics Naming Convention<\/strong> reduces ambiguity. It ensures that \u201cSpring Sale,\u201d \u201cspring_sale,\u201d and \u201c2026-springpromo\u201d aren\u2019t treated as separate initiatives. When leadership asks, \u201cHow did paid social perform last quarter?\u201d, your answer depends on whether your naming allows accurate grouping.<\/p>\n\n\n\n

    Why Analytics Naming Convention Matters in Conversion & Measurement<\/h2>\n\n\n\n

    In Conversion & Measurement<\/strong>, naming is strategic because it shapes how performance is interpreted and optimized. If naming is inconsistent, the team spends time cleaning reports instead of improving outcomes.<\/p>\n\n\n\n

    Key reasons an Analytics Naming Convention<\/strong> matters:<\/p>\n\n\n\n

      \n
    • Comparable performance across time:<\/strong> You can evaluate initiatives across weeks, quarters, and markets without rebuilding reports.<\/li>\n
    • Accurate attribution and budgeting:<\/strong> Clean grouping enables better spend decisions (what to scale, pause, or refine).<\/li>\n
    • Faster experimentation:<\/strong> When tests are named consistently, you can evaluate results without manual mapping.<\/li>\n
    • Cross-team alignment:<\/strong> Marketing, product, and sales can use the same definitions of campaign, funnel stage, and conversion.<\/li>\n
    • Competitive advantage:<\/strong> Teams that trust their measurement move faster\u2014especially in channels where timing matters.<\/li>\n<\/ul>\n\n\n\n

      In practice, an Analytics Naming Convention<\/strong> is one of the highest-leverage improvements you can make to your Analytics<\/strong> operations, because it reduces friction everywhere downstream.<\/p>\n\n\n\n

      How Analytics Naming Convention Works<\/h2>\n\n\n\n

      An Analytics Naming Convention<\/strong> is more operational than technical: it works when people follow it and systems reinforce it. A practical workflow looks like this:<\/p>\n\n\n\n

        \n
      1. Input \/ trigger:<\/strong> A campaign is launched, a new landing page is published, or a new conversion event is tracked. Someone must name it\u2014often in an ad platform, email tool, tag management system, or CMS.<\/li>\n
      2. Processing \/ standardization:<\/strong> The name is constructed using the convention (required fields, allowed values, separators, capitalization rules). Many teams also validate names before launch.<\/li>\n
      3. Execution \/ application:<\/strong> The standardized name is applied consistently across tools\u2014ads, links, event parameters, and reporting dimensions\u2014so the same concept is represented the same way.<\/li>\n
      4. Output \/ outcome:<\/strong> In Analytics<\/strong>, reports roll up cleanly (by channel, product, region, funnel stage). In Conversion & Measurement<\/strong>, you can attribute conversions and evaluate ROI with fewer \u201cunknown\u201d or \u201cmiscellaneous\u201d buckets.<\/li>\n<\/ol>\n\n\n\n

        If you treat naming as optional, it becomes \u201ctribal knowledge.\u201d If you treat it as a system, it becomes an asset.<\/p>\n\n\n\n

        Key Components of Analytics Naming Convention<\/h2>\n\n\n\n

        A durable Analytics Naming Convention<\/strong> usually includes both rules and governance. Common components include:<\/p>\n\n\n\n

          \n
        • A taxonomy (controlled vocabulary):<\/strong> Approved values for channels, regions, product lines, funnel stages, and offer types.<\/li>\n
        • A naming format (structure):<\/strong> A defined order of fields (e.g., channel_region_product_offer_audience_date<\/code>).<\/li>\n
        • Delimiters and casing rules:<\/strong> Underscore vs hyphen, lowercase vs Title Case, and rules for spaces and special characters.<\/li>\n
        • Campaign and content identifiers:<\/strong> Clear guidance for campaign name vs ad set vs creative vs landing page variant.<\/li>\n
        • Event and parameter definitions:<\/strong> Standard names for key user actions and their attributes (e.g., form type, plan tier, content category).<\/li>\n
        • Documentation and ownership:<\/strong> Who approves changes, who audits compliance, and where updates are recorded.<\/li>\n
        • Quality checks:<\/strong> Pre-launch validation and post-launch audits to catch errors early.<\/li>\n<\/ul>\n\n\n\n

          In Conversion & Measurement<\/strong>, these components prevent reporting drift as teams scale. In Analytics<\/strong>, they make data easier to model and analyze.<\/p>\n\n\n\n

          Types of Analytics Naming Convention<\/h2>\n\n\n\n

          There aren\u2019t \u201cofficial\u201d universal types, but most organizations apply an Analytics Naming Convention<\/strong> across several contexts:<\/p>\n\n\n\n

            \n
          1. Campaign and traffic naming (acquisition):<\/strong> Naming for campaigns, sources, mediums, and content variations to ensure consistent channel reporting.<\/li>\n
          2. On-site \/ in-app event naming (behavior):<\/strong> Standardizing event names and parameters so actions are tracked consistently across pages, devices, and releases.<\/li>\n
          3. Conversion and funnel naming (outcomes):<\/strong> Clear naming for conversion actions, funnel stages, and micro-conversions so Conversion & Measurement<\/strong> stays coherent.<\/li>\n
          4. Content and SEO taxonomy naming (owned media):<\/strong> Consistent categories, templates, and content types so performance can be compared across themes and formats.<\/li>\n
          5. Internal reporting dimensions (business context):<\/strong> Naming for regions, business units, product SKUs, partner types, or customer segments.<\/li>\n<\/ol>\n\n\n\n

            A mature Analytics Naming Convention<\/strong> connects these layers so acquisition, behavior, and outcomes can be analyzed together.<\/p>\n\n\n\n

            Real-World Examples of Analytics Naming Convention<\/h2>\n\n\n\n

            Below are practical scenarios that show how Analytics Naming Convention<\/strong> improves Conversion & Measurement<\/strong> and day-to-day Analytics<\/strong> work.<\/p>\n\n\n\n

            Example 1: Paid campaign naming across regions<\/h3>\n\n\n\n

            A company runs the same promotion in multiple countries. Without standards, each market names campaigns differently, and global reporting becomes manual. With an Analytics Naming Convention<\/strong>, the campaign naming might follow:<\/p>\n\n\n\n

              \n
            • paid_social_us_productA_spring_offer1_prospecting_2026w12<\/code><\/li>\n
            • paid_social_uk_productA_spring_offer1_prospecting_2026w12<\/code><\/li>\n<\/ul>\n\n\n\n

              Result: In Analytics<\/strong>, global dashboards can roll up by channel<\/code>, region<\/code>, product<\/code>, and audience<\/code>. In Conversion & Measurement<\/strong>, you can compare conversion rate and CPA across markets without re-tagging.<\/p>\n\n\n\n

              Example 2: Event naming for lead capture funnels<\/h3>\n\n\n\n

              A SaaS team tracks form interactions. If one developer names an event LeadFormSubmit<\/code> and another uses form_submit<\/code>, analysis becomes fragmented. A standard event approach might be:<\/p>\n\n\n\n

                \n
              • Event: form_submit<\/code><\/li>\n
              • Parameters: form_type=demo<\/code>, page_type=pricing<\/code>, plan=pro<\/code><\/li>\n<\/ul>\n\n\n\n

                Result: In Analytics<\/strong>, funnel analysis becomes consistent across releases. In Conversion & Measurement<\/strong>, you can attribute qualified leads to the right campaigns and pages.<\/p>\n\n\n\n

                Example 3: Email and lifecycle naming for retention<\/h3>\n\n\n\n

                A team runs onboarding and re-engagement sequences. A clear Analytics Naming Convention<\/strong> might encode lifecycle stage and intent:<\/p>\n\n\n\n

                  \n
                • email_onboarding_day03_featureX_activation<\/code><\/li>\n
                • email_retention_q2_renewal_reminder<\/code><\/li>\n<\/ul>\n\n\n\n

                  Result: In Analytics<\/strong>, you can compare engagement and downstream conversions by lifecycle stage. In Conversion & Measurement<\/strong>, retention efforts are measurable with fewer \u201cuncategorized\u201d messages.<\/p>\n\n\n\n

                  Benefits of Using Analytics Naming Convention<\/h2>\n\n\n\n

                  A well-run Analytics Naming Convention<\/strong> produces tangible advantages:<\/p>\n\n\n\n

                    \n
                  • Higher reporting accuracy:<\/strong> Cleaner rollups reduce misattribution and \u201cother\u201d buckets.<\/li>\n
                  • Faster time-to-insight:<\/strong> Analysts spend less time mapping messy labels and more time answering performance questions.<\/li>\n
                  • Lower operational cost:<\/strong> Fewer hours are wasted fixing tracking, re-building dashboards, or reconciling conflicting numbers.<\/li>\n
                  • Better experimentation velocity:<\/strong> A\/B tests and creative iterations remain comparable because naming encodes what changed.<\/li>\n
                  • Improved stakeholder trust:<\/strong> Executives and channel owners gain confidence when definitions stay consistent.<\/li>\n
                  • More scalable measurement:<\/strong> As channels and markets expand, Conversion & Measurement<\/strong> remains stable instead of collapsing under complexity.<\/li>\n<\/ul>\n\n\n\n

                    In short, Analytics Naming Convention<\/strong> is a force multiplier for your Analytics<\/strong> program.<\/p>\n\n\n\n

                    Challenges of Analytics Naming Convention<\/h2>\n\n\n\n

                    Despite the upside, teams often struggle with implementation. Common challenges include:<\/p>\n\n\n\n

                      \n
                    • Human inconsistency:<\/strong> Different teams interpret \u201cchannel,\u201d \u201ccampaign,\u201d or \u201coffer\u201d differently, especially across regions.<\/li>\n
                    • Tool fragmentation:<\/strong> Names get set in ad platforms, email tools, spreadsheets, and tracking systems\u2014often with no single enforcement point.<\/li>\n
                    • Legacy data:<\/strong> Historical naming may be messy, making trend analysis difficult without a mapping layer.<\/li>\n
                    • Over-engineering risk:<\/strong> A convention that\u2019s too complex becomes hard to follow and encourages shortcuts.<\/li>\n
                    • Change management:<\/strong> Teams need training, reminders, and audits; otherwise the standard degrades.<\/li>\n
                    • Measurement constraints:<\/strong> Privacy changes and limited identifiers can reduce granularity, increasing pressure on naming to carry meaning.<\/li>\n<\/ul>\n\n\n\n

                      A practical Analytics Naming Convention<\/strong> balances rigor with usability so people can follow it under real deadlines.<\/p>\n\n\n\n

                      Best Practices for Analytics Naming Convention<\/h2>\n\n\n\n

                      To make an Analytics Naming Convention<\/strong> stick, focus on clarity, governance, and enforcement:<\/p>\n\n\n\n

                        \n
                      • Start with your reporting questions:<\/strong> Design naming to answer real Conversion & Measurement<\/strong> needs (ROI by channel, CAC by segment, funnel conversion by page type).<\/li>\n
                      • Use a controlled vocabulary:<\/strong> Define approved values (e.g., paid_social<\/code>, not PaidSocial<\/code>, paid-social<\/code>, and social_paid<\/code>).<\/li>\n
                      • Keep it readable and stable:<\/strong> Prefer short, meaningful tokens over dense codes that nobody remembers.<\/li>\n
                      • Document required vs optional fields:<\/strong> Make it obvious what must be present for every campaign\/event.<\/li>\n
                      • Define delimiter and casing rules:<\/strong> Pick one approach and standardize it across tools.<\/li>\n
                      • Build a review step into launch workflows:<\/strong> A quick pre-flight check prevents months of messy data.<\/li>\n
                      • Audit regularly:<\/strong> Review new campaigns and events weekly or monthly; fix issues while they\u2019re small.<\/li>\n
                      • Create a mapping policy:<\/strong> Decide how you\u2019ll handle exceptions, migrations, and historical cleanup.<\/li>\n
                      • Assign ownership:<\/strong> In Analytics<\/strong>, data standards without an owner quietly fail.<\/li>\n<\/ul>\n\n\n\n

                        Tools Used for Analytics Naming Convention<\/h2>\n\n\n\n

                        An Analytics Naming Convention<\/strong> is implemented through process and supported by tooling. Common tool categories include:<\/p>\n\n\n\n

                          \n
                        • Analytics tools:<\/strong> Where naming appears in acquisition reports, event analysis, and conversion reporting; these surfaces reveal inconsistencies quickly.<\/li>\n
                        • Tag management systems:<\/strong> Often the operational layer for enforcing event names and parameters consistently.<\/li>\n
                        • Ad platforms and email platforms:<\/strong> Where campaign names and creative labels originate; standards must be applied at the source.<\/li>\n
                        • CRM systems:<\/strong> Useful for aligning lifecycle stages, lead sources, and revenue outcomes with Conversion & Measurement<\/strong> reporting.<\/li>\n
                        • Reporting dashboards \/ BI tools:<\/strong> Helpful for creating validation views (e.g., \u201cnew campaign names this week\u201d) and for building consistent rollups.<\/li>\n
                        • Spreadsheets and templates:<\/strong> Still one of the most effective ways to operationalize naming rules with dropdowns and examples.<\/li>\n
                        • Project management and documentation systems:<\/strong> Essential for versioning the standard and communicating changes.<\/li>\n<\/ul>\n\n\n\n

                          The goal is not more tools\u2014it\u2019s fewer naming decisions made ad hoc, and more naming applied consistently across your Analytics<\/strong> stack.<\/p>\n\n\n\n

                          Metrics Related to Analytics Naming Convention<\/h2>\n\n\n\n

                          Naming quality can be measured. Useful indicators include:<\/p>\n\n\n\n

                            \n
                          • Percentage of \u201cunassigned\/other\/unknown\u201d traffic:<\/strong> A leading sign that campaign naming or channel grouping is breaking down.<\/li>\n
                          • Naming compliance rate:<\/strong> Share of campaigns\/events that match required format and approved values.<\/li>\n
                          • Duplicate or near-duplicate rate:<\/strong> How often multiple labels represent the same concept (e.g., spring_sale<\/code> vs spring-sale<\/code>).<\/li>\n
                          • Time to produce a weekly performance report:<\/strong> A practical efficiency metric tied directly to naming cleanliness.<\/li>\n
                          • Rework hours:<\/strong> Time spent fixing tracking, reclassifying campaigns, or remapping fields in dashboards.<\/li>\n
                          • Conversion reporting stability:<\/strong> Whether core conversion trends change due to naming fixes rather than real performance changes.<\/li>\n<\/ul>\n\n\n\n

                            In Conversion & Measurement<\/strong>, these metrics help justify the time spent maintaining an Analytics Naming Convention<\/strong>.<\/p>\n\n\n\n

                            Future Trends of Analytics Naming Convention<\/h2>\n\n\n\n

                            Several shifts are changing how Analytics Naming Convention<\/strong> evolves within Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

                              \n
                            • Automation and validation:<\/strong> More teams are using automated checks to flag non-compliant campaign names and event parameters before launch.<\/li>\n
                            • AI-assisted governance:<\/strong> AI can suggest standardized names, detect anomalies, and identify duplicates\u2014but it still needs human-approved vocabularies.<\/li>\n
                            • Privacy-driven measurement design:<\/strong> With fewer identifiers available, consistent naming becomes even more important for aggregation and modeling.<\/li>\n
                            • Server-side and hybrid tracking:<\/strong> As tracking architectures change, naming standards must remain consistent across client and server event sources.<\/li>\n
                            • Personalization at scale:<\/strong> More variants (audiences, creatives, landing pages) increase naming volume, making templates and controlled values essential.<\/li>\n<\/ul>\n\n\n\n

                              The direction is clear: as measurement gets harder, disciplined Analytics Naming Convention<\/strong> becomes more valuable, not less.<\/p>\n\n\n\n

                              Analytics Naming Convention vs Related Terms<\/h2>\n\n\n\n

                              Analytics Naming Convention vs UTM parameters<\/strong>\nUTM parameters are one common place where naming rules are applied for campaign tracking. An Analytics Naming Convention<\/strong> is broader: it covers UTMs, but also event names, conversion labels, internal dimensions, and governance.<\/p>\n\n\n\n

                              Analytics Naming Convention vs tracking plan<\/strong>\nA tracking plan defines what<\/em> you will measure (events, properties, conversions, definitions). An Analytics Naming Convention<\/strong> defines how you will label<\/em> those elements consistently so reporting stays clean over time.<\/p>\n\n\n\n

                              Analytics Naming Convention vs data governance<\/strong>\nData governance is the umbrella practice that covers ownership, access, quality standards, and policies across data. An Analytics Naming Convention<\/strong> is a specific governance artifact focused on naming and taxonomy for Analytics<\/strong> and Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                              Who Should Learn Analytics Naming Convention<\/h2>\n\n\n\n
                                \n
                              • Marketers:<\/strong> To ensure campaigns can be measured accurately and optimized without reporting chaos.<\/li>\n
                              • Analysts:<\/strong> To reduce data cleaning, improve consistency, and build scalable dashboards in Analytics<\/strong>.<\/li>\n
                              • Agencies:<\/strong> To deliver clearer performance reporting across clients, channels, and creative variations in Conversion & Measurement<\/strong>.<\/li>\n
                              • Business owners and founders:<\/strong> To trust ROI reporting, allocate budgets confidently, and avoid \u201cmystery growth\u201d driven by tracking inconsistencies.<\/li>\n
                              • Developers:<\/strong> To implement event tracking with stable, reusable patterns that won\u2019t break reporting after each release.<\/li>\n<\/ul>\n\n\n\n

                                If you touch acquisition, tracking, or reporting, an Analytics Naming Convention<\/strong> directly affects your outcomes.<\/p>\n\n\n\n

                                Summary of Analytics Naming Convention<\/h2>\n\n\n\n

                                An Analytics Naming Convention<\/strong> is a standardized system for naming campaigns, events, conversions, and dimensions so data remains consistent and comparable. It matters because Conversion & Measurement<\/strong> depends on clean grouping, reliable attribution, and trustworthy reporting. Inside Analytics<\/strong>, naming is what turns scattered labels into structured insights that scale across tools, teams, and time.<\/p>\n\n\n\n

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

                                1) What is an Analytics Naming Convention in simple terms?<\/h3>\n\n\n\n

                                An Analytics Naming Convention<\/strong> is a rulebook for how you name campaigns, events, and conversions so they show up consistently in reports and can be analyzed without manual cleanup.<\/p>\n\n\n\n

                                2) How strict should an Analytics Naming Convention be?<\/h3>\n\n\n\n

                                Strict enough that key fields are consistent (channel, region, product, offer), but not so complex that people avoid using it. A small, enforced standard usually beats a perfect but ignored one.<\/p>\n\n\n\n

                                3) Does an Analytics Naming Convention only apply to campaign tracking?<\/h3>\n\n\n\n

                                No. It often starts with campaigns, but it should also cover event names, conversion actions, content taxonomy, and internal reporting dimensions used in Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                                4) How do I enforce naming without slowing down launches?<\/h3>\n\n\n\n

                                Use templates with required fields, controlled vocabularies, and lightweight pre-launch checks. Add periodic audits so issues are corrected quickly, not months later.<\/p>\n\n\n\n

                                5) Which teams should own Analytics Naming Convention governance?<\/h3>\n\n\n\n

                                Typically a shared ownership model works best: marketing operations or growth ops manages campaign rules, while an Analytics<\/strong> or data team owns event\/conversion standards and audits.<\/p>\n\n\n\n

                                6) What are the biggest signs our Analytics naming is broken?<\/h3>\n\n\n\n

                                High \u201cunassigned\/other\u201d traffic, duplicated campaign labels, frequent dashboard fixes, and disagreements over \u201cwhat counts\u201d as a channel or conversion are common indicators.<\/p>\n\n\n\n

                                7) Can better naming improve conversion rate or ROI directly?<\/h3>\n\n\n\n

                                Indirectly, yes. Cleaner Conversion & Measurement<\/strong> helps you identify winners faster, reduce wasted spend, and scale effective tactics with confidence\u2014leading to better ROI over time.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                An **Analytics Naming Convention** is the set of rules your team uses to name campaigns, traffic sources, events, conversions, audiences, and reporting dimensions so they stay consistent over time. In **Conversion & Measurement**, naming is not \u201cadministrative work\u201d\u2014it\u2019s the foundation that determines whether your reporting is clear, comparable, and actionable. When naming is inconsistent, the same channel shows up under five different labels, conversions can\u2019t be reliably attributed, and teams waste hours reconciling \u201cwhat this means.\u201d<\/p>\n","protected":false},"author":10235,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1887],"tags":[],"class_list":["post-7004","post","type-post","status-publish","format-standard","hentry","category-analytics"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7004","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=7004"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7004\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7004"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7004"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7004"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}