| 开发者 | forgeonline |
|---|---|
| 更新时间 | 2026年6月18日 07:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
leadsource folder to /wp-content/plugins/No. LeadSource hooks into your form plugin automatically. There are no shortcodes to add, no hidden fields to configure, and no form templates to edit.
Yes. The plugin also detects ad platform click IDs (gclid, fbclid, etc.) and automatically labels the traffic source. Even visitors arriving via organic search or direct traffic are categorised.
No. The frontend script is tiny vanilla JavaScript (no jQuery dependency) that runs once on page load to read URL parameters. There are no external API calls and no impact on page load speed.
Yes. The UTM capture runs in the visitor's browser via JavaScript, so server-side caching does not interfere with tracking.
The plugin uses "Same Session" attribution — the captured UTM data persists until the browser is closed. This is the most accurate setting and prevents cross-session over-counting.
No. All data is stored locally in your WordPress database. The plugin does not communicate with any external analytics or tracking service.
Yes. LeadSource captures the Google Click ID (gclid) on every form submission, so you can match leads back to the campaigns, ad groups and keywords that produced them and feed conversions back into Google Ads.
Yes. LeadSource records lead source and full UTM attribution automatically for Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Formidable Forms, Fluent Forms and Elementor Pro Forms, with no per-form setup.
LeadSource uses same-session attribution. The captured source persists until the browser is closed, which avoids the cross-session over-counting that long cookie windows can cause.