{"id":7342,"date":"2026-03-24T09:14:45","date_gmt":"2026-03-24T09:14:45","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/tag\/"},"modified":"2026-03-24T09:14:45","modified_gmt":"2026-03-24T09:14:45","slug":"tag","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/tag\/","title":{"rendered":"Tag: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Tracking"},"content":{"rendered":"\n

In digital marketing, a Tag<\/strong> is one of the most important building blocks of Conversion & Measurement<\/strong>. It\u2019s the mechanism that lets you observe user behavior, attribute outcomes to marketing efforts, and power Tracking<\/strong> across analytics, advertising, and experimentation systems. Without a solid Tag strategy, reporting becomes guesswork: conversions go missing, campaigns get misattributed, and optimization decisions are made on incomplete evidence.<\/p>\n\n\n\n

Tagging matters even more today because measurement is no longer \u201cset and forget.\u201d Privacy changes, browser restrictions, multi-device journeys, and expanding channel mixes have raised the bar for reliable Conversion & Measurement<\/strong>. A well-designed Tag approach helps you collect high-quality data, respect user choices, and keep Tracking<\/strong> consistent across your site, apps, and marketing stack\u2014so your team can improve performance with confidence.<\/p>\n\n\n\n

What Is Tag?<\/h2>\n\n\n\n

A Tag<\/strong> is a small piece of code, configuration, or instruction that sends data from a digital touchpoint (like a website or app) to another system for Tracking<\/strong> and analysis. In practice, a Tag might record a page view, capture a button click, send purchase details, or pass identifiers needed for attribution\u2014depending on what your Conversion & Measurement<\/strong> plan requires.<\/p>\n\n\n\n

At its core, Tagging answers: What happened? Where did it happen? Who\/what caused it (as far as allowed)? And what should we do with that information?<\/em> The business meaning is straightforward: a Tag is how your organization turns user interactions into measurable signals that support marketing decisions, revenue reporting, and product insights.<\/p>\n\n\n\n

Within Conversion & Measurement<\/strong>, a Tag is the collection layer. It sits between your digital experiences (site\/app) and your downstream tools (analytics, ad platforms, data warehouses). Inside Tracking<\/strong>, it\u2019s the \u201cinstrumentation\u201d that makes user journeys observable and comparable over time.<\/p>\n\n\n\n

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

A strong Tag foundation improves both strategic clarity and execution speed. When your Tag plan is consistent, you can trust the data that fuels budgeting, creative testing, audience targeting, and lifecycle marketing.<\/p>\n\n\n\n

Key ways Tag supports Conversion & Measurement<\/strong> outcomes:<\/p>\n\n\n\n

    \n
  • Accurate attribution and ROI<\/strong>: Clean Tag data connects spend to results and reduces \u201cunknown\u201d conversions.<\/li>\n
  • Faster optimization loops<\/strong>: Reliable Tracking<\/strong> enables quicker decisions on landing pages, funnels, and ads.<\/li>\n
  • Better audience understanding<\/strong>: Tags capture behavioral signals (with consent) that inform segmentation and personalization.<\/li>\n
  • Cross-team alignment<\/strong>: Shared definitions for events and parameters prevent marketing, analytics, and product teams from arguing over metrics.<\/li>\n
  • Competitive advantage<\/strong>: Organizations with disciplined Tag governance learn faster and waste less budget on unmeasurable tactics.<\/li>\n<\/ul>\n\n\n\n

    How Tag Works<\/h2>\n\n\n\n

    While implementations vary, a Tag typically works through a practical workflow that connects user actions to measurable outputs in your Conversion & Measurement<\/strong> system.<\/p>\n\n\n\n

      \n
    1. \n

      Input or trigger<\/strong>\n Something happens: a page loads, a user clicks \u201cAdd to cart,\u201d a form submits, or a purchase completes. The Tag is configured to fire on specific triggers (page rules, click selectors, event listeners, or app events).<\/p>\n<\/li>\n

    2. \n

      Processing and data packaging<\/strong>\n The Tag collects relevant context\u2014such as page URL, campaign parameters, product details, value, currency, or user state\u2014and formats it into a payload. This is where data quality decisions matter: naming conventions, required fields, and consent checks all shape what gets sent.<\/p>\n<\/li>\n

    3. \n

      Execution and data transmission<\/strong>\n The Tag sends the payload to a destination: an analytics endpoint, an ad platform, a server-side collector, or an internal pipeline. Some Tags run in the browser\/app, while others run on a server to improve control and resilience.<\/p>\n<\/li>\n

    4. \n

      Output and outcome<\/strong>\n Downstream tools store and interpret the data. Reports, audiences, conversion models, and bidding algorithms depend on this Tracking<\/strong> signal. If the Tag is wrong (fires twice, misses parameters, ignores consent), your Conversion & Measurement<\/strong> outputs degrade\u2014often silently.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

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

      A complete Tag setup is more than code snippets. The best programs treat Tagging as a managed system with documentation, QA, and accountability.<\/p>\n\n\n\n

      Core elements<\/h3>\n\n\n\n
        \n
      • Tag specification (measurement plan)<\/strong>: What events you track, why they matter, and the fields required for each event.<\/li>\n
      • Triggers and rules<\/strong>: The conditions that decide when a Tag fires (e.g., page path matches, button click, transaction success).<\/li>\n
      • Variables and parameters<\/strong>: The data points sent with a Tag (e.g., value, item IDs, campaign info, user status).<\/li>\n
      • Destinations<\/strong>: Analytics, ad networks, CRM, CDP, data warehouse, experimentation platforms\u2014where Tracking<\/strong> data is used.<\/li>\n
      • Consent and privacy controls<\/strong>: Rules that respect opt-in\/opt-out choices and limit collection based on jurisdiction and policy.<\/li>\n
      • Governance and ownership<\/strong>: Who can create, edit, approve, and deploy Tag changes; how versioning and rollback work.<\/li>\n<\/ul>\n\n\n\n

        Team responsibilities<\/h3>\n\n\n\n
          \n
        • Marketing<\/strong> defines use cases and conversion definitions in Conversion & Measurement<\/strong>.<\/li>\n
        • Analytics<\/strong> designs the taxonomy, naming conventions, and validation rules.<\/li>\n
        • Developers<\/strong> implement data layers\/app events and ensure performance and security.<\/li>\n
        • Privacy\/legal<\/strong> ensures consent, disclosure, and retention align with requirements.<\/li>\n<\/ul>\n\n\n\n

          Types of Tag<\/h2>\n\n\n\n

          \u201cTag\u201d is a broad concept, but in day-to-day Tracking<\/strong> and Conversion & Measurement<\/strong>, these distinctions are most useful:<\/p>\n\n\n\n

          1) Pageview vs event Tags<\/h3>\n\n\n\n
            \n
          • Pageview Tag<\/strong>: Fires when a page loads; foundational for content and navigation analysis.<\/li>\n
          • Event Tag<\/strong>: Fires on user interactions (clicks, scroll depth, video plays, form submits) and conversion steps.<\/li>\n<\/ul>\n\n\n\n

            2) Conversion vs engagement Tags<\/h3>\n\n\n\n
              \n
            • Conversion Tag<\/strong>: Records outcomes like purchases, leads, subscriptions, or key milestones.<\/li>\n
            • Engagement Tag<\/strong>: Captures behavioral signals that correlate with intent (e.g., product views, filter usage).<\/li>\n<\/ul>\n\n\n\n

              3) Client-side vs server-side Tags<\/h3>\n\n\n\n
                \n
              • Client-side Tag<\/strong>: Runs in a browser or app; faster to deploy but more exposed to blockers and device variability.<\/li>\n
              • Server-side Tag<\/strong>: Runs on controlled infrastructure; can improve reliability, governance, and data minimization.<\/li>\n<\/ul>\n\n\n\n

                4) First-party vs third-party contexts<\/h3>\n\n\n\n
                  \n
                • First-party<\/strong> implementations typically rely on your owned domain\/app and are central to modern Conversion & Measurement<\/strong>.<\/li>\n
                • Third-party<\/strong> contexts depend on external domains\/services and face tighter restrictions in many environments.<\/li>\n<\/ul>\n\n\n\n

                  Real-World Examples of Tag<\/h2>\n\n\n\n

                  Example 1: Ecommerce purchase Tag for revenue reporting<\/h3>\n\n\n\n

                  An online retailer implements a purchase Tag that fires only on the order confirmation page (or confirmed purchase event in the app). It sends order value, currency, transaction ID, and item details. This improves Conversion & Measurement<\/strong> accuracy for revenue, AOV, and product performance while powering Tracking<\/strong> needed for remarketing suppression (exclude recent buyers).<\/p>\n\n\n\n

                  Example 2: Lead-generation form Tag with quality signals<\/h3>\n\n\n\n

                  A B2B company tracks form submissions as conversions, but also sends metadata like form type, lead tier (based on selections), and page category. This Tag enables more than \u201ccounting leads\u201d: it supports Conversion & Measurement<\/strong> for pipeline contribution and helps Tracking<\/strong> distinguish high-intent demo requests from low-intent newsletter signups.<\/p>\n\n\n\n

                  Example 3: Campaign measurement using URL parameters and event Tags<\/h3>\n\n\n\n

                  A brand runs paid social and email campaigns with consistent campaign parameters and an event Tag that records key on-site actions (product view, add to cart, checkout start). Together, these Tags connect sessions to outcomes and reveal where drop-off occurs. In Conversion & Measurement<\/strong>, this clarifies which creatives and audiences drive incremental value, not just clicks.<\/p>\n\n\n\n

                  Benefits of Using Tag<\/h2>\n\n\n\n

                  A disciplined Tag strategy improves both performance and operational efficiency.<\/p>\n\n\n\n

                    \n
                  • Higher data accuracy<\/strong>: Fewer missing conversions, fewer duplicate events, and more stable reporting.<\/li>\n
                  • Lower acquisition cost over time<\/strong>: Better Tracking<\/strong> helps bidding and targeting systems learn from real outcomes.<\/li>\n
                  • Faster experimentation<\/strong>: A\/B tests rely on consistent event collection; reliable Tags shorten time-to-insight.<\/li>\n
                  • Improved customer experience<\/strong>: When Tag governance is strong, pages load faster and fewer unnecessary scripts run.<\/li>\n
                  • Better lifecycle marketing<\/strong>: Clean conversion and engagement Tags support segmentation, onboarding, retention, and win-back programs within Conversion & Measurement<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                    Challenges of Tag<\/h2>\n\n\n\n

                    Tagging is deceptively easy to start and notoriously hard to maintain at scale. Common issues include:<\/p>\n\n\n\n

                      \n
                    • Data quality problems<\/strong>: Tags firing twice, firing on the wrong pages, or sending inconsistent parameters breaks Tracking<\/strong>.<\/li>\n
                    • Attribution ambiguity<\/strong>: Even perfect Tags can\u2019t fully solve cross-device identity, walled gardens, or offline effects.<\/li>\n
                    • Performance and reliability<\/strong>: Too many Tags can slow pages; client-side Tags may be blocked or fail to load.<\/li>\n
                    • Governance debt<\/strong>: Over time, unused Tags accumulate, naming conventions drift, and no one knows what\u2019s \u201csafe to remove.\u201d<\/li>\n
                    • Privacy and consent complexity<\/strong>: Conversion & Measurement<\/strong> must respect user choices; Tag behavior must adapt accordingly.<\/li>\n<\/ul>\n\n\n\n

                      Best Practices for Tag<\/h2>\n\n\n\n

                      Strong Tag programs treat measurement like product engineering: documented, tested, versioned, and continuously improved.<\/p>\n\n\n\n

                      Planning and taxonomy<\/h3>\n\n\n\n
                        \n
                      • Define a measurement plan that maps business goals to specific events and parameters.<\/li>\n
                      • Use consistent naming conventions (event names, parameter keys, and categories).<\/li>\n
                      • Separate \u201cmust-have\u201d events (core conversions) from \u201cnice-to-have\u201d events (exploratory engagement).<\/li>\n<\/ul>\n\n\n\n

                        Implementation and reliability<\/h3>\n\n\n\n
                          \n
                        • Prefer deterministic triggers (confirmed success states) over fragile click-based assumptions.<\/li>\n
                        • Ensure each conversion has a unique identifier where possible (e.g., transaction ID) to reduce duplicates.<\/li>\n
                        • Validate payloads: required fields present, correct data types, and expected value ranges.<\/li>\n<\/ul>\n\n\n\n

                          Governance and scaling<\/h3>\n\n\n\n
                            \n
                          • Use a change management process: request \u2192 review \u2192 QA \u2192 deploy \u2192 monitor.<\/li>\n
                          • Maintain a Tag inventory: owner, purpose, destinations, consent requirements, and last verified date.<\/li>\n
                          • Regularly audit and remove obsolete Tracking<\/strong> to reduce risk and improve performance.<\/li>\n<\/ul>\n\n\n\n

                            Monitoring<\/h3>\n\n\n\n
                              \n
                            • Set up alerts for conversion drops, sudden spikes, or missing parameters.<\/li>\n
                            • Monitor site\/app releases that could break triggers (UI changes, route changes, checkout redesigns).<\/li>\n
                            • Compare analytics totals against backend systems for reconciliation in Conversion & Measurement<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                              Tools Used for Tag<\/h2>\n\n\n\n

                              Tagging is operationalized through a combination of platforms and workflows. Vendor specifics vary, but these categories are common in Conversion & Measurement<\/strong> and Tracking<\/strong> ecosystems:<\/p>\n\n\n\n

                                \n
                              • Tag management systems (TMS)<\/strong>: Centralize Tag deployment, triggers, variables, and version control to reduce code releases.<\/li>\n
                              • Analytics tools<\/strong>: Receive event and pageview data, provide reporting, funnels, cohorts, and attribution views.<\/li>\n
                              • Ad platforms and conversion APIs<\/strong>: Use conversion Tags to optimize delivery and measure campaign outcomes.<\/li>\n
                              • CRM and marketing automation<\/strong>: Consume conversion and lead Tags to route, score, and nurture prospects.<\/li>\n
                              • Data warehouses and ETL pipelines<\/strong>: Store raw event streams for governance, modeling, and advanced analysis.<\/li>\n
                              • Monitoring and QA tools<\/strong>: Help validate firing behavior, payload contents, and release impacts.<\/li>\n
                              • Reporting dashboards<\/strong>: Combine multiple sources into decision-ready views for Conversion & Measurement<\/strong> stakeholders.<\/li>\n<\/ul>\n\n\n\n

                                Metrics Related to Tag<\/h2>\n\n\n\n

                                Because a Tag is a measurement mechanism, its success is evaluated through both marketing KPIs and instrumentation health metrics.<\/p>\n\n\n\n

                                Instrumentation quality metrics<\/h3>\n\n\n\n
                                  \n
                                • Event match rate<\/strong>: Percentage of expected events that actually arrive in destination systems.<\/li>\n
                                • Duplicate rate<\/strong>: Frequency of double-counted conversions or repeated events per session.<\/li>\n
                                • Parameter completeness<\/strong>: Share of events with required fields populated (value, currency, IDs).<\/li>\n
                                • Latency<\/strong>: Time from user action to data availability for reporting or optimization.<\/li>\n
                                • Consent-based coverage<\/strong>: How Tracking<\/strong> volume shifts by consent state and geography.<\/li>\n<\/ul>\n\n\n\n

                                  Performance and ROI metrics enabled by Tags<\/h3>\n\n\n\n
                                    \n
                                  • Conversion rate (CVR)<\/strong> and cost per acquisition (CPA)<\/strong> based on reliable conversion Tags.<\/li>\n
                                  • Return on ad spend (ROAS)<\/strong> or marketing ROI<\/strong> with accurate revenue\/event values.<\/li>\n
                                  • Funnel drop-off rates<\/strong> across checkout or lead flows.<\/li>\n
                                  • Customer lifetime value (LTV)<\/strong> modeling using consistent conversion and retention events.<\/li>\n
                                  • Incrementality indicators<\/strong> (where available) to validate whether Tracking<\/strong> signals reflect true lift.<\/li>\n<\/ul>\n\n\n\n

                                    Future Trends of Tag<\/h2>\n\n\n\n

                                    Tagging is evolving alongside privacy, automation, and new measurement expectations.<\/p>\n\n\n\n

                                      \n
                                    • More server-side and first-party approaches<\/strong>: Organizations are shifting toward controlled collection to improve reliability and reduce exposure to client-side blockers, while keeping Conversion & Measurement<\/strong> compliant.<\/li>\n
                                    • Consent-aware measurement by design<\/strong>: Tag behavior increasingly adapts dynamically based on user preferences, with clearer data minimization.<\/li>\n
                                    • AI-assisted instrumentation and anomaly detection<\/strong>: AI is being used to suggest event taxonomies, detect broken Tags, and flag unusual conversion patterns in Tracking<\/strong> streams.<\/li>\n
                                    • Modeled and aggregated measurement<\/strong>: As granular identifiers become less available, platforms rely more on aggregation and modeling. Tags still matter because models depend on high-quality inputs.<\/li>\n
                                    • Stronger governance expectations<\/strong>: Enterprises treat Tag changes like software releases, with approvals, audits, and documentation as standard practice in Conversion & Measurement<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                                      Tag vs Related Terms<\/h2>\n\n\n\n

                                      Tag vs Pixel<\/h3>\n\n\n\n

                                      A pixel<\/strong> is often a specific type of Tag historically implemented as a tiny image request or script, commonly used for advertising Tracking<\/strong>. \u201cTag\u201d is broader: it includes pixels, event scripts, SDK calls, and server-side requests.<\/p>\n\n\n\n

                                      Tag vs Event<\/h3>\n\n\n\n

                                      An event<\/strong> is the recorded user interaction (e.g., \u201cpurchase\u201d or \u201csign_up\u201d). A Tag<\/strong> is the mechanism that sends that event data to a destination. In other words: the event is what happened<\/em>; the Tag is how it gets measured<\/em> in Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                                      Tag vs UTM (campaign parameter)<\/h3>\n\n\n\n

                                      Campaign parameters describe acquisition context (source, medium, campaign). They are not a Tag by themselves, but they are often captured and forwarded by Tags to support Tracking<\/strong> and attribution.<\/p>\n\n\n\n

                                      Who Should Learn Tag<\/h2>\n\n\n\n
                                        \n
                                      • Marketers<\/strong> need Tag literacy to define conversions correctly, interpret performance, and avoid optimizing to misleading metrics.<\/li>\n
                                      • Analysts<\/strong> rely on Tags as the foundation of trustworthy Conversion & Measurement<\/strong> and clean datasets.<\/li>\n
                                      • Agencies<\/strong> must implement and audit Tags across multiple clients, ensuring consistent Tracking<\/strong> that supports reporting and optimization.<\/li>\n
                                      • Business owners and founders<\/strong> benefit from understanding what\u2019s realistically measurable, what\u2019s modeled, and where data can mislead.<\/li>\n
                                      • Developers<\/strong> need to implement events and data layers safely, maintain performance, and ensure Tags respect consent and security constraints.<\/li>\n<\/ul>\n\n\n\n

                                        Summary of Tag<\/h2>\n\n\n\n

                                        A Tag<\/strong> is the practical mechanism that sends user interaction data from your website or app to the tools that power Conversion & Measurement<\/strong>. It is central to Tracking<\/strong> conversions, engagement, and campaign impact. When designed with clear definitions, strong governance, and consistent QA, Tags enable accurate attribution, faster optimization, and better business decisions. When neglected, they silently degrade reporting, inflate or undercount conversions, and undermine marketing confidence.<\/p>\n\n\n\n

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

                                        1) What is a Tag in digital marketing measurement?<\/h3>\n\n\n\n

                                        A Tag<\/strong> is code or configuration that captures user actions and sends data to analytics or marketing platforms for Tracking<\/strong> and reporting within Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                                        2) How many Tags should a website have?<\/h3>\n\n\n\n

                                        There\u2019s no ideal number. You should have as many Tags as needed to measure key journeys\u2014and no more. Extra or redundant Tags can slow performance and increase data risk, so audits and consolidation are part of good Conversion & Measurement<\/strong> hygiene.<\/p>\n\n\n\n

                                        3) What\u2019s the difference between a Tag and an analytics event?<\/h3>\n\n\n\n

                                        An analytics event is the recorded action (like \u201cadd_to_cart\u201d). A Tag<\/strong> is the implementation that transmits that action and its parameters to the analytics system for Tracking<\/strong>.<\/p>\n\n\n\n

                                        4) Why is my conversion Tracking inconsistent even though the Tag is installed?<\/h3>\n\n\n\n

                                        Common causes include wrong triggers (fires before confirmation), duplicate firing, missing parameters, consent restrictions, ad blockers, or checkout\/app flow changes. The fix is usually a combination of QA, trigger hardening, and reconciliation with backend data in Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                                        5) Do Tags affect website speed?<\/h3>\n\n\n\n

                                        They can. Too many client-side Tags, heavy scripts, or poorly timed firing can slow pages. Good Tag governance focuses on necessity, performance testing, and removing unused Tracking<\/strong>.<\/p>\n\n\n\n

                                        6) Should I use client-side or server-side Tagging?<\/h3>\n\n\n\n

                                        Client-side is easier to deploy and inspect, but can be less reliable. Server-side improves control and can strengthen governance, but requires more engineering and operational setup. Many teams use a hybrid approach depending on Conversion & Measurement<\/strong> needs.<\/p>\n\n\n\n

                                        7) How do I know if a Tag is working correctly?<\/h3>\n\n\n\n

                                        Verify that it fires only when intended, sends complete parameters, respects consent settings, and matches expected counts when compared to backend systems. Ongoing monitoring and periodic audits are essential for trustworthy Tracking<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                        In digital marketing, a **Tag** is one of the most important building blocks of **Conversion & Measurement**. It\u2019s the mechanism that lets you observe user behavior, attribute outcomes to marketing efforts, and power **Tracking** across analytics, advertising, and experimentation systems. Without a solid Tag strategy, reporting becomes guesswork: conversions go missing, campaigns get misattributed, and optimization decisions are made on incomplete evidence.<\/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-7342","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\/7342","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=7342"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7342\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7342"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7342"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}