內容簡介
BaseCloud UTM Tracker 是一款專為 WordPress 設計的 UTM 追蹤與 webhook 管理解決方案，提供無限自訂 webhook、完整的合併標籤支援，並自動注入 UTM 參數，協助網站追蹤流量與轉換。
【主要功能】
• 無限自訂 webhook 支援
• 自動 UTM 參數注入
• Claude 連接器功能
• 轉換追蹤報告生成
• 安全設計，無個人資料存儲
外掛標籤
開發者團隊
📦 歷史版本下載
原文外掛簡介
BaseCloud UTM Tracker is the ultimate UTM tracking and webhook management solution for WordPress. Replace Gravity Forms webhook add-on with unlimited custom webhooks, full merge tag support, and automatic UTM injection for the “Big 4” form plugins.
NEW in 4.5: Claude connector
Connect Claude to your site and ask for reports in plain language. The plugin becomes a remote MCP server (off until you switch it on under Blog Post Conversion Tracker → Claude connector) with read-only tools for traffic, leads, WhatsApp and calls, Search Console insights, AI visibility and the organic comparison. Every answer carries its exact dates, timezone and accuracy notes, so Claude quotes your real numbers instead of estimating them.
Presentation reports – a branded slide deck with the BaseCloud logo, opened inside claude.ai or through a signed, expiring link you can present from any browser or save as PDF.
Works with claude.ai, Claude Desktop and Claude Code – claude.ai signs in with OAuth (you approve it on your own site); Claude Code and other clients can use an API key.
Safe by design – read-only, administrators only, no personal data, tokens stored as hashes, rate limits, and a self-test that checks your server before you connect.
NEW in 4.4: visits, leads beyond Gravity Forms and keyword insights
Everything new is part of the Blog Post Conversion Tracker. Visit counting and the BaseCloud Forms bridge are on by default while the tracker is on, also on sites that already use it, so they start after the update without any action (both are first-party, follow the tracker’s consent setting and can be switched off in the Tracker section). Every other new feature is off until you switch it on. The UTM tracker is unchanged apart from two fixes (see the changelog).
Visits and channels – first-party visit counts per landing page and channel (search, social, AI assistants, email, paid, campaign, referral, direct), conversion rates per channel, and an organic comparison of plugin visits, Search Console clicks and, optionally, Google Analytics 4 sessions, with the likely reason for each gap.
BaseCloud Forms bridge – BaseCloud CRM forms embedded on your pages receive the visitor’s source, landing page and journey as extra fields, and confirmed submissions are recorded as leads.
WhatsApp and call tracking – a reference code in the pre-filled WhatsApp message, WhatsApp and phone clicks recorded with their journey, an inbound API that lets your CRM, WATI or phone provider (for example Twilio) match chats and calls back to the visit, and tracking numbers per source or from a per-visitor pool.
Keyword insights – Search Console rhythm by weekday and month, brand and non-brand searches separately, the searches each page really appears for next to its focus keyphrase, striking-distance queries, pages competing for the same query, and suspected automated queries set aside.
AI visibility – AI crawler hits split into training, search index and user-triggered fetches, human visits from AI assistants, and the missing pages AI crawlers ask for.
How it works – a guide inside the plugin that explains where every number comes from and how accurate it is, with a live setup checklist.
Reports now include traffic, leads and Search Console insights.
NEW in 4.3: search keywords, AI visibility and reports
Everything new is part of the Blog Post Conversion Tracker and is off by default. The UTM tracker is unchanged.
Search keywords – connect Google Search Console with a service account to see the queries that sent clicks to the landing page of each organic Google conversion, flagged against your target keywords (read from Yoast SEO, Rank Math, All in One SEO and SEOPress, plus your own list). These are the likely keywords, not the visitor’s exact search: Google does not share that, and Search Console data is 2-3 days behind.
AI visibility – conversions referred by AI assistants (ChatGPT, Perplexity, Gemini, Copilot, Claude and others), an AI crawler log per page with optional IP verification, a robots.txt check for AI crawlers, an llms.txt generator, and AI answer citations from the Ahrefs API.
Reports – daily, weekly, monthly and half-yearly JSON reports of your best converting posts, channels, forms, keywords and AI visibility, sent to report webhooks with an optional PDF attachment, plus previews and PDF downloads for any date range.
Secure by design – API keys, service account keys and report webhook URLs are encrypted and write-only, requests go only to fixed service hosts or validated https webhooks, and reports contain no personal data.
NEW in 4.2: Blog Post Conversion Tracker
See which blog post a visitor was reading right before they filled in your Gravity Form. Turn it on under UTM Tracker > Blog Post Conversion Tracker (it is off by default).
Journey tracking – the browser keeps first and last touch, the first and last post read and the most recent pages in localStorage, with a compact first-party cookie (bc_blog_attr, under 2 KB) as a backup. Gravity Forms submissions carry the full journey in a hidden field. Cache-safe, size-safe and consent-aware (Google Consent Mode regions respected).
Entry columns – “Blog: Converted From Post” (Yes, Yes (unverified) or No) and “Blog: Source Post” on Gravity Forms entries, plus minutes to convert, same visit, pages viewed after the post and an optional attribution window.
Clean webhooks – a readable JSON payload (form, entry, contact, fields, conversion, visitor, journey) with ISO 8601 times, sent after the visitor’s response so forms stay fast. UTM parameters are left to the UTM tracker.
Secure by design – webhook URLs and secrets are encrypted (AES-256-GCM, with an optional BASECLOUD_BPCT_KEY constant), HTTPS only with private-network blocking, never shown again after saving, and requests can be HMAC-signed.
Top Converting Posts and recent conversions in the dashboard.
Fully separate from the UTM tracker: its settings, cookies and webhooks are untouched. Deleting the plugin removes only the Blog Post Conversion Tracker data.
🎯 THE COLLECTOR: Advanced Cookie Tracking
Automatically captures and stores UTM parameters from your marketing campaigns in secure, persistent cookies.
📦 THE COURIER: Automated Webhook Injection
Game Changer! Automatically injects UTM data into ALL form webhook submissions – works with Gravity Forms, Elementor Pro, WPForms, and Contact Form 7!
The “Big 4” Form Support
Gravity Forms – Full integration with async webhook support
Elementor Pro Forms – Webhook injection for page builder forms
WPForms – Complete webhook automation
Contact Form 7 – Classic form plugin support
Key Features
🚀 Zero Manual Configuration – Works automatically after activation
🎯 COLLECTOR System – Advanced cookie-based tracking for 8 parameters
📦 COURIER System – Automatic webhook injection for all major form plugins
⚡ Async Webhook Support – Works with background processing (critical for Gravity Forms)
🔄 Real-Time Diagnostics – Animated status dashboard shows system health
📊 Entry Meta Storage – UTM data saved with each Gravity Forms submission
🎨 Beautiful Dashboard – Modern, animated interface with live status indicators
🔒 Privacy Compliant – Secure cookies with proper SameSite and HTTPS support
📱 iOS 14+ Support – Tracks gbraid and wbraid for enhanced Apple privacy tracking
Tracked Parameters (8 Total)
referrer – Previous page URL
utm_source – Campaign source (Google, Facebook, etc.)
utm_medium – Marketing medium (CPC, email, social)
utm_campaign – Campaign name
utm_term – Campaign keywords
gclid – Google Click ID
gbraid – Google Brand Engagement (iOS 14+)
wbraid – Web to App Brand Engagement (iOS 14+)
How THE COURIER Works
Visitor arrives with UTM parameters in URL
COLLECTOR captures and stores data in cookies
Visitor submits a Gravity Form
COURIER automatically injects all UTM data into webhook payload
Your CRM receives complete attribution data – automatically!
Perfect For
Digital Marketing Agencies – Complete campaign attribution without manual setup
E-commerce Sites – Track ROI from every marketing channel
Lead Generation – Automatic UTM data in your CRM
SaaS Companies – Understand customer acquisition sources
PPC Campaigns – Full Google Ads and Facebook Ads tracking
What’s NEW in v2.0.0?
🎯 COLLECTOR System – Advanced cookie tracking engine
📦 COURIER System – Automatic webhook injection (no manual fields!)
🎨 Animated Dashboard – Real-time system diagnostics with animations
📊 Entry Meta Storage – UTM data saved with each form submission
🔧 Excluded Webhooks – Option to exclude specific webhook URLs
✨ iOS 14+ Support – gbraid and wbraid parameter tracking
🚀 Zero Configuration – Works automatically after activation
Gravity Forms Integration (THE COURIER)
🚀 No Manual Field Creation Required!
The COURIER system automatically injects all UTM data into Gravity Forms webhook submissions. Simply:
Enable “Gravity Forms Integration” in plugin settings
Set up your Gravity Forms webhooks as normal
The COURIER automatically adds UTM data to every webhook request
Optional: You can still create visible fields with parameter names (referrer, utm_source, etc.) if you want users to see the data. The COLLECTOR will populate them automatically.
Excluded Webhooks: Configure specific webhook URLs to exclude from UTM injection (useful for internal notifications).
Technical Features
Lightweight – Minimal impact on site performance
Standards Compliant – Follows WordPress coding standards
Secure – Proper data sanitization and validation
Translatable – Ready for internationalization
Mobile Friendly – Works across all devices and browsers
Entry Meta Storage – UTM data stored with each Gravity Forms entry
Webhook Automation – Zero configuration webhook injection
Animated UI – Real-time system status with smooth animations
Use Cases
Marketing Attribution: Track which campaigns generate the most leads and sales – automatically!
CRM Integration: UTM data flows seamlessly to your CRM via Gravity Forms webhooks.
A/B Testing: Compare performance between different campaign variations.
ROI Analysis: Calculate return on investment for different marketing channels.
Customer Journey: Understand how visitors discover and interact with your site.
External services
The plugin’s server never sends data to BaseCloud. The services below are contacted only when you switch the related Blog Post Conversion Tracker feature on and save the credentials it needs. Conversion, lead and report webhooks send data only to the https URLs you enter yourself. The inbound API for chats and calls only receives requests; it contacts no one. The Claude connector answers only the Claude apps and API keys you approve.
Claude client metadata (claude.ai)
Used by the Claude connector to identify the Claude app that asks to connect.
Host: claude.ai by default (the allowed hosts are a setting of the Claude connector).
When: only while the Claude connector is switched on, when an app that identifies itself with a client metadata document URL opens the approval page on your site. The document is cached for 24 hours.
Data sent: an HTTPS GET for the public client metadata document. No site or visitor data is sent. The connector otherwise only answers requests from the Claude apps you approve; it sends your reports to them and to no one else.
Anthropic Consumer Terms: https://www.anthropic.com/legal/consumer-terms
Anthropic Privacy Policy: https://www.anthropic.com/legal/privacy
Google OAuth 2.0 and Google Search Console API
Used by Search keywords to read Search Console query data for your own site.
Hosts: oauth2.googleapis.com (access token) and www.googleapis.com (Search Console API).
When: only while Search keywords is enabled and a service account key is saved: the initial backfill of your Search Console history runs about every 5 minutes until it is complete, then a daily sync, plus “Test connection” and “Sync now”.
Data sent: a JWT signed with your service account key (the service account email and a read-only scope) and the Search Console property with date ranges. Data received: query, page, click and impression rows. No visitor data is sent.
Google APIs Terms of Service: https://developers.google.com/terms
Google Privacy Policy: https://policies.google.com/privacy
Google Analytics Data API (optional)
Used by the organic comparison to read Google Analytics 4 sessions per landing page.
Hosts: oauth2.googleapis.com (access token) and analyticsdata.googleapis.com (GA4 Data API).
When: only while GA4 is switched on in the Search keywords section and a service account key is saved: a daily report, plus “Test connection”.
Data sent: a JWT signed with your service account key (the service account email and the read-only analytics.readonly scope) and the GA4 property ID with a date range. Data received: sessions per landing page and channel group, and sessions from AI assistant sources. No visitor data is sent.
Google APIs Terms of Service: https://developers.google.com/terms
Google Privacy Policy: https://policies.google.com/privacy
BaseCloud CRM forms (BaseCloud Forms bridge)
The plugin’s server does not contact BaseCloud. When your pages embed BaseCloud CRM forms, each form sends its submissions from the visitor’s browser to your BaseCloud CRM at api.basecloudglobal.com. While the tracker and the bridge are on, the plugin adds the attribution fields listed under “What is sent to BaseCloud Forms?” to that request. Nothing is added on pages without a BaseCloud form, when the bridge is switched off, or before consent when consent mode is on. The allowed CRM hosts can be changed in the Tracker section.
BaseCloud Privacy Policy: https://www.basecloudglobal.com/privacy-policy/
OpenAI, Perplexity and Anthropic crawler IP ranges
Used by the AI crawler log to check that requests claiming to come from these companies’ crawlers come from the IP ranges they publish.
Hosts: openai.com, www.perplexity.ai and claude.com.
When: only while the AI crawler log and IP verification are both on: one GET request for each vendor’s public IP-range file about once a week, or when you click “Refresh crawler IP ranges” (which also needs both settings on).
Data sent: nothing beyond the request itself.
OpenAI Terms of Use: https://openai.com/policies/terms-of-use and Privacy Policy: https://openai.com/policies/privacy-policy
Perplexity Terms of Service: https://www.perplexity.ai/hub/legal/terms-of-service and Privacy Policy: https://www.perplexity.ai/hub/legal/privacy-policy
Anthropic Privacy Policy: https://www.anthropic.com/legal/privacy
Ahrefs API v3
Used by AI answer citations to read how often AI answers cite your pages (Ahrefs Brand Radar).
Host: api.ahrefs.com.
When: only while the Ahrefs feature is enabled and an API key is saved: a weekly sync (one request plus one for each selected AI platform), plus “Test connection” and “Sync now”. Calls use Ahrefs API units from your Ahrefs subscription.
Data sent: your API key, the target domain, the selected AI platforms and the optional country.
Ahrefs Terms of Service: https://ahrefs.com/legal/terms
Ahrefs Privacy Policy: https://ahrefs.com/legal/privacy-policy
Privacy Policy
BaseCloud UTM Tracker uses first-party cookies and browser storage for campaign and content attribution. Its server never sends data to BaseCloud. Data only leaves your site through integrations you configure yourself: your form, lead and report webhooks, the Meta Conversions API, the BaseCloud Forms bridge (which adds attribution to BaseCloud CRM forms already embedded on your pages), and the Search Console, Google …
