FindIP Shield for WordPress

1. In WordPress admin, open Plugins → Add New Plugin, search for FindIP Shield, install and activate.
2. Create a Shield site at findip.net → Shield → Sites → New site whose domain matches your WordPress hostname.
3. Open Settings → FindIP Shield, paste the site's public key (starts with pub_), and save.
4. Load a public page, then confirm the first event on your Shield site's Install page.

The plugin loads an exact, immutable Shield SDK build from cdn.findip.net with subresource integrity — the browser refuses to run a script that does not match the recorded hash. Login pages are covered as well as public pages.

• Privacy mode — strict (default), balanced, or advanced, identical to the Shield SDK modes. Strict sends the page and session data every mode sends (including form metadata and the form outline, never field values) with the browser's user agent, language and timezone, and leaves out the visitor ID, screen and device details, and the form snapshot. It sets no visitor cookie. See Data Collection.
• Automatic tracking — page views, one session_start per browser session, and form-activity events derived from form attributes only; field values are never read.
• Consent — with require consent enabled, the plugin starts in the configured pre-consent behavior (strict or disabled) until your consent tool dispatches a findip:consent event:

document.dispatchEvent(new CustomEvent('findip:consent', {
  detail: { granted: true }
}));

If WooCommerce is active, this plugin can additionally emit cart, checkout, payment-failure, and order-completion context (toggleable in settings). For richer storefront signals with per-event controls, use the dedicated FindIP Shield for WooCommerce plugin instead — the two plugins are mutually exclusive and must not run together.

Events report integration: wordpress in the dashboard, so WordPress traffic is distinguishable from plain JavaScript or Google Tag Manager installations.

Browser risk responses are informational. For decisions that matter (sign-ups, checkouts), verify the session server-side with your secret key — see Server Verification.