AdPriva
| 开发者 | adprivadevops |
|---|---|
| 更新时间 | 2026年10月21日 22:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
AdPriva verifies your traffic with cryptographic proofs so you can tell real, human visits from
abusive bots. Install the plugin, click Connect with AdPriva (a secure OAuth sign-in — no API keys
to copy), and the plugin will:
- Register and verify your site with AdPriva automatically.
- Provision a site placement and load the AdPriva verification tag on your site from the AdPriva CDN.
- Show a traffic & validity summary right on your WordPress dashboard, with a link to your full AdPriva console.
- Settings page — control where the tag loads (post types, exclude logged-in users,
administrators, or specific URLs), choose whether the tag waits for visitor consent (consent
mode), toggle the dashboard widget, and (advanced) override the AdPriva endpoints. Consent
plugins can suppress the tag through the
adpriva_should_load_tagfilter. - In-admin dashboard — KPI cards, a human vs. bot verdict breakdown, and a trend chart over the last 7, 30, or 90 days, all without leaving WordPress.
安装:
- Upload the plugin to
/wp-content/plugins/adpriva, or install it from the Plugins screen. - Activate it.
- Open the AdPriva menu and click Connect with AdPriva.
屏幕截图:
常见问题:
Do I need an AdPriva account?
Yes. The Connect button signs you in to AdPriva; you approve the connection for your organization.
Does this collect my visitors' personal data?
No. The plugin sends your site's domain and the connection token to AdPriva. Traffic verification is performed by AdPriva using privacy-preserving signals.
How do I stop loading the tag?
Disconnect from the AdPriva settings page, or use the adpriva_should_load_tag filter to control it.
Can the tag wait for my visitors' consent?
Yes. Under Settings → Visitor consent, choose TCF if your consent banner supports the IAB TCF
v2 framework (the tag then waits for consent to purpose 1, "Store and/or access information on a
device"), or Manual to call AdPriva.grantConsent() and AdPriva.revokeConsent() from your own
consent tool. Setup steps for Cookiebot, OneTrust, Usercentrics and Google Tag Manager are at
https://docs.adpriva.com/developer-docs/tag-installation/#consent-modes
更新日志:
1.2.0
- New: Settings → Visitor consent → Consent mode. TCF makes the tag wait for consent from your IAB TCF v2 consent banner; Manual makes it wait until your site calls
AdPriva.grantConsent(). In both modes the tag sends nothing before consent and stops when consent is withdrawn. Off, the default, keeps the current behaviour. This is a new setting, unrelated to the "Consent integration" option removed in 1.1.0. - Changed: the tag's
<script>now loads withasync, so it never delays your pages. - Translations: added the new strings to the
.potfile.
- Removed: the "Consent integration" setting. It never changed when the tag loads. To hold the tag until consent, use the
adpriva_should_load_tagfilter (unchanged). - Removed: the
data-placementattribute on the tag's<script>and the "Placement ID" line on the Settings page. The tag identifies your site by its domain and never read the attribute. - Translations: regenerated the
.potfile.
- Fixed: the default AdPriva console address now points at console.adpriva.com. The "Open console" links in the dashboard, settings page, and widget previously went to the wrong AdPriva app unless you had set an endpoint override.
- Compliance: the Contributors field now lists the plugin owner's WordPress.org account, as required for the directory listing.
- Removed the unused Plugin URI header and hardened WordPress Plugin Check (strict mode) for a clean review. No functional changes.
- First stable release, submitted to the WordPress.org plugin directory.
- Connect with AdPriva via OAuth 2.0 authorization-code with PKCE — no API keys to copy.
- Loads the AdPriva verification tag from the CDN with your provisioned placement ID.
- Settings page: tag targeting (post types, exclude logged-in users / administrators / URLs), consent integration mode, dashboard preferences, and advanced endpoint overrides.
- In-admin dashboard and dashboard widget: KPI cards, human vs. bot verdict breakdown, and a 7/30/90-day trend chart.
- New: in-admin dashboard with KPI cards, verdict breakdown, and a 7/30/90-day trend chart (no console trip needed).
- New: Settings page — tag targeting (post types, exclude logged-in users / administrators / URLs), consent integration mode, dashboard preferences, and advanced endpoint overrides.
- New: the dashboard widget can be toggled from Settings, and now links to the in-admin dashboard.
- Endpoint URLs resolve as: a wp-config constant wins, then a Settings override, then the built-in default.
- Initial release: Connect with AdPriva (OAuth + PKCE), CDN tag injection, and a dashboard traffic widget.