{"id":4484,"date":"2026-05-04T17:59:15","date_gmt":"2026-05-04T17:59:15","guid":{"rendered":"https:\/\/www.coffee.ai\/articles\/apollo-website-visitor-identification\/"},"modified":"2026-08-16T05:02:19","modified_gmt":"2026-08-16T05:02:19","slug":"apollo-website-visitor-identification","status":"publish","type":"post","link":"https:\/\/www.coffee.ai\/articles\/apollo-website-visitor-identification","title":{"rendered":"Apollo Website Visitor ID: How It Works vs Coffee"},"content":{"rendered":"<p><em>Written by: Doug Camplejohn, CEO &amp; Co-Founder, Coffee | Last updated: August 15, 2026<\/em><\/p>\n<h2 id=\"key-takeaways\">Key takeaways for Apollo and Coffee users<\/h2>\n<ul>\n<li>Website visitor identification turns anonymous sessions into known companies or individuals. Most 2026 platforms still stop at company-level data, so sales teams spend time manually finding contacts.<\/li>\n<li>Apollo\u2019s visitor pixel returns company names with a 7-day delay and no person-level resolution. Reps must run separate lookups, which removes the first-hour outreach window that drives 7\u00d7 higher response rates.<\/li>\n<li>Real-world company-level match rates usually land between 30\u201365% of B2B traffic. Deterministic person-level identification reaches roughly 30\u201340% of U.S. visitors. International traffic almost always stays at company-level signals because of GDPR constraints.<\/li>\n<li>Teams that need named prospects, real-time alerts, persona-matched lead suggestions, and automatic CRM or sequence enrollment must stitch together several tools when they rely on Apollo alone.<\/li>\n<li>Coffee combines the entire workflow, including pixel, identity graph, Slack alerts, CRM sync, and campaign enrollment, inside one agent so you turn anonymous traffic into pipeline-ready conversations faster. <a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\">Start turning anonymous traffic into pipeline-ready conversations<\/a> today.<\/li>\n<\/ul>\n<h2>How website visitor identification actually works<\/h2>\n<p>Website visitor identification resolves an anonymous browser session to a named company or individual. At the company level, reverse-IP lookup matches the visitor\u2019s IP address against a database of corporate IP ranges and returns an organization name, domain, and firmographic data. At the person level, an identity graph layer sits on top of IP matching and returns a name, job title, work email, and LinkedIn profile.<\/p>\n<p>For RevOps teams, this distinction shapes pipeline outcomes. Company-level data produces a signal such as \u201cAcme Corp visited your pricing page.\u201d Person-level data produces a lead such as \u201cJane Smith, VP of Sales at Acme Corp, visited your pricing page twice this week.\u201d Pipeline velocity depends on the second scenario. <a href=\"https:\/\/leadpipe.com\/blog\/visitor-identification-guide-for-revops\" target=\"_blank\" rel=\"noindex nofollow\">Research on visitor identification workflow automation<\/a> shows that teams reaching out within the first hour of a visit are 7\u00d7 more likely to have a meaningful conversation than those waiting 24 hours. That window opens only with real-time, person-level identification.<\/p>\n<h2>How to see website visitors in Apollo<\/h2>\n<p>Apollo\u2019s visitor identification feature activates after you install its tracking pixel on your site. The general setup process follows these steps.<\/p>\n<ol>\n<li>Log in to Apollo and navigate to Settings &gt; Tracking &amp; Analytics to generate your unique pixel script.<\/li>\n<li>On <strong>Webflow<\/strong>, go to Project Settings &gt; Custom Code, paste the script into the Head Code field, and publish the site. A paid Webflow Site plan (Basic or above) is required for custom code injection, per <a href=\"https:\/\/leadfeeder.com\/blog\/website-visitor-identification\/webflow-visitor-identification\" target=\"_blank\" rel=\"noindex nofollow\">Webflow visitor identification documentation<\/a>.<\/li>\n<li>On <strong>WordPress<\/strong>, paste the script through a header snippet plugin such as WPCode. This approach avoids direct theme file edits and follows <a href=\"https:\/\/getbeam.fyi\/blog\/wordpress-visitor-tracking\" target=\"_blank\" rel=\"noindex nofollow\">standard WordPress tracking installation practice<\/a>.<\/li>\n<li>On <strong>custom sites<\/strong>, paste the script inside the <code>&lt;head&gt;<\/code> tag of your base template so it fires site-wide.<\/li>\n<li>Configure a consent banner. Under GDPR and UK PECR, <a href=\"https:\/\/cookieyes.com\/blog\/uk-cookie-guidance-ico-pecr\" target=\"_blank\" rel=\"noindex nofollow\">the UK ICO\u2019s 2026 guidance<\/a> requires prior consent for any pixel-based individual tracking. EU rules mirror this requirement. For U.S. traffic, <a href=\"https:\/\/leadpipe.com\/blog\/is-website-visitor-identification-legal\" target=\"_blank\" rel=\"noindex nofollow\">CCPA\/CPRA compliance<\/a> requires notice at collection and a working opt-out, including honoring Global Privacy Control signals.<\/li>\n<\/ol>\n<p>Users report a 7-day data latency before identified visitor records appear in Apollo\u2019s interface. This structural delay makes same-day outreach impossible within the platform alone.<\/p>\n<h2>How Apollo visitor identification behaves in practice<\/h2>\n<p>Apollo\u2019s pixel matches sessions primarily at the company level. When a match appears, Apollo surfaces the visiting organization and lets sales reps browse Apollo\u2019s contact database to find people who work there. The identification itself does not return a named individual who visited. It returns the company, and the rep manually selects contacts to pursue.<\/p>\n<p>Several documented constraints shape this experience.<\/p>\n<ul>\n<li><strong>Company-level only:<\/strong> The pixel does not resolve to a named visitor. Person selection remains a manual, post-identification step.<\/li>\n<li><strong>US contacts only:<\/strong> Apollo\u2019s person-level contact coverage is strongest in North America, particularly the U.S. market for which it was built. International visitors resolve to company data at best.<\/li>\n<li><strong>VPN and ad-blocker drop-off:<\/strong> <a href=\"https:\/\/salestarget.ai\/blogs\/reverse-ip-lookup-anonymous-website-visitors-b2b\" target=\"_blank\" rel=\"noindex nofollow\">VPN traffic is frequently misattributed to the VPN provider\u2019s IP<\/a> rather than the actual employer, which reduces effective match rates. <a href=\"https:\/\/digitalapplied.com\/blog\/server-side-tracking-2026-privacy-first-analytics-cookies\" target=\"_blank\" rel=\"noindex nofollow\">Browser-based ad blockers combined with Safari ITP block client-side tags on more than 40% of sessions<\/a> in key markets.<\/li>\n<li><strong>No suggested leads:<\/strong> Apollo does not use your buyer persona to recommend which specific individuals inside a visiting company to contact. That prioritization step stays manual.<\/li>\n<li><strong>7-day latency:<\/strong> Data does not appear in real time, eliminating the first-hour window mentioned earlier.<\/li>\n<\/ul>\n<h2>How to evaluate visitor identification accuracy<\/h2>\n<p>Given these structural limitations in Apollo\u2019s approach, teams need a consistent framework to evaluate any visitor identification platform. The variables that determine real-world performance include match rates, coverage, latency, and workflow depth.<\/p>\n<ul>\n<li><strong>Match rate at the company level:<\/strong> Realistic company-level match rates run 30\u201365% of qualifying B2B traffic. Vendor claims of 80% often mix B2B and consumer sessions or include low-confidence matches.<\/li>\n<li><strong>Match rate at the individual level:<\/strong> <a href=\"https:\/\/leadpipe.com\/blog\/state-of-website-visitor-identification-2026\" target=\"_blank\" rel=\"noindex nofollow\">Deterministic person-level identification achieves roughly 30\u201340% of U.S. B2B visitors<\/a> in 2026. Probabilistic tools quote higher rates that include low-confidence guesses.<\/li>\n<li><strong>Individual vs. company granularity:<\/strong> Only person-level identification produces an actionable lead without a manual lookup step.<\/li>\n<li><strong>International coverage:<\/strong> <a href=\"https:\/\/pipeline.zoominfo.com\/sales\/rb2b-vs-warmly\" target=\"_blank\" rel=\"noindex nofollow\">Person-level identification is unavailable for EU, APAC, and Latin American traffic<\/a> on most platforms because of GDPR-equivalent regulations. Company-level remains the ceiling for international visitors.<\/li>\n<li><strong>Latency:<\/strong> Real-time alerts enable same-session or same-day outreach. Seven-day delays do not support that motion.<\/li>\n<li><strong>Workflow automation:<\/strong> Some platforms route identified visitors directly into CRM records and outreach sequences. Others stop at a dashboard and leave the rest to manual work or custom integrations.<\/li>\n<\/ul>\n<p> <a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><strong>See how Coffee consolidates pixel, identity graph, and CRM sync in one platform<\/strong><\/a><\/p>\n<h2>Apollo vs Coffee: side-by-side accuracy comparison<\/h2>\n<p>The following table compares Apollo\u2019s visitor identification capabilities with Coffee and category benchmarks across six core dimensions. It highlights where company-level-only tools create manual work that Coffee automates inside one agent.<\/p>\n<table>\n<thead>\n<tr>\n<th>Capability<\/th>\n<th>Apollo Visitor ID<\/th>\n<th>RB2B \/ Warmly (category benchmark)<\/th>\n<th>Coffee<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Identification granularity<\/td>\n<td>Company-level only<\/td>\n<td><a href=\"https:\/\/support.rb2b.com\/en\/articles\/11155094-company-level-identification\" target=\"_blank\" rel=\"noindex nofollow\">RB2B resolves 40\u201345% of U.S.-based website traffic to a person-level ID<\/a>; Warmly: ~15% person-level<\/td>\n<td>Named individual with name, title, email, LinkedIn<\/td>\n<\/tr>\n<tr>\n<td>US person-level match rate<\/td>\n<td>Not applicable (company only)<\/td>\n<td><a href=\"https:\/\/support.rb2b.com\/en\/articles\/11155094-company-level-identification\" target=\"_blank\" rel=\"noindex nofollow\">RB2B resolves 40\u201345% of U.S.-based website traffic to a person-level ID (combined identification up to 70\u201380%)<\/a><\/td>\n<td>Person-level identification using identity graph layer<\/td>\n<\/tr>\n<tr>\n<td>International coverage<\/td>\n<td>Company-level; U.S. contacts only<\/td>\n<td><a href=\"https:\/\/pipeline.zoominfo.com\/sales\/rb2b-vs-warmly\" target=\"_blank\" rel=\"noindex nofollow\">Company-level only outside U.S. (GDPR ringfencing)<\/a><\/td>\n<td>U.S. person-level; company-level international<\/td>\n<\/tr>\n<tr>\n<td>Suggested leads (persona-matched)<\/td>\n<td>None, manual contact selection<\/td>\n<td>None, raw people lists or company only<\/td>\n<td>Yes, recommends 2\u20133 specific contacts matching your buyer persona<\/td>\n<\/tr>\n<tr>\n<td>Data latency<\/td>\n<td>~7 days (user-reported)<\/td>\n<td><a href=\"https:\/\/woodpecker.co\/blog\/identify-anonymous-website-visitors\" target=\"_blank\" rel=\"noindex nofollow\">Most tools: seconds to minutes<\/a><\/td>\n<td>Real-time Slack alerts<\/td>\n<\/tr>\n<tr>\n<td>End-to-end workflow automation<\/td>\n<td>No, separate enrichment and sequencing tools required<\/td>\n<td>Partial, CRM push and Slack alerts, sequencing is external<\/td>\n<td>Yes, pixel to alert to CRM add to campaign enrollment in one agent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Note: Apollo\u2019s visitor identification match rate is not published as a standalone figure because the product returns company-level signals only. The table reflects this structural difference rather than a missing data point.<\/p>\n<h2>How to check who is visiting your website with Coffee<\/h2>\n<p>Coffee generates a custom tracking pixel from within the platform, and installation takes under five minutes on any site type.<\/p>\n<ol>\n<li><strong>Webflow:<\/strong> Copy the Coffee pixel script. In Webflow, go to Project Settings &gt; Custom Code and paste the script into the Head Code field, then publish the site. A paid Webflow Site plan is required for custom code, as <a href=\"https:\/\/leadfeeder.com\/blog\/website-visitor-identification\/webflow-visitor-identification\" target=\"_blank\" rel=\"noindex nofollow\">documented for all head-tag scripts on Webflow<\/a>. You can also deploy through Google Tag Manager to avoid the plan requirement.<\/li>\n<li><strong>WordPress:<\/strong> Install a header snippet plugin such as WPCode. Paste the Coffee pixel into the header snippet field and save. This approach requires no theme file edits or database changes and follows <a href=\"https:\/\/getbeam.fyi\/blog\/wordpress-visitor-tracking\" target=\"_blank\" rel=\"noindex nofollow\">standard WordPress pixel installation practice<\/a>.<\/li>\n<li><strong>Custom sites:<\/strong> Paste the Coffee script inside the <code>&lt;head&gt;<\/code> tag of your base HTML template. Coffee verifies installation automatically and begins identifying visitors immediately.<\/li>\n<\/ol>\n<p>For EU and UK visitors, gate the Coffee pixel behind a consent management platform. <a href=\"https:\/\/forgeandsmith.com\/blog\/cookies-tracking-consent-legal-checklist-for-business-websites\" target=\"_blank\" rel=\"noindex nofollow\">Consent management platforms must detect and respond to Global Privacy Control signals<\/a> and prevent non-consented tracking scripts from firing. For U.S. visitors, provide notice at collection and a working opt-out mechanism that aligns with CCPA\/CPRA requirements.<\/p>\n<h2>How Coffee routes identified visitors into pipeline<\/h2>\n<p>Coffee\u2019s end-to-end workflow closes the gap between pixel fire and pipeline action without extra point solutions.<\/p>\n<ol>\n<li><strong>Pixel hit:<\/strong> A visitor lands on your site. Coffee\u2019s pixel fires and resolves the session against its identity graph. The platform returns name, title, email, LinkedIn profile, company, pages visited, time on site, and whether the visit is a first or return session.<\/li>\n<li><strong>Real-time Slack alert:<\/strong> A notification surfaces the identified visitor immediately. <a href=\"https:\/\/leadpipe.com\/blog\/identify-website-visitors-get-contact-info\" target=\"_blank\" rel=\"noindex nofollow\">High-performing teams configure channel-specific alerts<\/a> so pricing-page visitors route to #sales-alerts while blog readers route to #marketing-leads.<\/li>\n<li><strong>One-click CRM add:<\/strong> The prospect is added to Coffee with all enrichment pre-filled. No one needs to type data manually. The record includes behavioral data such as pages visited, time on site, and visit frequency.<\/li>\n<li><strong>Suggested Leads:<\/strong> Where competitors surface a raw list of everyone at the visiting company, Coffee uses your defined buyer persona to recommend the two or three specific individuals most worth contacting, with LinkedIn profiles ready for outreach.<\/li>\n<li><strong>Auto-enrollment in Campaigns:<\/strong> The identified prospect can be enrolled directly into a multi-step email sequence that runs from the rep\u2019s own connected mailbox. Stop-on-reply stays enabled by default so no automated email fires after a real conversation begins.<\/li>\n<\/ol>\n<p>This architecture mirrors the <a href=\"https:\/\/leadpipe.com\/blog\/visitor-identification-guide-for-revops\" target=\"_blank\" rel=\"noindex nofollow\">standard webhook-driven pipeline<\/a>, which runs pixel to webhook to router to CRM, engagement, and alerts. Coffee executes every stage inside a single agent instead of relying on Zapier, Clay, a separate sequencing tool, and manual deduplication logic.<\/p>\n<p> <a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><strong>Try Coffee\u2019s automated workflow, from pixel hit to sequence enrollment without manual steps<\/strong><\/a> <\/p>\n<h2>How Apollo fits international teams and compliance<\/h2>\n<p>Apollo holds SOC 2 certification and serves a large customer base. For international RevOps teams, the core trust questions focus on data coverage and legal compliance rather than security posture.<\/p>\n<p>On coverage, <a href=\"https:\/\/pipeline.zoominfo.com\/sales\/rb2b-vs-warmly\" target=\"_blank\" rel=\"noindex nofollow\">person-level visitor identification is unavailable for EU, APAC, and Latin American traffic<\/a> across virtually all platforms, including Apollo, because of GDPR-equivalent regulations. International visitors resolve to company-level data at best. These visitors also achieve lower company-level and person-level identification rates industry-wide.<\/p>\n<p>On compliance, <a href=\"https:\/\/leadpipe.com\/blog\/is-website-visitor-identification-legal\" target=\"_blank\" rel=\"noindex nofollow\">under GDPR and the ePrivacy Directive, person-level visitor identification generally requires affirmative consent<\/a>, while company-level identification can often rely on legitimate interest. The UK regime under UK GDPR and PECR mirrors this, and <a href=\"https:\/\/cookieyes.com\/blog\/uk-cookie-guidance-ico-pecr\" target=\"_blank\" rel=\"noindex nofollow\">the ICO\u2019s 2026 guidance<\/a> requires prior consent for any tracking that identifies individual users or links visitor IDs to conversions.<\/p>\n<p>Teams with significant EU or UK traffic should configure jurisdiction-aware geofencing. U.S. traffic receives person-level identification. EU and UK traffic defaults to company-level only, with pixel firing gated behind a compliant consent banner.<\/p>\n<h2>Frequently asked questions about Apollo and visitor IDs<\/h2>\n<h3>How did Apollo get my information?<\/h3>\n<p>Apollo\u2019s contact database draws from publicly available sources including LinkedIn profiles, company websites, job postings, and third-party data providers. The platform also uses user-contributed data from customers who grant Apollo access to their email contacts. When Apollo\u2019s visitor identification pixel fires on a website you visited, it matches your session\u2019s IP address to a company in its database. Apollo does not identify you as a named individual through the pixel alone. That match happens when a sales rep manually searches Apollo\u2019s contact database for people at the identified company.<\/p>\n<p>If your information appears in Apollo\u2019s database, it came from public professional data or from a mutual connection\u2019s email sync. Apollo provides a data opt-out process through its privacy portal for individuals who want their records removed.<\/p>\n<h3>Can websites identify visitors outside the U.S.?<\/h3>\n<p>Company-level identification of international visitors is technically feasible and widely used. Reverse-IP lookup can resolve a visiting IP to a company name and domain regardless of geography, as long as the IP range exists in the vendor\u2019s database. Person-level identification outside the U.S. follows a different rule set. GDPR in the EU and equivalent regulations in the UK, Canada, and much of the world restrict or prohibit resolving a website visit to a named individual without explicit prior consent.<\/p>\n<p>In practice, most visitor identification platforms, including Coffee, deliver person-level data for U.S. visitors and company-level data only for international visitors. Teams with global traffic should treat international visitor identification as a company-level signal and design their outreach workflow around account-based outreach rather than expecting a named contact.<\/p>\n<h3>What is a visitor ID and how accurate is it?<\/h3>\n<p>A visitor ID is the identifier a tracking platform assigns to a browser session or device to link it to a known entity, either a company or an individual. Accuracy varies by identification method and traffic type. Company-level reverse-IP identification produces matches at varying rates depending on traffic composition, and accuracy can be high when a match appears. The remaining sessions belong to remote workers on home ISPs, VPN users, mobile network visitors, and others whose IP addresses do not map to a corporate range.<\/p>\n<p>Person-level identification adds an identity graph layer that can resolve named individuals. This method works reliably only in the U.S. and only on traffic that passes through the identity graph\u2019s network. Deterministic person-level tools can achieve high accuracy on the sessions they match. Probabilistic tools that quote higher overall match rates often include low-confidence guesses that inflate apparent performance. The most reliable way to measure real accuracy is to run a 30-day parallel test with two or three tools and cross-reference identified visitors against your CRM.<\/p>\n<h3>How do I remove my name from Apollo?<\/h3>\n<p>Apollo provides a self-service opt-out through its privacy portal at apollo.io\/privacy-policy. Submitting a removal request through the portal starts a process that suppresses your contact record from Apollo\u2019s database and prevents it from being re-added through automated data refresh cycles. The process usually takes several business days.<\/p>\n<p>Removal from Apollo\u2019s database does not erase your information from other data providers or from CRM records that Apollo data has already populated for Apollo\u2019s customers. If you want broader data removal, you must submit separate requests to each data provider whose database contains your information, because no single universal opt-out mechanism exists across the B2B data industry.<\/p>\n<h2>Decision checklist for switching from Apollo to Coffee<\/h2>\n<p>The following conditions indicate that Apollo\u2019s visitor identification alone is insufficient for your pipeline goals and that an integrated agent like Coffee deserves a closer look. These criteria fall into three categories: data granularity gaps, timing constraints, and workflow fragmentation.<\/p>\n<ul>\n<li>Your team needs named individuals from website visits, not just company names, and cannot absorb the manual lookup step Apollo requires. This gap in data granularity pushes reps toward research instead of outreach.<\/li>\n<li>You are losing the first-hour outreach window because Apollo\u2019s 7-day data latency prevents same-day follow-up. This timing constraint removes your highest-converting engagement window.<\/li>\n<li>You are paying for separate tools, including a visitor identification platform, an enrichment database, and a sequencing tool, and want to consolidate into one agent. Consolidation reduces both cost and the integration overhead of maintaining multiple point solutions.<\/li>\n<li>Your buyer persona is specific enough that a raw list of everyone at a visiting company is not actionable. You need the platform to recommend which two or three people to contact so reps can prioritize quickly.<\/li>\n<li>Your CRM data quality is degraded by manual entry, and you need an agent that auto-creates and enriches contact records from identified visitors without human input. Automated enrichment keeps records consistent and current.<\/li>\n<li>Your team is 10\u201350 people and cannot justify the engineering overhead of building a custom webhook pipeline that connects a visitor ID tool to your CRM and sequencing platform. A native workflow removes that build-and-maintain burden.<\/li>\n<\/ul>\n<p>If most of these conditions apply, the operational cost of assembling point solutions around Apollo\u2019s visitor identification exceeds the cost of switching to a platform that handles the full workflow natively.<\/p>\n<p> <a href=\"https:\/\/www.coffee.ai\/pricing\" target=\"_blank\"><strong>See your named visitors, suggested leads, and outreach sequences in one Coffee workspace<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Apollo identifies company-level visitors with a 7-day delay. Coffee delivers real-time, person-level ID with auto-enrollment. See why teams switch.<\/p>\n","protected":false},"author":11,"featured_media":4483,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4484","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts\/4484","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/comments?post=4484"}],"version-history":[{"count":2,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts\/4484\/revisions"}],"predecessor-version":[{"id":8605,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/posts\/4484\/revisions\/8605"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/media\/4483"}],"wp:attachment":[{"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/media?parent=4484"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/categories?post=4484"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.coffee.ai\/articles\/wp-json\/wp\/v2\/tags?post=4484"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}