Redkirin Ad Click Verification
by redkirin 1 (0 reviews)

Redkirin Ad Click Verification

Ad fraud protection (アドフラウド対策) for conversions: keeps bot clicks on phone, LINE, email and other tracked links out of GA4 events and Google Ads.

Redkirin Ad Click Verification ranks #36,951 among WordPress.org plugins with 10+ active installations, is #1,371 of 4,265 in the SEO & Marketing category, a 1/5 rating from 0 reviews, and was last updated Oct 26, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v1.9.8 Current Version v1.9.8
Updated 1 week ago Last Update on 26 Oct, 2026
Refreshed 1 week ago Last Refreshed on
#1,371 of 4,265 in SEO & Marketing Top 50% by installs Downloads -62.7% this week Actively maintained
View on WordPress.org
Rank
#36,951
— No change
Active Installs
10+
— No change
KW Avg Position
11
— No change
Downloads
625
+1 today
Support Resolved
0%
— No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 20

Total Progress 70%
10+ 20+
13,778
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 3 more installs to reach 20+

Rank Changes

35,103 36,027 36,951 37,875 38,799 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
35,441 38,713 41,985 45,256 48,528 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #36,951
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 30 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 100 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Redkirin Ad Click Verification

No. Only the measurement is withheld. Phone calls, LINE and other links always work; when a click is intercepted the plugin performs the navigation itself.
Not necessarily. With "Intercept unverified clicks" enabled, existing "Click – Just Links" triggers simply stop firing for bots. For the cleanest setup, create a custom event trigger for rkacv_verified_click and pause your old click triggers to avoid double counting.
A tap within the minimum dwell time (default 1 second) with no prior interaction cannot be distinguished from a bot and is not measured. Lower the dwell time or set the required signal count to 0 if this matters more than bot filtering.
Yes. All verification happens in the browser and via the REST API. Behind a reverse proxy or CDN, return the real visitor IP with the rkacv_client_ip filter so the IP range check works.
An optional log of blocked / verified clicks: time, link URL, page URL, reason, dwell time, signal count, user agent and an anonymised IP (last octet / lower 80 bits zeroed; can be disabled). Logs are purged after the configured number of days and the table keeps the newest 20,000 rows. Everything is removed on uninstall.
Yes. Obvious bots get no tags at all ("Fire no tags for obvious bots"), and once a visitor is verified the plugin pushes rkacv_verified_pageview. Use that event, optionally with a page path condition, as your key event instead of page_view. Bots that are only recognisable after the page view was sent (IP range, no interaction) cannot be removed from page_view itself, which is why the verified event exists.
Yes. Verification acts on the page, so it is platform-independent. Click IDs from Google, Meta (fbclid), Yahoo! JAPAN (yclid), LINE, TikTok, X and Microsoft are recognised for landings and repeat suppression, and the report shows a per-platform breakdown. Fire each platform's conversion tag from GTM on the verified events (rkacv_verified_click, rkacv_form_submit, rkacv_verified_pageview); a directly installed Meta Pixel can receive the verified events as custom events.
It shows, per campaign and per placement, how many landings carried definite bot signals (webdriver, synthetic clicks, headless user agents, crawler IPs) versus how many looked human. Placement and device breakdowns require Google Ads ValueTrack parameters in your tracking template, for example {lpurl}?campaignid={campaignid}&placement={placement}&device={device}. The plugin never changes your Google Ads account; exclusions are applied by you in Google Ads.
The log is diagnostic data reported by visitors' browsers. The endpoint requires a token signed by the site, but the token is part of the public page, so anyone who can load the page can also post entries. Treat the log as a tuning aid, not as evidence: it never changes what GA4 or Google Ads measure. Writes are rate limited per IP and site-wide, capped per IP per day, and when the table is full the oldest rows are discarded so new entries are always stored.

Sign In / Register

You need to sign in or register to use this feature.