Title: Capybara SEO Lead Source Tracker Author: capybaraseo Published: August 18, 2026 Last modified: August 18, 2026 --- Search plugins ![](https://ps.w.org/capybara-seo-lead-source-tracker/assets/banner-772x250.png? rev=3653496) ![](https://ps.w.org/capybara-seo-lead-source-tracker/assets/icon.svg?rev=3653496) # Capybara SEO Lead Source Tracker By [capybaraseo](https://profiles.wordpress.org/capybaraseo/) [Download](https://downloads.wordpress.org/plugin/capybara-seo-lead-source-tracker.0.7.0.zip) * [Details](https://wordpress.org/plugins/capybara-seo-lead-source-tracker/#description) * [Reviews](https://wordpress.org/plugins/capybara-seo-lead-source-tracker/#reviews) * [Installation](https://wordpress.org/plugins/capybara-seo-lead-source-tracker/#installation) * [Development](https://wordpress.org/plugins/capybara-seo-lead-source-tracker/#developers) [Support](https://wordpress.org/support/plugin/capybara-seo-lead-source-tracker/) ## Description Capybara SEO Lead Source Tracker captures UTM parameters and click IDs (gclid, gbraid, wbraid, fbclid) from the URL, stores them in localStorage (first-touch attribution), and automatically updates WhatsApp links with a dynamic message that includes the lead source data. **Key features:** * Captures utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid, gbraid, wbraid, fbclid * First-touch attribution: data is preserved across pages even if subsequent visits have no UTMs * Automatic channel detection: Google Ads, Meta Ads, Organic, Referral * Lines with no captured data are omitted from the WhatsApp message * Combinable button placements: Floating button (auto-injected, zero setup) and CSS Selector (reuse existing buttons) can both be turned on at once, plus the always-available [capysele_button] shortcode — all sharing the same number and tracking * Customizable message template with placeholders * Multilingual: English and Spanish included. Language is set automatically based on the WordPress site locale. * Debug mode: logs captured data to the browser console **Available placeholders for the message template:** {channel}, {utm_source}, {utm_medium}, {utm_campaign}, {utm_content}, {utm_term},{ gclid}, {gbraid}, {wbraid}, {fbclid}, {landing_page}, {captured_at} ## Screenshots [⌊Configure the receiving number and choose one or more button placements.⌉⌊Configure the receiving number and choose one or more button placements.⌉[ Configure the receiving number and choose one or more button placements. [⌊Customize the message template with first-touch attribution placeholders.⌉⌊Customize the message template with first-touch attribution placeholders.⌉[ Customize the message template with first-touch attribution placeholders. [⌊Display the tracked floating button and shortcode button on a WordPress page.⌉⌊ Display the tracked floating button and shortcode button on a WordPress page.⌉[ Display the tracked floating button and shortcode button on a WordPress page. [⌊Send a prefilled WhatsApp message containing the captured lead-source data.⌉⌊Send a prefilled WhatsApp message containing the captured lead-source data.⌉[ Send a prefilled WhatsApp message containing the captured lead-source data. ## Installation 1. Upload the plugin zip from Plugins > Add New > Upload Plugin. 2. Activate the plugin. 3. Go to Settings > Capybara SEO Lead Source Tracker. 4. Set your WhatsApp number and message template. 5. Turn on “Floating button” for a ready-to-use button with no further setup, and/ or turn on “CSS Selector” with the CSS class of an existing button to add tracking to it — both can be enabled together. The [capysele_button] shortcode is always available regardless of these toggles. 6. Test with a URL containing UTM parameters, e.g. ?utm_source=google&utm_medium=cpc& utm_campaign=test ## FAQ ### Does it work with any WhatsApp button? Yes. Enable “CSS Selector” and set the selector to match your existing buttons ( e.g. a[href*=”wa.me”]) and the plugin will update their href automatically. This can be combined with the floating button at the same time. ### What is first-touch attribution? The first UTM parameters captured during a user’s session are stored and kept even if the user navigates to other pages without UTMs. This way, the original traffic source is always preserved in the WhatsApp message. ### What happens if a field has no data? Lines in the message template whose placeholder has no captured value are automatically removed from the WhatsApp message. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Capybara SEO Lead Source Tracker” is open source software. The following people have contributed to this plugin. Contributors * [ Capybara SEO ](https://profiles.wordpress.org/capybaraseo/) [Translate “Capybara SEO Lead Source Tracker” into your language.](https://translate.wordpress.org/projects/wp-plugins/capybara-seo-lead-source-tracker) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/capybara-seo-lead-source-tracker/), check out the [SVN repository](https://plugins.svn.wordpress.org/capybara-seo-lead-source-tracker/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/capybara-seo-lead-source-tracker/) by [RSS](https://plugins.trac.wordpress.org/log/capybara-seo-lead-source-tracker/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.7.0 * Renamed internal PHP/JS/CSS identifiers (constants, classes, option key, shortcode, script/style handles, JS global, localStorage key, CSS classes) from the `wa_ls`/` WA_LS`/`wa-ls` prefix to `capysele`, per WordPress.org review feedback that the old prefix (inherited from an earlier codename) wasn’t distinctive. The shortcode is now [capysele_button]. * readme.txt Description, Installation and FAQ are now English-only, per WordPress. org guidelines. Spanish content in the plugin UI itself is unaffected — it’s still handled via standard WordPress i18n. * Removed the bundled es_ES .po/.mo translation files from the package; translations are now handled via translate.wordpress.org once the plugin is live. * Removed the now-unnecessary load_plugin_textdomain() call and its accompanying plugin_locale filter (not needed for WordPress.org-hosted plugins since WP 4.6). * Settings are stored under a new option key (capysele_settings); existing installs will start from defaults after updating. #### 0.6.2 * Renamed the plugin again, from “Capybara SEO Lead Source Tracker for WhatsApp” to “Capybara SEO Lead Source Tracker” — WordPress.org’s readme validator flagged“ whatsapp” as a restricted term that cannot appear anywhere in the plugin name or permalink/slug (not just at the start). The word is still used freely in the description, FAQ, and tags, which aren’t restricted. No functional changes; settings and stored data are preserved. #### 0.6.1 * Renamed the plugin from “WA Lead Source Tracker” to “Capybara SEO Lead Source Tracker for WhatsApp” — WordPress.org rejected the “WA” prefix as a restricted trademark-related term at the start of a plugin name/slug. No functional changes; settings and stored data are preserved. #### 0.6.0 * Added a floating WhatsApp button that the plugin can auto-inject on every page( bottom-right, standard chat-bubble style), with no need for an existing button, link, or shortcode placement. * Replaced the old single, mutually-exclusive “operation mode” with independent, combinable toggles: Floating button and CSS Selector can now be turned on at the same time (e.g. keep tracking your existing button and also show the floating button on pages that don’t have one). The shortcode is now always available regardless of these toggles. Existing sites are migrated automatically — no action needed. * Reorganized the settings page into numbered sections (Enable & number, Where the button appears, Message, Advanced) with a plain-language guide explaining when to turn on each option. #### 0.5.8 * Added a settings link directly inside the plugin’s description on the Plugins screen (in addition to the existing “Settings” row action). * Plugin header Description is now sourced in English and translated to Spanish, consistent with the rest of the plugin’s i18n strings. #### 0.5.7 * Fix: regional Spanish site locales (es_PE, es_MX, es_AR, es_CO, etc.) fell back to English because the bundled translation only matched es_ES exactly. Any es_* locale now maps to the bundled es_ES translation. * Fully translated the default WhatsApp message template into Spanish (source/medium/ campaign/term labels were previously left in English). * Added a “Settings” quick link to the plugin’s row on the Plugins screen. #### 0.5.6 * Fix: organic Google/Bing/Yahoo/DuckDuckGo/Baidu/Yandex/Ecosia search traffic without UTMs was misclassified as Referral instead of Organic. Search engine referrers are now detected and mapped to the Organic channel before the generic referral fallback. #### 0.5.5 * Added referral URL tracking via document.referrer: external referrers are captured and exposed via the {referrer} placeholder, and used as a fallback signal for Referral channel detection. #### 0.5.4 * Fix Joinchat integration: intercept click on document (capture phase) instead of updating data-settings DOM attribute, since Joinchat caches settings in memory on init. #### 0.5.3 * Joinchat plugin compatibility: selector targeting .joinchat updates message_send inside data-settings JSON. #### 0.5.2 * Replaced emoji with WhatsApp bold markdown (_[…]_) to avoid encoding corruption across all devices and WP sanitization pipeline. #### 0.5.1 * Replaced 📋 emoji with ⚠️ (better device support). #### 0.5.0 * Default message template now includes a framed reference block before tracking variables to discourage users from deleting attribution data. #### 0.4.0 * Added multilingual support: English and Spanish (auto-detected from WordPress site locale). * English set as source language following WordPress i18n standards. * Channel labels (Organic, Referral, etc.) are now translatable. #### 0.3.0 * Fixed channel detection: gclid, gbraid, wbraid now correctly identify Google Ads without requiring UTM parameters. * Removed “Directo / sin dato” fallback — channel line is now hidden when there is no attribution data. * Lines with no captured data are filtered from the WhatsApp message. * Consecutive blank lines collapsed after filtering. #### 0.2.0 * Operation mode (CSS Selector vs Shortcode) now correctly controls which buttons are targeted. * Shortcode mode targets only plugin-generated buttons. #### 0.1.0 * Initial MVP release. ## Meta * Version **0.7.0** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.0.4** * PHP version ** 7.4 or higher ** * Tags * [attribution](https://wordpress.org/plugins/tags/attribution/)[leads](https://wordpress.org/plugins/tags/leads/) [tracking](https://wordpress.org/plugins/tags/tracking/)[UTM](https://wordpress.org/plugins/tags/utm/) [whatsapp](https://wordpress.org/plugins/tags/whatsapp/) * [Advanced View](https://wordpress.org/plugins/capybara-seo-lead-source-tracker/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/capybara-seo-lead-source-tracker/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/capybara-seo-lead-source-tracker/reviews/) ## Contributors * [ Capybara SEO ](https://profiles.wordpress.org/capybaraseo/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/capybara-seo-lead-source-tracker/) ## Donate Would you like to support the advancement of this plugin? [ Donate to this plugin ](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=paypal@ilmaistro.pe¤cy_code=USD)