Title: LeadTrackr Author: Lester Visser Published: ଅକ୍ଟୋବର 9, 2024 Last modified: ସେପ୍ଟେମ୍ବର 9, 2026 --- Search plugins ![](https://ps.w.org/leadtrackr/assets/icon.svg?rev=3165679) # LeadTrackr By [Lester Visser](https://profiles.wordpress.org/leadtrackr/) [Download](https://downloads.wordpress.org/plugin/leadtrackr.1.1.2.zip) * [Details](https://ory.wordpress.org/plugins/leadtrackr/#description) * [Reviews](https://ory.wordpress.org/plugins/leadtrackr/#reviews) * [Development](https://ory.wordpress.org/plugins/leadtrackr/#developers) [Support](https://wordpress.org/support/plugin/leadtrackr/) ## Description ### Use of Third-Party Service This plugin relies on a third-party service provided by the plugin developer (LeadTrackr) to process and send form submissions. Specifically, form submissions are sent to the LeadTrackr API endpoint for the creation of leads. * API endpoint: `https://app.leadtrackr.io/api/leads/createLead` * API endpoint when an API token is configured: `https://app.leadtrackr.io/api/ leads/createServerSideLead`. This request also includes the visitor’s IP address and user agent. * The service processes lead creation requests using the submitted data. * For more information, please review the [LeadTrackr Terms of Use](https://leadtrackr.io/tos) and [Privacy Policy](https://leadtrackr.io/privacy-policy). By using this plugin, users agree to transmit data to this external service as part of the lead creation functionality. ### Remote Script The optional LeadBot contact launcher is loaded from a third-party CDN, and only when it is switched on in the plugin settings. Sites that leave it off request nothing from this host. * Script: `https://cdn.jsdelivr.net/gh/leadtrackr/leadtrackr-leadbot@1/dist/lt- leadbot.min.js` * Source code: https://github.com/leadtrackr/leadtrackr-leadbot * Submissions made through the LeadBot are sent to the same LeadTrackr API described above. ### Cookies With Channel Flow tracking enabled, the plugin sets two first-party cookies on the visitor’s browser: * `lt_channelflow` — the visitor’s marketing channel path (source, medium, campaign and landing page per session). Contains no personal information and no unique visitor identifier. Expires after 395 days. * `lt_session` — indicates whether the visitor is still within the same browsing session. Contains no visitor information. Expires after 30 minutes of inactivity. * `lt_consent` — the Google Consent Mode state (granted or denied per category) at the visitor’s last pageview, so it can be recorded alongside the lead. Only set on sites that run Google Consent Mode, and only when a definite state can be read. Contains no visitor information. Expires after 30 minutes of inactivity. Channel Flow tracking is enabled by default on new installations and left disabled on sites that update from an earlier version. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “LeadTrackr” is open source software. The following people have contributed to this plugin. Contributors * [ Lester Visser ](https://profiles.wordpress.org/leadtrackr/) [Translate “LeadTrackr” into your language.](https://translate.wordpress.org/projects/wp-plugins/leadtrackr) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/leadtrackr/), check out the [SVN repository](https://plugins.svn.wordpress.org/leadtrackr/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/leadtrackr/) by [RSS](https://plugins.trac.wordpress.org/log/leadtrackr/?limit=100&mode=stop_on_copy&format=rss). ## Changelog ### 1.1.2 **A failure inside the plugin can no longer break a form.** Everything that runs inside a visitor’s request — the six form integrations and the frontend scripts — is now wrapped so that whatever it throws is written to the error log and stops there. Tracking is worth less than the submission it observes: if LeadTrackr cannot record a lead, the visitor still sees their form go through. Fixed: * Sites configured by an earlier version could hold an empty value where a list of forms was expected. On PHP 8 that ended the request with a fatal error, so the form returned a 500 to the visitor and the lead was lost along with it. Stored form settings are now read as a list whatever the option holds, and rows that are not usable form records are skipped rather than deciding whether the form works. * The plugin’s own settings page failed to load on those same sites, which left the configuration unreachable exactly when it needed correcting. * Saving the settings with the Project ID field empty overwrote a working project ID with nothing. Every lead on the site stopped from that moment, while the form kept submitting and the page still said saved. That save is now refused, and the API keeps what it has if a project ID arrives empty anyway. ### 1.1.0 **Channel Flow no longer needs Google Tag Manager.** The plugin records the visitor’s journey itself, so a site without GTM gets a channel path too. One entry per session rather than per pageview, using the same definition GA4 uses: a new session after 30 minutes of inactivity, or when a new campaign brings the visitor in. Enabled by default on new installations and left off on sites that update, so nothing changes under an existing site’s feet. **The LeadBot can be switched on from the plugin.** A contact launcher for message, phone and WhatsApp, with settings for who is talking, which channels appear and how it looks. Nothing is requested from the CDN unless it is switched on. **Leads carry more context.** The landing page of each session, the page the conversion happened on, and the Google Consent Mode state at that moment. Consent is recorded only — the plugin never blocks on it; that stays the CMP’s job. **Optional API token for server-side delivery.** With a token, leads are sent server- side, which adds the visitor’s IP address and user agent. Sites that update keep working without one. Fixed: * Country domains of search engines were recorded as referrals instead of organic traffic, so a visitor arriving through google.nl showed up as `www.google.nl / referral`. * Composite name fields were stored as a single value. Fluent Forms and WPForms submit first and last name as one object, which ended up in the first name field in one piece. * Fields were matched in form order, so a company name appearing before the first name claimed that slot and the real first name was never stored. * Campaigns using auto-tagging without UTM parameters are now attributed through the click ID in the URL. * The Elementor form scan loaded every page builder blob on the site into memory, which could exhaust the memory limit on large sites. * The settings page could not be saved on sites without pretty permalinks. * Leads are no longer sent when no project ID is configured, and a failed delivery is logged instead of disappearing silently. * Divi’s tab was always available, even when Divi was not installed. ## Meta * Version **1.1.2** * Last updated **1 week ago** * Active installations **20+** * WordPress version ** 6.0 or higher ** * Tested up to **7.0.4** * PHP version ** 7.0 or higher ** * Language * [English (US)](https://wordpress.org/plugins/leadtrackr/) * [Advanced View](https://ory.wordpress.org/plugins/leadtrackr/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/leadtrackr/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/leadtrackr/reviews/) ## Contributors * [ Lester Visser ](https://profiles.wordpress.org/leadtrackr/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/leadtrackr/)