{"id":11902,"date":"2026-09-28T16:07:06","date_gmt":"2026-09-28T08:07:06","guid":{"rendered":"https:\/\/aeosub.com\/adpriva\/"},"modified":"2026-09-28T16:07:06","modified_gmt":"2026-09-28T08:07:06","slug":"adpriva","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/adpriva\/","title":{"rendered":"AdPriva"},"content":{"rendered":"
\"AdPriva\"<\/div>\n
\n
LethaldiranMX Insight<\/div>\n
\n
\n

AdPriva addresses a critical blind spot in modern web operations by delivering privacy-conscious, cryptographic traffic verification directly into the WordPress dashboard. By replacing complex manual API configurations with a secure OAuth 2.0 PKCE flow and serving a lightweight tag via CDN, it lowers the barrier to distinguishing genuine human engagement from automated bot traffic. For publishers and site operators looking to audit their audience quality without compromising GDPR compliance or introducing heavy server-side tracking overhead, this plugin offers a highly streamlined, drop-in solution.<\/p>\n

Best Fit & Operational Role:<\/strong> This plugin is an excellent fit for publishers, ad-supported content sites, and digital marketers who need to validate their traffic quality for advertisers or internal audits without the weight of traditional analytics suites. It integrates cleanly into the WordPress stack as a non-intrusive monitoring layer, utilizing a single database option to store its configuration. Its granular control settings\u2014allowing administrators to exclude logged-in users, specific roles, or precise URLs\u2014make it highly adaptable for membership sites or e-commerce platforms where administrative or transactional traffic would otherwise skew verification metrics.<\/p>\n

Potential Limitations & Pitfalls:<\/strong> While the plugin is lightweight, it relies on external assets, specifically loading a front-end verification script from AdPriva’s CDN and making remote API requests to populate the wp-admin dashboard. Site administrators must ensure their Content Security Policies (CSP) are configured to allow connections to both the API and CDN endpoints to prevent script blocking. Additionally, while the plugin offers integration with consent management tools, sites operating under strict zero-cookie or zero-consent-prior-to-interaction policies will need to carefully configure the tag’s loading behavior to ensure compliance alignment.<\/p>\n<\/div>\n<\/div><\/div>\n

\n
\n \"AdPriva <\/p>\n
\n
Plugin Specification<\/div>\n

WordPress.org Official Data<\/small>\n <\/div>\n<\/p><\/div>\n\n\n\n\n\n\n\n
Developer<\/th>\nAdPriva<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv1.0.2<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n6.0 \/ 7.1.2<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-09-28 8:03am GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details -><\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
Privacy-first traffic verification. Connect your site to AdPriva, load the tag, and see human vs. bot traffic in your WordPress dashboard.<\/div>\n

AdPriva verifies your traffic with cryptographic proofs so you can tell real, human visits from
\nabusive bots. Install the plugin, click Connect with AdPriva<\/strong> (a secure OAuth sign-in \u2014 no API keys
\nto copy), and the plugin will:<\/p>\n

    \n
  • Register and verify your site with AdPriva automatically.<\/li>\n
  • Provision a site placement and load the AdPriva verification tag on your site from the AdPriva CDN.<\/li>\n
  • Show a traffic & validity summary right on your WordPress dashboard, with a link to your full
    \nAdPriva console.<\/li>\n<\/ul>\n

    The plugin is self-sufficient inside wp-admin:<\/p>\n

      \n
    • Settings page<\/strong> \u2014 control where the tag loads (post types, exclude logged-in users,
      \nadministrators, or specific URLs), choose how it cooperates with consent plugins, toggle the
      \ndashboard widget, and (advanced) override the AdPriva endpoints.<\/li>\n
    • In-admin dashboard<\/strong> \u2014 KPI cards, a human vs. bot verdict breakdown, and a trend chart over the
      \nlast 7, 30, or 90 days, all without leaving WordPress.<\/li>\n<\/ul>\n

      No personal data about your visitors is collected by this plugin. Verification happens server-side at
      \nAdPriva using privacy-preserving signals.<\/p>\n

      Connecting<\/h4>\n

      After activating, open the AdPriva<\/strong> menu in wp-admin and click Connect with AdPriva<\/strong>. You will be
      \nsent to AdPriva to approve the connection for your organization, then returned to your site \u2014 connected.<\/p>\n

      External services<\/h3>\n

      This plugin connects to AdPriva, a third-party service, to verify your traffic. This is required for
      \nthe plugin to function.<\/p>\n

      1. AdPriva API \u2014 https:\/\/api.adpriva.com<\/code><\/strong>
      \nUsed to: complete the “Connect with AdPriva” sign-in (OAuth 2.0 authorization-code with PKCE), register
      \nand verify your site’s domain, provision a site placement, and fetch your traffic summary and per-day
      \ntrend for the dashboard widget and the in-admin dashboard.
      \nData sent: your site’s domain, the OAuth authorization parameters, and the access token issued to this
      \ninstall. No visitor personal data is sent by the plugin.
      \nTerms: https:\/\/adpriva.com\/terms \u2014 Privacy Policy: https:\/\/adpriva.com\/privacy<\/p>\n

      2. AdPriva verification tag (CDN) \u2014 https:\/\/cdn.adpriva-ads.com\/tag.js<\/code><\/strong>
      \nUsed to: load the lightweight verification tag on your site’s front end (with your provisioned
      \nplacement ID) so AdPriva can verify traffic. The script is served from AdPriva’s CDN.
      \nTerms: https:\/\/adpriva.com\/terms \u2014 Privacy Policy: https:\/\/adpriva.com\/privacy<\/p>\n

      Privacy<\/h3>\n
        \n
      • The plugin stores a single option in your database holding the AdPriva connection: access\/refresh
        \ntokens (encrypted at rest using your site’s WordPress salts), your placement ID, and your domain.<\/li>\n
      • The plugin does not set cookies and does not collect or store your visitors’ personal data.<\/li>\n
      • You can disconnect at any time from the AdPriva<\/strong> settings page; this revokes the access token and
        \ndeletes the stored connection. Uninstalling the plugin removes all stored data.<\/li>\n
      • Respecting consent: the tag only loads when connected and when your Settings \u2192<\/span> Tag targeting rules
        \nallow it, and a consent\/privacy plugin can always suppress it via the adpriva_should_load_tag<\/code>
        \nfilter (the filter is the final override).<\/li>\n
      • Settings are stored in a separate adpriva_settings<\/code> option; they contain no visitor data.<\/li>\n<\/ul>\n
        Editorial note: This overview combines WordPress.org official plugin metadata with an AI-assisted LethaldiranMX editorial review. Plugin data should be verified on the official WordPress.org listing before installation.<\/div>","protected":false},"excerpt":{"rendered":"

        Privacy-first traffic verification. Connect your site to AdPriva, load the tag, and see human vs. bot traffic in your WordPress dashboard.<\/p>","protected":false},"author":1,"featured_media":11903,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[760,786,787,3110,3111,555],"class_list":["post-11902","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-analytics","tag-bot-detection","tag-privacy","tag-traffic-quality","tag-traffic-verification","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=11902"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11902\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/11903"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=11902"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=11902"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=11902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}