{"id":10571,"date":"2026-03-29T14:51:55","date_gmt":"2026-03-29T14:51:55","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/paid-social-naming-convention\/"},"modified":"2026-03-29T14:51:55","modified_gmt":"2026-03-29T14:51:55","slug":"paid-social-naming-convention","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/paid-social-naming-convention\/","title":{"rendered":"Paid Social Naming Convention: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Paid Social"},"content":{"rendered":"\n

A Paid Social Naming Convention<\/strong> is a standardized way to name your campaigns, ad sets (or targeting groups), ads, and creatives so that performance data is easy to read, filter, compare, and automate. In Paid Marketing<\/strong>, where teams may run dozens (or thousands) of experiments across regions, audiences, and funnel stages, naming is not cosmetic\u2014it\u2019s operational infrastructure.<\/p>\n\n\n\n

Within Paid Social<\/strong>, consistent naming becomes the bridge between what you intended<\/em> to run (strategy) and what you can prove<\/em> worked (measurement). A strong Paid Social Naming Convention<\/strong> reduces reporting friction, speeds up optimization, and prevents costly mistakes like misapplied budgets, mislabeled tests, or untraceable creative results.<\/p>\n\n\n\n

What Is Paid Social Naming Convention?<\/h2>\n\n\n\n

A Paid Social Naming Convention<\/strong> is a documented, repeatable taxonomy for labeling assets in social advertising accounts\u2014typically at the campaign, ad set, and ad level\u2014using a consistent format and agreed-upon fields. It is designed to make data understandable to humans and usable by systems.<\/p>\n\n\n\n

The core concept is simple: names should encode meaning<\/strong>. Instead of \u201cCampaign 12\u201d or \u201cRetargeting test,\u201d a structured name can communicate objective, geography, product, audience, creative concept, and timeframe in a predictable order.<\/p>\n\n\n\n

From a business perspective, a Paid Social Naming Convention<\/strong> supports faster decision-making. When leaders ask \u201cWhich creative concept drove lower acquisition costs in Germany for Product A?\u201d you can answer without manual detective work.<\/p>\n\n\n\n

In Paid Marketing<\/strong>, naming conventions complement other foundations like tracking plans, attribution settings, and reporting dashboards. Inside Paid Social<\/strong>, the naming layer helps you manage complexity across audiences, placements, creative iterations, and optimization events.<\/p>\n\n\n\n

Why Paid Social Naming Convention Matters in Paid Marketing<\/h2>\n\n\n\n

A Paid Social Naming Convention<\/strong> matters because modern Paid Marketing<\/strong> is a volume game: more segments, more experiments, more creative variations, and more stakeholders. Without naming discipline, performance insights get trapped in messy accounts and inconsistent spreadsheets.<\/p>\n\n\n\n

Strategically, naming makes your Paid Social<\/strong> program comparable over time. You can run multiple quarters of tests and still reliably group results by funnel stage, offer type, or creative theme\u2014even as team members change.<\/p>\n\n\n\n

The business value is tangible:<\/p>\n\n\n\n

    \n
  • Cleaner reporting reduces analyst hours and agency overhead.<\/li>\n
  • Better segmentation improves budget allocation decisions.<\/li>\n
  • Stronger governance lowers the risk of launching the wrong message to the wrong audience.<\/li>\n<\/ul>\n\n\n\n

    Teams that implement a consistent Paid Social Naming Convention<\/strong> often gain a competitive advantage because they can learn faster. In Paid Marketing<\/strong>, speed of learning is often more important than any single optimization tactic.<\/p>\n\n\n\n

    How Paid Social Naming Convention Works<\/h2>\n\n\n\n

    A Paid Social Naming Convention<\/strong> is less about \u201ctechnology\u201d and more about a practical workflow that teams follow consistently.<\/p>\n\n\n\n

      \n
    1. \n

      Input \/ trigger<\/strong>\n A campaign request is created: a new product launch, a seasonal promotion, a retargeting refresh, or a creative testing sprint. The request includes key details like objective, audience, market, and offer.<\/p>\n<\/li>\n

    2. \n

      Analysis \/ planning<\/strong>\n The team decides the classification fields that must be represented in names (for example: channel, objective, geo, funnel stage, product, audience type, creative concept, and date). They also decide which fields are mandatory vs optional.<\/p>\n<\/li>\n

    3. \n

      Execution \/ application<\/strong>\n When building campaigns in Paid Social<\/strong>, the buyer applies the convention to each naming level (campaign, ad set, ad). Ideally, names are generated from a template or a controlled dropdown system to avoid typos and inconsistent abbreviations.<\/p>\n<\/li>\n

    4. \n

      Output \/ outcome<\/strong>\n Reporting tools, pivot tables, and dashboards can now filter and group results reliably. In Paid Marketing<\/strong>, this improves cross-campaign comparisons, test readouts, and budget governance.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      The key is consistency: a \u201cgood\u201d Paid Social Naming Convention<\/strong> is one your team actually follows\u2014and one that continues to work as your program scales.<\/p>\n\n\n\n

      Key Components of Paid Social Naming Convention<\/h2>\n\n\n\n

      A durable Paid Social Naming Convention<\/strong> usually includes the following components:<\/p>\n\n\n\n

      A shared taxonomy (the dictionary)<\/h3>\n\n\n\n

      This defines the fields you\u2019ll encode and the allowed values. Examples: standard geo codes, funnel stage labels, objective names, product lines, and audience categories.<\/p>\n\n\n\n

      A naming structure (the template)<\/h3>\n\n\n\n

      Most teams use a separator-based format such as [Field]=Value<\/code> pairs or a fixed sequence. The goal is predictable parsing\u2014by humans and by formulas.<\/p>\n\n\n\n

      Field governance (who decides what)<\/h3>\n\n\n\n

      In Paid Marketing<\/strong>, naming breaks when everyone invents their own abbreviations. Assign ownership: who can add new audience codes, new product labels, or new creative concept names.<\/p>\n\n\n\n

      QA and enforcement<\/h3>\n\n\n\n

      A Paid Social Naming Convention<\/strong> needs guardrails: checklists before launch, periodic audits, and a way to flag noncompliant names.<\/p>\n\n\n\n

      Reporting alignment<\/h3>\n\n\n\n

      Your naming fields should map to how you report and how leadership asks questions. If your weekly business review is organized by region and funnel stage, those fields should be easy to filter in Paid Social<\/strong> exports.<\/p>\n\n\n\n

      Types of Paid Social Naming Convention<\/h2>\n\n\n\n

      There aren\u2019t strict \u201cofficial\u201d types, but there are practical approaches teams use in Paid Social<\/strong> and Paid Marketing<\/strong>:<\/p>\n\n\n\n

      1) Hierarchical by asset level<\/h3>\n\n\n\n
        \n
      • Campaign name<\/strong>: high-level intent (objective, product, geo, funnel stage)<\/li>\n
      • Ad set \/ targeting group<\/strong>: audience definition (prospecting vs retargeting, interest cluster, lookalike tier, exclusion logic)<\/li>\n
      • Ad name<\/strong>: creative attributes (format, concept, hook, version, influencer\/UGC tag)<\/li>\n<\/ul>\n\n\n\n

        This is the most common and scales well.<\/p>\n\n\n\n

        2) Human-readable vs code-based<\/h3>\n\n\n\n
          \n
        • Human-readable<\/strong> conventions favor clarity in-platform (great for collaboration).<\/li>\n
        • Code-based<\/strong> conventions optimize for compactness and strict parsing (great for automation and data pipelines).<\/li>\n<\/ul>\n\n\n\n

          Many teams blend both: readable words with controlled abbreviations.<\/p>\n\n\n\n

          3) Reporting-first vs ops-first<\/h3>\n\n\n\n
            \n
          • Reporting-first<\/strong> naming prioritizes dimensions used in dashboards.<\/li>\n
          • Ops-first<\/strong> naming prioritizes build speed, QA, and launch safety.<\/li>\n<\/ul>\n\n\n\n

            A mature Paid Social Naming Convention<\/strong> balances both.<\/p>\n\n\n\n

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

            Below are practical examples you can adapt. The point is not the exact tokens, but the consistency and meaning.<\/p>\n\n\n\n

            Example 1: Multi-market acquisition campaign<\/h3>\n\n\n\n

            Use case:<\/strong> A SaaS brand runs acquisition in two countries with different offers.\n– Campaign: PS | ACQ | ProductA | US | Prospecting | Q2-2026<\/code>\n– Ad set: Broad | Age25-54 | ExclCustomers<\/code>\n– Ad: Video | DemoHook | v03 | 15s<\/code><\/p>\n\n\n\n

            In Paid Marketing<\/strong>, this makes it easy to compare CAC by market and isolate which hook performed best in Paid Social<\/strong>.<\/p>\n\n\n\n

            Example 2: Retargeting with funnel-stage clarity<\/h3>\n\n\n\n

            Use case:<\/strong> An ecommerce store retargets site visitors with a limited-time discount.\n– Campaign: PS | CONV | BrandX | UK | Retargeting | CartAbandon | Week12<\/code>\n– Ad set: ViewedProduct_7d | ExclPurchasers_180d<\/code>\n– Ad: Static | Offer20Off | v01<\/code><\/p>\n\n\n\n

            A consistent Paid Social Naming Convention<\/strong> ensures retargeting doesn\u2019t get mixed into prospecting results and keeps incrementality discussions grounded.<\/p>\n\n\n\n

            Example 3: Creative testing sprint with version control<\/h3>\n\n\n\n

            Use case:<\/strong> A subscription app tests 10 UGC concepts against one audience.\n– Campaign: PS | ACQ | App | CA | Prospecting | CreativeTest | Mar-2026<\/code>\n– Ad set: InterestCluster_Fitness | Optimize_Purchase<\/code>\n– Ad: UGC | PainPoint_Sleep | Creator05 | v02<\/code><\/p>\n\n\n\n

            This structure helps the team summarize learnings by concept, creator, and version\u2014without manually opening each ad.<\/p>\n\n\n\n

            Benefits of Using Paid Social Naming Convention<\/h2>\n\n\n\n

            A strong Paid Social Naming Convention<\/strong> produces compounding returns because it reduces friction everywhere your program touches.<\/p>\n\n\n\n

            Performance improvements<\/h3>\n\n\n\n

            When assets are clearly labeled, you can spot patterns faster\u2014such as which creative themes drive higher conversion rates in Paid Social<\/strong> or which audiences are saturating.<\/p>\n\n\n\n

            Cost savings<\/h3>\n\n\n\n

            Clean naming reduces:\n– time spent cleaning exports,\n– mistakes during launch,\n– rework when stakeholders ask for breakdowns.<\/p>\n\n\n\n

            In Paid Marketing<\/strong>, fewer hours spent wrangling data means more hours spent improving strategy.<\/p>\n\n\n\n

            Efficiency and scale<\/h3>\n\n\n\n

            Naming consistency enables repeatable build processes. Agencies and in-house teams can onboard faster, hand off accounts more cleanly, and scale experiments without losing track of what\u2019s running.<\/p>\n\n\n\n

            Better customer and audience experience<\/h3>\n\n\n\n

            While naming is internal, it indirectly improves customer experience by reducing mis-targeting and ensuring the right message reaches the right stage of the funnel.<\/p>\n\n\n\n

            Challenges of Paid Social Naming Convention<\/h2>\n\n\n\n

            Even well-designed conventions fail without adoption and maintenance.<\/p>\n\n\n\n

            Inconsistent adoption across teams<\/h3>\n\n\n\n

            Different buyers may prefer different shorthand. Without governance, a Paid Social Naming Convention<\/strong> becomes \u201csuggested,\u201d not \u201cstandard.\u201d<\/p>\n\n\n\n

            Character limits and readability<\/h3>\n\n\n\n

            Some platforms restrict name length. Overloading names with too many fields makes them hard to scan and more error-prone.<\/p>\n\n\n\n

            Changing strategy and org structure<\/h3>\n\n\n\n

            Paid Marketing<\/strong> evolves\u2014new products, new regions, new funnel definitions. If the convention can\u2019t adapt, teams will bypass it.<\/p>\n\n\n\n

            Measurement and attribution limitations<\/h3>\n\n\n\n

            Naming improves organization<\/em>, not truth. If conversion tracking is incomplete or attribution is constrained by privacy changes, naming won\u2019t fix the underlying measurement gaps\u2014but it will help you diagnose them faster.<\/p>\n\n\n\n

            Best Practices for Paid Social Naming Convention<\/h2>\n\n\n\n

            Start with reporting questions, not naming aesthetics<\/h3>\n\n\n\n

            List the top 10 questions stakeholders ask (by product, region, funnel stage, offer, creative concept). Design your Paid Social Naming Convention<\/strong> so those dimensions are visible and consistent.<\/p>\n\n\n\n

            Use mandatory fields and keep optional fields limited<\/h3>\n\n\n\n

            A practical baseline is:\n– Channel indicator (to align across Paid Marketing<\/strong>)\n– Objective or optimization event\n– Product\/brand\n– Geo\/market\n– Funnel stage (prospecting vs retargeting)\n– Time marker (month\/quarter or sprint)<\/p>\n\n\n\n

            Optional fields can live at the ad set or ad level.<\/p>\n\n\n\n

            Standardize values with a controlled vocabulary<\/h3>\n\n\n\n

            Decide once: do you use US<\/code> or USA<\/code>? Retargeting<\/code> or RT<\/code>? Then lock it. The quality of a Paid Social Naming Convention<\/strong> is mostly the quality of its dictionary.<\/p>\n\n\n\n

            Build a QA checklist before launch<\/h3>\n\n\n\n

            Simple checks catch most errors:\n– required fields present,\n– correct separators,\n– no free-typed geo codes,\n– version numbers incremented correctly.<\/p>\n\n\n\n

            Document ownership and change control<\/h3>\n\n\n\n

            Assign a single owner (or small committee) for updates. Publish changes with examples so your Paid Social<\/strong> team doesn\u2019t drift into unofficial variants.<\/p>\n\n\n\n

            Tools Used for Paid Social Naming Convention<\/h2>\n\n\n\n

            A Paid Social Naming Convention<\/strong> is operationalized through systems, not just a doc.<\/p>\n\n\n\n

              \n
            • Ad platforms<\/strong>: Where names are applied and exported. Many teams rely on saved build templates and import\/export workflows.<\/li>\n
            • Spreadsheets<\/strong>: Common for naming generators, dropdown-controlled values, and bulk build sheets.<\/li>\n
            • Analytics tools<\/strong>: Used to validate that naming fields align with performance reporting and conversion events.<\/li>\n
            • Reporting dashboards \/ BI<\/strong>: Where naming fields are turned into filters, groupings, and consistent charts across Paid Marketing<\/strong>.<\/li>\n
            • Automation tools<\/strong>: Used to create templates, enforce formats, run audits, or flag noncompliant names.<\/li>\n
            • CRM systems<\/strong>: Helpful for aligning naming with lifecycle stages and customer segments, especially when Paid Social<\/strong> supports lead gen and pipeline reporting.<\/li>\n
            • Data warehouses<\/strong>: Useful for parsing naming strings into structured columns at scale, enabling robust analysis over time.<\/li>\n<\/ul>\n\n\n\n

              The \u201cbest\u201d stack is the one that reduces manual typing and increases compliance.<\/p>\n\n\n\n

              Metrics Related to Paid Social Naming Convention<\/h2>\n\n\n\n

              You don\u2019t measure naming for vanity\u2014you measure it to protect performance and decision quality in Paid Marketing<\/strong>.<\/p>\n\n\n\n

              Governance and efficiency metrics<\/h3>\n\n\n\n
                \n
              • Naming compliance rate<\/strong>: % of active campaigns\/ad sets\/ads following the standard.<\/li>\n
              • Audit error rate<\/strong>: number of missing fields, invalid values, or inconsistent separators.<\/li>\n
              • Time-to-report<\/strong>: hours to produce weekly performance readouts before vs after adopting the convention.<\/li>\n
              • Rework rate<\/strong>: how often campaigns are renamed or rebuilt due to naming\/structure confusion.<\/li>\n<\/ul>\n\n\n\n

                Performance metrics enabled by good naming<\/h3>\n\n\n\n

                Once naming is consistent, you can confidently compare:\n– CPA\/CAC by funnel stage (prospecting vs retargeting),\n– ROAS by product line,\n– conversion rate by creative concept or format,\n– frequency and reach by audience type in Paid Social<\/strong>.<\/p>\n\n\n\n

                The convention doesn\u2019t change these metrics directly; it makes them more trustworthy and easier to act on.<\/p>\n\n\n\n

                Future Trends of Paid Social Naming Convention<\/h2>\n\n\n\n

                Paid Social Naming Convention<\/strong> practices are evolving as platforms, privacy, and automation change Paid Marketing<\/strong>.<\/p>\n\n\n\n

                AI-assisted build and auto-labeling<\/h3>\n\n\n\n

                As teams use automated campaign creation and creative iteration, naming must keep up. Expect more template-driven naming and automated validation to prevent messy, machine-generated asset sprawl.<\/p>\n\n\n\n

                More emphasis on first-party data alignment<\/h3>\n\n\n\n

                With ongoing privacy constraints, marketers increasingly align Paid Social<\/strong> structure to CRM segments and lifecycle stages. Naming will reflect customer state (lead, trial, subscriber) more explicitly to support measurement and budget decisions.<\/p>\n\n\n\n

                Standardization across channels<\/h3>\n\n\n\n

                Organizations want one view of Paid Marketing<\/strong> across search, social, video, and retail media. Naming conventions will increasingly share a common taxonomy, with channel-specific fields added only where necessary.<\/p>\n\n\n\n

                Better parsing and governance<\/h3>\n\n\n\n

                More teams will treat naming as data engineering: parseable strings, strict dictionaries, and automated audits, because reporting quality depends on it.<\/p>\n\n\n\n

                Paid Social Naming Convention vs Related Terms<\/h2>\n\n\n\n

                Paid Social Naming Convention vs UTM naming convention<\/h3>\n\n\n\n

                A Paid Social Naming Convention<\/strong> labels in-platform assets (campaigns, ad sets, ads). UTM conventions label the tracking parameters appended to links for analytics. They should be aligned, but they solve different problems: platform organization vs downstream traffic attribution.<\/p>\n\n\n\n

                Paid Social Naming Convention vs campaign taxonomy<\/h3>\n\n\n\n

                A campaign taxonomy is the broader classification system (dimensions, definitions, hierarchies). The Paid Social Naming Convention<\/strong> is the practical encoding of that taxonomy into names people and systems actually use.<\/p>\n\n\n\n

                Paid Social Naming Convention vs tracking plan<\/h3>\n\n\n\n

                A tracking plan defines what events, conversions, and properties you measure. Naming conventions help organize how you run and analyze campaigns, but they don\u2019t replace instrumentation. In Paid Marketing<\/strong>, you usually need both for reliable insights.<\/p>\n\n\n\n

                Who Should Learn Paid Social Naming Convention<\/h2>\n\n\n\n
                  \n
                • Marketers and media buyers<\/strong> benefit by launching faster, avoiding errors, and optimizing Paid Social<\/strong> with cleaner comparisons.<\/li>\n
                • Analysts<\/strong> benefit by reducing manual cleanup and enabling repeatable reporting across Paid Marketing<\/strong>.<\/li>\n
                • Agencies<\/strong> benefit by standardizing client operations, improving handoffs, and proving value with clearer insights.<\/li>\n
                • Business owners and founders<\/strong> benefit by getting more readable performance summaries and fewer ambiguous \u201cit depends\u201d answers.<\/li>\n
                • Developers and marketing ops<\/strong> benefit by enabling automation, data pipelines, and reliable parsing of campaign metadata into structured fields.<\/li>\n<\/ul>\n\n\n\n

                  Summary of Paid Social Naming Convention<\/h2>\n\n\n\n

                  A Paid Social Naming Convention<\/strong> is a standardized method for naming campaigns, targeting groups, and ads so that Paid Social<\/strong> performance can be measured, managed, and scaled reliably. It matters because Paid Marketing<\/strong> depends on speed, clarity, and accurate comparisons\u2014none of which are possible when naming is inconsistent. Implemented well, it supports governance, reduces reporting time, and helps teams translate strategy into measurable outcomes across Paid Social<\/strong> programs.<\/p>\n\n\n\n

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

                  1) What is a Paid Social Naming Convention?<\/h3>\n\n\n\n

                  A Paid Social Naming Convention<\/strong> is a consistent template and dictionary for naming campaigns, ad sets, and ads so teams can filter, compare, and automate reporting without confusion or manual cleanup.<\/p>\n\n\n\n

                  2) How detailed should a naming convention be?<\/h3>\n\n\n\n

                  Detailed enough to answer your recurring reporting questions (objective, geo, product, funnel stage, audience type, creative concept), but not so detailed that names become unreadable or exceed platform limits.<\/p>\n\n\n\n

                  3) Should Paid Social names match naming in other Paid Marketing channels?<\/h3>\n\n\n\n

                  Yes, wherever it helps cross-channel reporting. A shared baseline taxonomy (product, geo, funnel stage) makes Paid Marketing<\/strong> analysis easier, while keeping channel-specific fields only where they add real value.<\/p>\n\n\n\n

                  4) Where should I put audience details\u2014in the campaign name or ad set name?<\/h3>\n\n\n\n

                  Typically in the ad set (or targeting group) name, because audiences are what differ most at that level in Paid Social<\/strong>. Keep the campaign name focused on objective, product, geo, and funnel stage.<\/p>\n\n\n\n

                  5) What are common mistakes teams make with Paid Social Naming Convention?<\/h3>\n\n\n\n

                  Common issues include inconsistent abbreviations, missing required fields, unclear versioning for creatives, and letting each team member invent new labels without governance.<\/p>\n\n\n\n

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

                  Use templates with dropdown values, a short pre-launch QA checklist, and periodic audits. In mature Paid Marketing<\/strong> teams, lightweight automation can flag errors before campaigns go live.<\/p>\n\n\n\n

                  7) Does a naming convention improve Paid Social performance directly?<\/h3>\n\n\n\n

                  Not directly, but it improves the speed and quality of decisions. By making results easier to interpret, a Paid Social Naming Convention<\/strong> helps teams optimize faster, cut wasted spend, and scale what works with confidence.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  A **Paid Social Naming Convention** is a standardized way to name your campaigns, ad sets (or targeting groups), ads, and creatives so that performance data is easy to read, filter, compare, and automate. In **Paid Marketing**, where teams may run dozens (or thousands) of experiments across regions, audiences, and funnel stages, naming is not cosmetic\u2014it\u2019s operational infrastructure.<\/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":[1910],"tags":[],"class_list":["post-10571","post","type-post","status-publish","format-standard","hentry","category-paid-social"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/10571","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=10571"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/10571\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=10571"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=10571"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=10571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}