Skip to content
PluginCanary

AdWords Conversion Tracking Code

by kcseopro · 1,000+ active installs · Checked 3 Nov 2026
Avoid2 Criticals1 Warning

Avoid: vulnerability published 31 Dec 2025 still has no fix after 14 days.

39/ 100 Canary Score

Capped at 39 while a vulnerability has no patch.

Sub-scores for AdWords Conversion Tracking Code
Ownership100
Maintenance0
Security35
Support70
Reputation70

How the score works

Active signals

Facts we detected, with links to the source.

  • CriticalSEC-2Vulnerability published 31 Dec 2025 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.14 Jan 2026Evidence
  • CriticalMNT-1No release in 108 months (last release 28 Nov 2017). Plan a replacement if the plugin is important to your site.28 Nov 2018Evidence
  • WarningMNT-2Tested up to WordPress 4.3.34, 28 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

No ownership changes recorded since 3 Nov 2026.

Maintenance

Last release
9 years ago
Releases, 24 months
0
Tested up to
4.3 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter for AdWords Conversion Tracking Code
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20260

Last release 28 Nov 2017. Tested up to 4.3, 28 major versions behind WordPress 7.1.

Support

Support history appears after our first snapshots of the forum counts.

Security record

PublishedIssueCVSSAffectedFixed inDays to patch
31 Dec 2025AdWords Conversion Tracking Code <= 1.0 - Authenticated (Contributor+) Stored Cross-Site Scripting6.4<= 1.0No fixn/a

Source: Wordfence Intelligence.

Reputation

Lifetime rating 5.0 from 1 ratings. Quarterly trends appear as new reviews arrive.

Rating distribution
5 star1
4 star0
3 star0
2 star0
1 star0

Momentum

1,000+ active installs. History builds with each weekly snapshot.

Weekly downloads, last 27 weeks
Weekly downloads for AdWords Conversion Tracking Code
4 May 202614
11 May 202625
18 May 202624
25 May 202634
1 Jun 202624
8 Jun 202635
15 Jun 202621
22 Jun 202618
29 Jun 202621
6 Jul 202619
13 Jul 202619
20 Jul 202621
27 Jul 202629
3 Aug 202639
10 Aug 202634
17 Aug 202631
24 Aug 202630
31 Aug 202627
7 Sep 202632
14 Sep 202652
21 Sep 202644
28 Sep 202652
5 Oct 202645
12 Oct 202641
19 Oct 202666
26 Oct 202685
2 Nov 202613

Weekly downloads over the last 4 weeks are 55% above the 27-week average.

Healthier alternatives

Same category, higher Canary Score. Never sponsored.

Post Views CounterScore 93 · 100,000+Page Visits Counter - LiteScore 93 · 5,000+GA Google Analytics - Connect Google Analytics to WordPressScore 92 · 400,000+Matomo Analytics - Powerful, Privacy-First Insights for WordPressScore 92 · 100,000+Microsoft ClarityScore 91 · 200,000+

Facts

Version1.0
Authorkcseopro
Added9 Sep 2015
Last updated28 Nov 2017
Active installs1,000+
Requires WordPress3.0.1
Tested up to4.3.34
Requires PHPnot stated
CategoryMarketing & Advertising > Advertising & PPC Management
Tagsads, widget, adsense, widgets, custom ad

Questions

Is AdWords Conversion Tracking Code still maintained?

AdWords Conversion Tracking Code was last updated on 28 Nov 2017. Its Canary status is Avoid.

Is AdWords Conversion Tracking Code safe?

AdWords Conversion Tracking Code has 1 published vulnerability with no patched version. Its Canary status is Avoid.

Who owns AdWords Conversion Tracking Code?

The wordpress.org author is kcseopro. Recent committers: kcseopro, plugin-master. We have recorded no ownership change.

What can I use instead of AdWords Conversion Tracking Code?

Plugins in the same category with a higher Canary Score: Post Views Counter, Page Visits Counter - Lite, GA Google Analytics - Connect Google Analytics to WordPress, Matomo Analytics - Powerful, Privacy-First Insights for WordPress, Microsoft Clarity.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews, Wordfence Intelligence.Plugin data refreshed 3 Nov 2026.Report a data issue