Description
LeadSeed sets up Google Analytics and Google Tag Manager for small businesses, so they can see
which ads bring them leads. This plugin is how your WordPress site turns that tracking on.
- Install and activate this plugin.
- Tap Connect to LeadSeed (on the Plugins screen, or under LeadSeed in your WordPress
menu), then tap Approve in LeadSeed. You land back in your LeadSeed setup, connected.
Prefer a token? Open LeadSeed in your WordPress menu, choose “Have a connection token
instead? Paste it”, paste the token from your LeadSeed onboarding (“Turn on tracking” step), and
click Save & check connection. - That’s it. The plugin fetches your Google Tag Manager container from LeadSeed and adds the
snippet to every page for you. The settings page shows whether your connection is live, and
Disconnect this site turns it off.
What the plugin does on your site:
- Adds your Google Tag Manager snippet to every page (in the
<head>, plus the standard
FAQ
-
Do I need a LeadSeed account?
-
Yes. The plugin connects your site to LeadSeed; without an account it cannot add any tracking.
Sign up at https://myleadseed.com. -
Do I need a connection token?
-
Not usually. Tap Connect to LeadSeed and approve in LeadSeed instead. If the button can’t
finish on your site (a security or caching plugin can block the link back), the plugin says so and
offers the paste box. -
Where do I get the connection token?
-
From your LeadSeed onboarding, on the “Turn on tracking” step. It starts with
ls_. -
How do I disconnect my site?
-
Open LeadSeed in your WordPress menu and tap Disconnect this site. Tracking stops on your
pages straight away. If any leads haven’t reached your lead sheet yet, the page tells you how many
first: disconnecting deletes them from your site. -
The settings page says leads are waiting to be sent.
-
Nothing to do: they are safe on your site and the plugin keeps trying until LeadSeed confirms each
one. If the number keeps growing for more than a day, or the page says leads could not be saved on
this site, check your LeadSeed connection or contact LeadSeed support. -
It says “Token rejected”.
-
Re-copy the token from LeadSeed and paste it exactly (no extra spaces), then click Save & check
connection again. If you have lost the token, generate a new one in LeadSeed; the new one replaces
the old. -
Does this edit my theme?
-
No. The snippet is added by the plugin when each page is built, so it survives theme updates.
-
What happens if I deactivate or delete the plugin?
-
Deactivating stops the snippet and the scheduled check straight away. Leads still waiting to be
sent stay saved and are sent after you reactivate it. Deleting the plugin also removes everything it
stored, including your connection token and any leads still waiting to be sent.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“SowTrack Conversion Tracking” is open source software. The following people have contributed to this plugin.
Contributors
Translate “SowTrack Conversion Tracking” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.7.0
- Renamed to SowTrack Conversion Tracking; no functional change. The plugin still connects your
site to LeadSeed, and its LeadSeed menu, settings and connection are unchanged. - The plugin’s folder is now
sowtrack.
1.6.0
- Leads can now be delivered through LeadSeed, which writes them into the lead sheet in your own
Google account — no Apps Script to paste or deploy. LeadSeed tells the plugin which way your
account works; sites on the older Apps Script setup keep working exactly as before. - Every lead sent through LeadSeed is saved on your own site first and kept until LeadSeed confirms
it, so a lead is never lost to a brief outage. Sending happens after the visitor’s page has
finished, so forms are never slowed down. - The settings page shows how many leads are waiting to be sent, if any. Disconnecting tells you
first if waiting leads would be deleted. - Opening your site through LeadSeed’s test link marks your own test enquiry as a test.
1.5.0
- New Connect to LeadSeed button: tap it, approve in LeadSeed, and you’re connected. No token to
copy. Your site and LeadSeed swap the connection token directly, server to server. - New Disconnect this site button on the LeadSeed settings page.
- Until the site is connected, the Plugins screen shows a reminder to connect, which you can dismiss.
- The paste-a-token form still works exactly as before. Sites already connected with a token stay
connected when they update.
1.4.0
- Prepared for the WordPress.org plugin directory: the plugin’s folder is now
leadseed, scripts
are printed with WordPress’s own script helpers, and the readme documents every external service
the plugin uses. - Requires WordPress 5.7 or later.
- If you installed an earlier version from a .zip file, deactivate and delete it before installing
this one, then paste your connection token again (deleting the old copy removes its settings).
While an older copy is still active, WordPress will refuse to activate this version.
1.3.0
- Lead capture now also covers SureForms, Elementor Pro forms, Fluent Forms, Ninja Forms and
Jetpack Forms — alongside Contact Form 7, Gravity Forms and WPForms. Same direct site-to-Google
flow: your leads go straight to your own Google Sheet and are never routed through LeadSeed. - The connection status endpoint now reports whether a lead destination is configured, so LeadSeed
support can tell “not connected yet” apart from “connected but not working” without asking you to
dig through wp-admin. Only a yes/no is exposed — never your sheet URL or your secret.
1.2.0
- Lead capture now also forwards WPForms submissions (Lite and Pro, AJAX and native) to your
connected Google Sheet — same direct site-to-Google flow as Contact Form 7 and Gravity Forms.
1.1.0
- Lead capture: forwards Contact Form 7 and Gravity Forms submissions (with ad click-IDs) straight
to the Google Sheet you connect in LeadSeed. Lead data flows directly into that sheet — it is never
routed through LeadSeed.
1.0.0
- Initial release: pull-based GTM snippet injection + connection status endpoint.