{"id":7302,"date":"2026-03-24T07:41:48","date_gmt":"2026-03-24T07:41:48","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/gclid-upload\/"},"modified":"2026-03-24T07:41:48","modified_gmt":"2026-03-24T07:41:48","slug":"gclid-upload","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/gclid-upload\/","title":{"rendered":"Gclid Upload: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Tracking"},"content":{"rendered":"\n

Gclid Upload is a method used in Conversion & Measurement<\/strong> to connect ad clicks to conversions that happen later or outside a website\u2014often in a CRM, a point-of-sale system, or a sales pipeline. It plays a key role in Tracking<\/strong> because it helps preserve the relationship between the original paid click and the eventual outcome, even when that outcome isn\u2019t captured by a standard web pixel.<\/p>\n\n\n\n

Modern Conversion & Measurement<\/strong> strategies increasingly rely on first-party data, server-side workflows, and offline event reconciliation. In that environment, Gclid Upload matters because it improves attribution quality for paid search campaigns, enables more accurate bidding optimization, and provides clearer reporting on what actually drives revenue\u2014not just what drives form fills.<\/p>\n\n\n\n

What Is Gclid Upload?<\/h2>\n\n\n\n

Gclid Upload<\/strong> is the process of sending conversion records back to an ad platform using the Google Click Identifier (gclid) captured at the time of the ad click. In simple terms: you store the click ID when a user arrives, and later you \u201cupload\u201d a conversion tied to that click ID when a meaningful action occurs (like a qualified lead, a closed deal, or a signed contract).<\/p>\n\n\n\n

The core concept is reconciliation: linking a click to a downstream business event. Instead of relying only on browser-based Tracking<\/strong>, Gclid Upload creates a durable join key between marketing acquisition data and back-office conversion data.<\/p>\n\n\n\n

From a business perspective, Gclid Upload is about measuring what you actually value. Many organizations care more about revenue, profit, retention, or sales-qualified leads than they do about immediate on-site micro-conversions. In Conversion & Measurement<\/strong>, this approach helps align reporting with real outcomes.<\/p>\n\n\n\n

Within Tracking<\/strong>, Gclid Upload sits at the intersection of ad click capture, first-party data storage, and conversion event submission. It\u2019s not just a technical step\u2014it\u2019s a measurement design choice that affects how campaigns are evaluated and optimized.<\/p>\n\n\n\n

Why Gclid Upload Matters in Conversion & Measurement<\/h2>\n\n\n\n

Gclid Upload improves strategic decision-making by upgrading attribution from \u201cwhat happened on the site\u201d to \u201cwhat happened in the business.\u201d That shift is crucial when the customer journey includes phone calls, sales demos, invoicing, or onboarding workflows that happen days or weeks after the click.<\/p>\n\n\n\n

In Conversion & Measurement<\/strong>, better data quality translates into better budget allocation. When conversion feedback reflects actual qualified outcomes, optimization systems can prioritize the keywords, audiences, and creatives that generate value\u2014not noise.<\/p>\n\n\n\n

Key outcomes often include:<\/p>\n\n\n\n

    \n
  • Smarter optimization<\/strong>: Bid strategies perform better when conversion signals represent true success states (for example, closed-won deals).<\/li>\n
  • More defensible ROI<\/strong>: Finance and leadership teams trust reporting more when conversions reflect CRM reality.<\/li>\n
  • Competitive advantage<\/strong>: Teams that implement reliable Tracking<\/strong> loops can iterate faster and out-learn competitors who rely on shallow metrics.<\/li>\n<\/ul>\n\n\n\n

    If you run longer sales cycles, lead qualification stages, or offline fulfillment, Gclid Upload is often one of the highest-leverage upgrades you can make to your Conversion & Measurement<\/strong> stack.<\/p>\n\n\n\n

    How Gclid Upload Works<\/h2>\n\n\n\n

    Although implementations vary, Gclid Upload typically follows a practical workflow that connects click capture to offline conversion feedback:<\/p>\n\n\n\n

      \n
    1. \n

      Input \/ Trigger: capture the gclid<\/strong>\n – A user clicks a paid ad and lands on your site.\n – The landing URL contains a gclid parameter.\n – Your site or tag setup reads the gclid and stores it in a first-party context (often in a cookie and then in your database when a form is submitted).<\/p>\n<\/li>\n

    2. \n

      Processing: store and join the click ID to a person or lead<\/strong>\n – When the user becomes identifiable (form fill, account creation, call tracking association), the gclid is saved alongside the lead\/contact record.\n – Data hygiene matters: you need consistent timestamps, lead IDs, and deduplication rules for reliable Tracking<\/strong>.<\/p>\n<\/li>\n

    3. \n

      Execution: create conversion records for upload<\/strong>\n – When a meaningful event occurs (qualified lead, opportunity created, purchase completed offline), you generate a conversion record that includes:<\/p>\n

        \n
      • The gclid<\/li>\n
      • The conversion name\/action<\/li>\n
      • The conversion time<\/li>\n
      • The conversion value (optional but recommended)<\/li>\n
      • This step is where Conversion & Measurement<\/strong> becomes \u201cbusiness-aware.\u201d<\/li>\n<\/ul>\n<\/li>\n
      • \n

        Output \/ Outcome: upload and use in reporting\/optimization<\/strong>\n – The conversion records are sent to the ad platform through an import or API process.\n – Reporting then attributes those conversions back to campaigns\/keywords.\n – Optimization systems can use the imported conversions as feedback signals.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        In practice, Gclid Upload is most successful when it\u2019s treated as a lifecycle measurement system, not a one-time technical task.<\/p>\n\n\n\n

        Key Components of Gclid Upload<\/h2>\n\n\n\n

        A dependable Gclid Upload program usually includes these elements:<\/p>\n\n\n\n

          \n
        • Data capture layer<\/strong><\/li>\n
        • Landing page parameter capture (gclid)<\/li>\n
        • Consent-aware storage (depending on jurisdiction and policy)<\/li>\n
        • \n

          Form and call flows that preserve the click ID<\/p>\n<\/li>\n

        • \n

          Systems of record<\/strong><\/p>\n<\/li>\n

        • CRM or lead database that stores gclid at the contact\/lead level<\/li>\n
        • Order management or billing system for revenue events<\/li>\n
        • \n

          A data warehouse or central database (common in mature teams)<\/p>\n<\/li>\n

        • \n

          Conversion definitions and governance<\/strong><\/p>\n<\/li>\n

        • Clear mapping of business stages to conversion actions (e.g., \u201cSales Qualified Lead,\u201d \u201cClosed Won\u201d)<\/li>\n
        • Deduplication rules so you don\u2019t inflate results<\/li>\n
        • \n

          Ownership: marketing ops, analytics, and dev responsibilities defined<\/p>\n<\/li>\n

        • \n

          Upload mechanism<\/strong><\/p>\n<\/li>\n

        • Scheduled imports or API-based submission<\/li>\n
        • \n

          Error handling, retry logic, and monitoring<\/p>\n<\/li>\n

        • \n

          Quality assurance<\/strong><\/p>\n<\/li>\n

        • Validation that conversions appear in reporting<\/li>\n
        • Reconciliation between CRM totals and uploaded totals<\/li>\n
        • Ongoing audits of Tracking<\/strong> integrity<\/li>\n<\/ul>\n\n\n\n

          These components turn Gclid Upload from a tactical upload into a sustainable Conversion & Measurement<\/strong> capability.<\/p>\n\n\n\n

          Types of Gclid Upload<\/h2>\n\n\n\n

          Gclid Upload doesn\u2019t have \u201cformal\u201d types in the academic sense, but in real-world Tracking<\/strong> programs, it commonly appears in a few distinct contexts:<\/p>\n\n\n\n

            \n
          1. \n

            Offline conversion import (lead-to-sale)<\/strong>\n – Upload conversions when a lead becomes qualified or a deal closes.\n – Best for B2B, high-consideration services, and long sales cycles.<\/p>\n<\/li>\n

          2. \n

            Call-driven conversion upload<\/strong>\n – Associate phone leads to gclid and upload conversions based on call outcomes.\n – Requires strong call attribution and CRM logging discipline.<\/p>\n<\/li>\n

          3. \n

            Revenue\/value-based upload<\/strong>\n – Include conversion value (and sometimes multiple conversion stages) to improve optimization.\n – Especially powerful for Conversion & Measurement<\/strong> when lead quality varies widely.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

            A practical distinction is also one-time vs. multi-stage uploads<\/strong>. Some organizations upload only \u201cClosed Won,\u201d while others upload both \u201cQualified Lead\u201d and \u201cClosed Won\u201d to support earlier optimization while preserving revenue truth.<\/p>\n\n\n\n

            Real-World Examples of Gclid Upload<\/h2>\n\n\n\n

            Example 1: B2B SaaS lead qualification and closed-won reporting<\/h3>\n\n\n\n

            A SaaS company captures gclid on demo request landing pages and stores it on the lead record. When sales marks a lead as sales-qualified, the team triggers a Gclid Upload for \u201cSQL.\u201d When an opportunity becomes closed-won, they upload a second conversion with the contract value. This Conversion & Measurement<\/strong> approach aligns Tracking<\/strong> with pipeline reality and improves keyword-level optimization.<\/p>\n\n\n\n

            Example 2: Local services with phone-first conversions<\/h3>\n\n\n\n

            A home services business runs paid search campaigns that generate many calls. The marketing team associates the gclid to the caller via call attribution and saves it in the CRM when the booking is created. After the job is completed, they perform a Gclid Upload with the job revenue. This allows Tracking<\/strong> to reflect actual completed jobs\u2014not just calls.<\/p>\n\n\n\n

            Example 3: Retail with offline purchases<\/h3>\n\n\n\n

            A retailer runs ads for in-store promotions. Customers click ads, then purchase in-store using a loyalty identifier. The system ties the loyalty ID back to the captured gclid from the original click and uploads the offline purchase conversion. This improves Conversion & Measurement<\/strong> for campaigns where browser-based signals are incomplete.<\/p>\n\n\n\n

            Benefits of Using Gclid Upload<\/h2>\n\n\n\n

            Gclid Upload can produce meaningful improvements across performance, cost, and operational clarity:<\/p>\n\n\n\n

              \n
            • Better optimization signals<\/strong>: Bidding systems learn from outcomes that matter (qualified leads, revenue), strengthening Conversion & Measurement<\/strong> performance.<\/li>\n
            • Reduced wasted spend<\/strong>: By distinguishing low-quality leads from high-value customers, Tracking<\/strong> supports smarter exclusions and targeting.<\/li>\n
            • Improved cross-team alignment<\/strong>: Marketing and sales can share a consistent view of what \u201cconversion\u201d means.<\/li>\n
            • More accurate ROI measurement<\/strong>: Offline outcomes fill gaps left by browser limitations, cookie loss, or multi-device journeys.<\/li>\n
            • Stronger customer experience<\/strong>: When measurement improves, teams can focus on higher-intent messaging and reduce irrelevant retargeting and lead spam.<\/li>\n<\/ul>\n\n\n\n

              Challenges of Gclid Upload<\/h2>\n\n\n\n

              Despite its value, Gclid Upload introduces real-world complexity that teams should plan for:<\/p>\n\n\n\n

                \n
              • Data integrity risks<\/strong><\/li>\n
              • Missing gclid values due to broken capture, redirects, or form handling issues<\/li>\n
              • Duplicate conversions from repeated uploads or CRM workflow mistakes<\/li>\n
              • \n

                Timezone and timestamp mismatches that break attribution windows<\/p>\n<\/li>\n

              • \n

                Operational and governance hurdles<\/strong><\/p>\n<\/li>\n

              • Sales teams may not consistently update CRM stages, weakening Tracking<\/strong> reliability<\/li>\n
              • \n

                Disagreements about conversion definitions can undermine Conversion & Measurement<\/strong><\/p>\n<\/li>\n

              • \n

                Privacy and compliance considerations<\/strong><\/p>\n<\/li>\n

              • Consent requirements and data retention policies affect what can be stored and for how long<\/li>\n
              • \n

                Changes in browser behavior can reduce the reliability of client-side identifiers unless supported by robust first-party approaches<\/p>\n<\/li>\n

              • \n

                Delayed feedback loops<\/strong><\/p>\n<\/li>\n

              • If conversions happen weeks later, optimization may be slower than with immediate on-site events<\/li>\n<\/ul>\n\n\n\n

                Treat these as design constraints, not reasons to avoid Gclid Upload.<\/p>\n\n\n\n

                Best Practices for Gclid Upload<\/h2>\n\n\n\n

                To implement Gclid Upload reliably and scale it over time:<\/p>\n\n\n\n

                  \n
                • Capture and persist the gclid early<\/strong><\/li>\n
                • Store it on first landing and pass it through forms, scheduling tools, and call flows.<\/li>\n
                • \n

                  Prefer first-party storage and server-side persistence where possible for resilient Tracking<\/strong>.<\/p>\n<\/li>\n

                • \n

                  Define conversion actions that match business value<\/strong><\/p>\n<\/li>\n

                • Start with one or two high-confidence events (e.g., \u201cQualified Lead\u201d or \u201cClosed Won\u201d).<\/li>\n
                • \n

                  Add stages only when you can enforce consistent CRM updates.<\/p>\n<\/li>\n

                • \n

                  Upload values when they\u2019re trustworthy<\/strong><\/p>\n<\/li>\n

                • If you can attach revenue or margin, do it\u2014value-based signals strengthen Conversion & Measurement<\/strong>.<\/li>\n
                • \n

                  Be consistent about currency and whether values represent gross or net.<\/p>\n<\/li>\n

                • \n

                  Implement deduplication logic<\/strong><\/p>\n<\/li>\n

                • \n

                  Ensure each conversion stage is uploaded once per lead\/opportunity unless your measurement plan explicitly allows repeats.<\/p>\n<\/li>\n

                • \n

                  Monitor and reconcile<\/strong><\/p>\n<\/li>\n

                • Regularly compare CRM counts to uploaded counts.<\/li>\n
                • \n

                  Track error rates, rejection reasons, and anomalies by campaign.<\/p>\n<\/li>\n

                • \n

                  Document ownership<\/strong><\/p>\n<\/li>\n

                • Marketing ops owns definitions, analytics owns validation, engineering owns data pipelines\u2014make responsibility explicit.<\/li>\n<\/ul>\n\n\n\n

                  Tools Used for Gclid Upload<\/h2>\n\n\n\n

                  Gclid Upload is usually enabled by a stack of systems rather than a single tool. Common tool categories include:<\/p>\n\n\n\n

                    \n
                  • Ad platforms<\/strong><\/li>\n
                  • \n

                    Where imported conversions are received and used for reporting and optimization (Gclid Upload is inherently tied to paid search ecosystems).<\/p>\n<\/li>\n

                  • \n

                    Analytics tools<\/strong><\/p>\n<\/li>\n

                  • \n

                    Help validate click-to-conversion paths, debug tagging, and support Conversion & Measurement<\/strong> QA.<\/p>\n<\/li>\n

                  • \n

                    Tag management and server-side collection<\/strong><\/p>\n<\/li>\n

                  • \n

                    Used to capture gclid consistently, manage consent, and reduce brittle client-side Tracking<\/strong> dependencies.<\/p>\n<\/li>\n

                  • \n

                    CRM systems<\/strong><\/p>\n<\/li>\n

                  • \n

                    Store gclid at the lead\/contact\/opportunity level and trigger conversion milestones.<\/p>\n<\/li>\n

                  • \n

                    Automation and integration tools<\/strong><\/p>\n<\/li>\n

                  • \n

                    Schedule exports\/imports, transform data formats, and orchestrate pipelines.<\/p>\n<\/li>\n

                  • \n

                    Data warehouses and BI dashboards<\/strong><\/p>\n<\/li>\n

                  • Centralize event data, enable reconciliation, and provide governance-friendly reporting.<\/li>\n<\/ul>\n\n\n\n

                    The \u201cbest\u201d tooling is the combination that preserves identifiers accurately and minimizes manual handling.<\/p>\n\n\n\n

                    Metrics Related to Gclid Upload<\/h2>\n\n\n\n

                    A strong Gclid Upload program is measured on both marketing performance and data quality:<\/p>\n\n\n\n

                    Performance metrics<\/strong>\n– Conversion rate based on uploaded conversions (e.g., click \u2192 qualified lead)\n– Cost per qualified lead \/ cost per sale\n– Revenue per click \/ ROAS (when value is uploaded)\n– Pipeline generated and pipeline velocity (for B2B)<\/p>\n\n\n\n

                    Efficiency and quality metrics<\/strong>\n– Match rate: percentage of CRM conversions that have a valid gclid for upload\n– Upload acceptance rate: percentage of records successfully processed\n– Lag time: median days from click to uploaded conversion\n– Duplicate rate: percentage of conversions rejected or identified as duplicates<\/p>\n\n\n\n

                    These metrics keep Conversion & Measurement<\/strong> grounded in both impact and Tracking<\/strong> reliability.<\/p>\n\n\n\n

                    Future Trends of Gclid Upload<\/h2>\n\n\n\n

                    Several trends are shaping how Gclid Upload evolves within Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

                      \n
                    • More automation, less manual importing<\/strong><\/li>\n
                    • \n

                      API-driven pipelines and near-real-time event streaming reduce delays and mistakes.<\/p>\n<\/li>\n

                    • \n

                      Stronger first-party and server-side approaches<\/strong><\/p>\n<\/li>\n

                    • \n

                      As client-side Tracking<\/strong> becomes less dependable, durable first-party capture and controlled data flows become standard.<\/p>\n<\/li>\n

                    • \n

                      AI-assisted measurement operations<\/strong><\/p>\n<\/li>\n

                    • Anomaly detection for upload failures, suspicious spikes, and pipeline breaks<\/li>\n
                    • \n

                      Predictive modeling to estimate value earlier in the funnel (with careful governance)<\/p>\n<\/li>\n

                    • \n

                      Privacy-driven design<\/strong><\/p>\n<\/li>\n

                    • Consent-aware collection, minimization, and retention controls will increasingly be part of Gclid Upload implementations.<\/li>\n<\/ul>\n\n\n\n

                      The direction is clear: more resilient pipelines, better governance, and measurement that reflects real business outcomes.<\/p>\n\n\n\n

                      Gclid Upload vs Related Terms<\/h2>\n\n\n\n

                      Gclid Upload vs offline conversion tracking<\/strong>\n– Offline conversion tracking is the broader concept: measuring conversions that happen outside the website.\n– Gclid Upload is a specific method of offline conversion tracking that relies on the gclid as the join key for attribution and Tracking<\/strong>.<\/p>\n\n\n\n

                      Gclid Upload vs UTM parameter reporting<\/strong>\n– UTMs help categorize traffic sources in analytics tools.\n– Gclid Upload ties a specific click to a specific conversion for ad-platform attribution and optimization. UTMs are useful for analysis, but they aren\u2019t a direct substitute for click-ID-based Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                      Gclid Upload vs pixel-based (on-site) conversions<\/strong>\n– Pixels capture on-site actions quickly, but can miss offline outcomes and can be impacted by browser restrictions.\n– Gclid Upload is designed to close the loop when the conversion occurs later or elsewhere, strengthening end-to-end Tracking<\/strong>.<\/p>\n\n\n\n

                      Who Should Learn Gclid Upload<\/h2>\n\n\n\n
                        \n
                      • Marketers<\/strong> benefit by optimizing toward qualified outcomes and defending budget with stronger Conversion & Measurement<\/strong> evidence.<\/li>\n
                      • Analysts<\/strong> gain a more complete dataset for attribution, incrementality discussions, and funnel performance.<\/li>\n
                      • Agencies<\/strong> can differentiate by connecting ad spend to CRM outcomes and building higher-trust reporting.<\/li>\n
                      • Business owners and founders<\/strong> get clearer visibility into what actually drives revenue, not just leads.<\/li>\n
                      • Developers and marketing ops<\/strong> are essential for robust Tracking<\/strong> implementation, data pipelines, and system reliability.<\/li>\n<\/ul>\n\n\n\n

                        Summary of Gclid Upload<\/h2>\n\n\n\n

                        Gclid Upload is a Conversion & Measurement<\/strong> approach that sends conversions back to the ad platform using the gclid captured at click time. It matters because it connects paid media to offline or downstream outcomes like qualified leads, closed deals, and revenue\u2014improving both reporting accuracy and optimization. When implemented well, Gclid Upload strengthens Tracking<\/strong> across the full customer lifecycle and helps teams measure what the business truly values.<\/p>\n\n\n\n

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

                        1) What is Gclid Upload used for?<\/h3>\n\n\n\n

                        Gclid Upload is used to attribute offline or delayed conversions (like CRM milestones or completed sales) back to the original ad click, improving Conversion & Measurement<\/strong> and optimization quality.<\/p>\n\n\n\n

                        2) Do I need a CRM to do Gclid Upload?<\/h3>\n\n\n\n

                        A CRM is common, but not strictly required. You do need a reliable system to store the gclid alongside an identifiable record and to log conversion events in a structured way for Tracking<\/strong> and upload.<\/p>\n\n\n\n

                        3) How does Gclid Upload affect Tracking accuracy?<\/h3>\n\n\n\n

                        It typically increases Tracking<\/strong> accuracy for long journeys because it reduces reliance on browser-only measurement and links conversions to real business events.<\/p>\n\n\n\n

                        4) What are the most common reasons a Gclid Upload fails?<\/h3>\n\n\n\n

                        Common causes include missing or malformed gclid values, incorrect timestamps\/timezones, mismatched conversion action names, duplicate uploads, or insufficient data governance in the source system.<\/p>\n\n\n\n

                        5) Should I upload qualified leads, closed deals, or both?<\/h3>\n\n\n\n

                        In Conversion & Measurement<\/strong>, start with the most trustworthy event (often closed deals). If volume is too low for optimization, add qualified leads as an earlier signal\u2014provided your qualification process is consistent.<\/p>\n\n\n\n

                        6) How long after the click can I upload a conversion?<\/h3>\n\n\n\n

                        The allowable window depends on platform rules and configuration, but from a practical standpoint you should upload as soon as the conversion is confirmed and ensure your timestamps are accurate for attribution and Tracking<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

                        Gclid Upload is a method used in **Conversion & Measurement** to connect ad clicks to conversions that happen later or outside a website\u2014often in a CRM, a point-of-sale system, or a sales pipeline. It plays a key role in **Tracking** because it helps preserve the relationship between the original paid click and the eventual outcome, even when that outcome isn\u2019t captured by a standard web pixel.<\/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":[1890],"tags":[],"class_list":["post-7302","post","type-post","status-publish","format-standard","hentry","category-tracking"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7302","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=7302"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7302\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7302"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7302"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}