Shield · WooCommerce

FindIP Shield for WooCommerce

Privacy-conscious visitor risk signals for your WooCommerce storefront: VPN, proxy, Tor, relay, hosting, datacenter, malicious-IP, and network-service flags plus a risk score for every session — without collecting customer, cart, order, or payment data.

Installation

  1. Install and activate FindIP Shield for WooCommerce (WooCommerce is required; the standalone FindIP Shield WordPress plugin must be deactivated first — the two must not run together).
  2. Create a Shield site at findip.net → Shield → Sites → New site whose domain matches your storefront hostname.
  3. Open WooCommerce → FindIP Shield, paste the site's public key (pub_…), and save.
  4. Load a storefront 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, so the browser refuses to run a script that does not match the recorded hash.

What it tracks

Standard SDK events (session_start, page_view, automatic form events) plus WooCommerce storefront signals, each individually toggleable:

SignalEvent
Product page viewcustom with event_type: product_view
Cart page viewcustom with event_type: cart_view
Item added / removed (classic and Blocks)custom with event_type: cart_updated and action
Checkout page viewcustom with event_type: checkout_view
Checkout error / payment failurepayment_failed
Order received pagecustom with event_type: order_received

All events carry integration: woocommerce. Only coarse page-type context is sent — never product identifiers, prices, customer fields, or payment data.

Privacy and consent

  • Privacy modes — strict (default), balanced, advanced, identical to the Shield SDK modes.
  • Consent-aware initialization — 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.
  • Compatible with High-Performance Order Storage (HPOS) and Cart/Checkout Blocks; telemetry failures never affect storefront behavior.

Server-side verification

Browser risk responses are informational. For decisions that matter (order review, fraud holds), verify the session server-side with your secret key — see Server Verification.