用 GEO Tag 看清「AI 引擎引用 → 访客到站 → 转化」的完整链路,把 AI 可见性变成可度量的生意。 With GEO Tag, see the full "AI-engine citation → visit → conversion" funnel and turn AI visibility into measurable business.
进入控制台Go to Console
GEO Tag(vtag.js)是一段贴进网站 <head> 的第一方分析标签——类比 gtag.js,GA4 式事件模型,自动采集访客行为;并把「AI 引擎引用你的内容 → 访客到站 → 注册/下单」串成 GA4 看不到的完整漏斗。
GEO Tag (vtag.js) is a first-party analytics snippet for your site's <head> — gtag.js-style, GA4-like event model, automatic behavior tracking; it links "AI engines citing your content → visitor arrives → sign-up / purchase" into one funnel GA4 can't see.
想先看数据模型? 直接读事件 Schema。 Want the data model first? Read the event schema.
已有账号? 登录控制台看实时报表。 Already invited? Sign in to Console for realtime reports.
注册站点拿 Tag ID,把一段 snippet 贴进 <head>——贴了就有,SPA 自动支持,无需再写代码。
Register a site, get a Tag ID, paste one snippet into <head> — done. SPA routing handled automatically.
GA4 式三作用域与事件模型:用过 GA4 零学习成本,自定义事件一行代码上报。 GA4-style scopes and events: zero learning curve if you know GA4; custom events are one line of code.
查看 SchemaSee the schema落地页 URL 反查 AI 引擎引用记录,补全「哪个引擎、哪篇被引内容带来了这个访客」——GA4 的盲区。 Landing URLs are cross-referenced with AI-engine citation records — "which engine, citing what, brought this visitor". GA4's blind spot.
了解差异Learn whyGA4 的漏斗从「访客到站」才开始。豆包、DeepSeek、ChatGPT 们引用了你的内容、带来了多少访客——这一段 GA4 是盲区。 GA4's funnel starts only when the visitor lands. Which AI engines (Doubao, DeepSeek, ChatGPT…) cited your content and how much traffic they drove — that leg is invisible to GA4.
| GA4 | GEO Tag | |
|---|---|---|
| 看得到网站访客行为 | ✅ | ✅ |
| 看得到「AI 引擎引用」这一段 | ❌ 完全盲区 | ✅ 与信源监测打通 |
| 数据归属 | 客户 + GEO Tag | |
| 国内访问稳定性 | 偏弱 | 自托管可控 |
| Sees on-site visitor behavior | ✅ | ✅ |
| Sees the "AI-engine citation" leg | ❌ blind spot | ✅ joined with citation monitoring |
| Data ownership | You + GEO Tag | |
| Reliability in mainland China | Weak | Self-hosted, controllable |
上表「看得到 AI 引擎引用这一段」靠的就是它。引用记录不会自己送上门——我们替你定期拿你设定的问题去问各 AI 引擎,记录回答里提没提到你、引没引用你的页面,并把回答原文与全部引用链接留证。这些记录再和站点侧的落地页对上,才有路径卡里那条「哪个引擎、哪篇被引内容带来了这个访客」。 This is what fills the "AI-engine citation" row above. Citation records don't arrive on their own — we periodically ask each AI engine the questions you configured, record whether the answer mentions you or cites your pages, and keep the full answer text and citation list as evidence. Matched against site-side landing pages, those records are what make "which engine, citing what, brought this visitor" possible at all.
每站最多 10 条,在控制台自己维护。我们不代拟——问题的好坏直接决定这组数据的含金量。 Up to 10 per site, maintained in the console. We don't write them for you — question quality decides how meaningful the numbers are.
首期覆盖 DeepSeek、通义千问、文心一言、豆包、腾讯元宝 5 个国内引擎;节奏你自己设,默认每周一轮。 Five mainland engines to start — DeepSeek, Qwen, Ernie, Doubao, Yuanbao. You set the cadence; weekly is the default.
回答原文与全部引用链接入库可查。引擎侧与站点侧数据并排呈现,各讲各的事实,不做换算。 Answer text and every citation link are stored and auditable. Engine-side and site-side figures sit side by side as independent facts — we never convert one into the other.
采样是唯一按次收费的功能:0.15 元/次(一次 = 一个引擎回答一个问题),成功返回答案才扣,失败、超时、空回答不计费。贴码接入与全部报表不按量收费,余额为 0 也照常采集、照常出报表。 Sampling is the only metered feature: ¥0.15 per call (one call = one engine answering one question), charged only when an answer comes back — failures, timeouts and empty answers are free. The tag and every report are never metered and keep working at a zero balance.
查看计费说明Read the billing rules这里是概述。完整步骤、验证方法与排查见接入指南。An overview. For the full steps, verification and troubleshooting see the install guide.
和 GA4 一样的接入体验:注册站点拿到 Tag ID,把 snippet 贴进 <head>,实时报表秒级见数。
Same experience as GA4: register your site, get a Tag ID, paste the snippet into <head> — data shows up in the realtime report within seconds.
VG-XXXXXXXX(类比 GA4 的 G-XXXX),并登记域名白名单防他人盗用你的 ID。
Create a site under Console → Sites to get a unique VG-XXXXXXXX (like GA4's G-XXXX), with a domain allowlist so nobody else can use your ID.
<head>Paste the snippet into your site's <head>
控制台「站点管理」会生成填好 Tag ID 的贴码,复制即用;接入指南里有逐行说明、其它引用方式与排查步骤。 The console's Sites page generates the snippet with your Tag ID filled in — copy and paste. The install guide explains it line by line, with alternatives and troubleshooting.
贴完自动采集,无需再写代码: Auto-collected out of the box, no further code:// 在关键动作处调用,如提交表单、点 CTAcall at key actions — form submit, CTA click…
geotag('event', 'sign_up', { plan: 'pro', source: 'hero_cta' });
geotag('event', 'conversion', { value: 199, currency: 'CNY' });异步加载 + sendBeacon 批量上报;端点永远秒回 204,失败也不报错给页面。Async load + batched sendBeacon; the endpoint always returns 204 instantly and never surfaces errors to your page.
上报请求校验 Origin ∈ 你登记的域名白名单,别人贴你的 ID 无效。Reports are validated against your domain allowlist — your ID is useless on anyone else's site.
IP → 地域、User-Agent → 设备/系统/浏览器,在服务端完成,客户端零采集负担。IP → geo and User-Agent → device/OS/browser resolved server-side; zero client burden.
已知爬虫与 AI 抓取 UA 直接丢弃,不污染访客数。Known crawlers and AI-scraper UAs are dropped so they never pollute visitor counts.
三作用域 + 冻结命名规范,用过 GA4 就零学习成本。 Three scopes + frozen naming rules — zero learning curve if you know GA4.
| 作用域Scope | 标识Key | 类比 GA4GA4 analog |
|---|---|---|
| 租户站点Tenant site | tag_id (VG-XXXX) | property |
| 访客Visitor | visitor_id(第一方,localStorage) (first-party, localStorage) | user_pseudo_id |
| 会话Session | session_id(30 分钟不活跃切新) (new after 30 min idle) | ga_session_id |
这些字段每条事件都有,且不在 params 里——下面的事件表只列各自的 params。
Present on every event and outside params — the per-event table below lists only each event's own params.
| 字段Field | 谁产生Set by |
|---|---|
event_name, event_ts, visitor_id, session_id, is_new_visitor, page_path |
标签the tag |
landing_engine, session_engine, nav_site(归因信号) (attribution signals) |
标签the tag |
device, os, browser, country, city |
采集端——由 UA 与 IP 反查得到,客户端不发the collector — derived from UA and IP; not sent by the client |
paramsCore events & their params| 事件Event | 谁产生Emitted by | 触发Trigger | params |
|---|---|---|---|
session_start | 标签自动tag, automatic | 新会话首个动作first action of a session | referrer, utm_*, spm |
first_visit | 标签自动tag, automatic | 该访客首访visitor's first visit | 同上same as above |
page_view | 标签自动tag, automatic | 每次页面/SPA 路由every page / SPA route | page_title, page_referrer, page_query, page_hash |
user_engagement | 标签自动tag, automatic | 页面可见且有交互时累计(30 秒无操作停表)accrues while visible and active (stops after 30s idle) | engagement_time |
scroll | 标签自动tag, automatic | 滚动到 90%90% depth | percent |
click | 标签自动tag, automatic | 出站/CTA 点击outbound / CTA click | link_url, link_text, is_outbound |
form_submit | 需你埋点you instrument it | 你在表单提交后自行调用you call it after a form submit | form_id |
conversion 🎯 | 需你埋点you instrument it | 你在转化完成后自行调用you call it when a conversion completes | conversion_name, value, currency |
| 自定义Custom | 需你埋点you instrument it | geotag('event', name, params) | 任意(受命名规范约束)anything within naming rules |
vg_ / _(内部用),自定义事件禁用
Prefixes vg_ / _ are reserved (internal); not allowed in custom eventsdevice(desktop/mobile/tablet)、is_outbound(bool)
Frozen enums: device (desktop/mobile/tablet), is_outbound (bool)page_view 上报样例A page_view upload example
标签按批次上报。注意 page_path 在顶层不在 params 里;device / country / city 不在上报体里——由采集端收到后补上。
The tag uploads in batches. Note that page_path is top-level, not inside params; device / country / city are not in the upload — the collector adds them on receipt.
{
"tag_id": "VG-8F2A9C10",
"events": [{
"event_name": "page_view",
"event_ts": "2026-07-28T11:03:22+08:00",
"visitor_id": "v_7d3f9a2b1c",
"session_id": "s_20260728_7d3f_02",
"is_new_visitor": false,
"page_path": "/cases/cleaning-robot",
"session_engine": "doubao",
"params": {
"page_title": "清洁机器人案例""Cleaning robot case study",
"page_referrer": "https://www.doubao.com/"
}
}]
}以下是产品在隐私上的硬性设计,为要点摘要;收集字段、保留期限、各方责任与你的权利,以隐私政策为准。 A summary of the product's structural privacy properties. The fields collected, retention periods, responsibilities and your rights are governed by the privacy policy.
geotag('consent', 'denied') 后只发匿名计数,不落访客 ID
Consent API — after geotag('consent', 'denied') only anonymous counts are sent, no visitor ID stored当前为邀请制:在申请页填一张表提交申请,我们人工审核后为你开通账号与站点,通过即把激活链接发到你留的邮箱,拿到 Tag ID 即可接入。没留邮箱就开不了户 —— 账号以邮箱为登录名,激活链接也只能发邮件。 Currently invite-only: submit the request form, we review it by hand, and once approved you get an activation link at the email address you gave us — then install with your Tag ID. Without an email address we cannot open the account: it is your login name, and the activation link can only be delivered by mail.