Social Proof for WordPress Agencies: Licence and Rollout Checklist

Scope: a deployment checklist based on TrueProof 2.4.0 code and the published licence offer, reviewed October 2, 2026. This is not a customer case study or a measured conversion result.

Short answer: use Free when each client only needs core WooCommerce orders or approved reviews with ordinary display controls. Choose Pro for paid sources or selected-context rules on up to five sites; Agency offers the same paid capabilities with an allowance of up to 999 sites. Each site has its own settings and source data. TrueProof does not provide a hosted fleet dashboard, automatic cross-site configuration or network-wide WordPress Multisite activation.

Choose the licence by the client’s actual workflow

Free can be useful on many client sites without a paid key. An agency licence is not necessary solely because you manage several WooCommerce installations. Conversely, a Pro key is not a replacement for each site’s source plugin or operational checks.

1. Document ownership and product fit

Record the purchase owner, renewal contact, client’s required source, planned page scope and who can approve publicly displayed fields. Agree how the licence will be handled if the client leaves your service. Keep keys in an appropriate secret store; do not put them in screenshots, public tickets or this checklist.

TrueProof Pro is €49 billed annually; Agency is €149 billed annually. Both renew until cancelled; applicable EU VAT can be added at checkout. Check current pricing and the original-purchase refund terms before committing a client. Priority email support is available during the paid period, not a published response-time SLA.

2. Prove one site’s setup before rolling it out

1. Install the current WordPress.org plugin and record WordPress, PHP, source-plugin and TrueProof versions.
2. Use staging for synthetic orders; the widget is initially disabled. Activate a paid licence only where the chosen feature requires it.
3. Select Real Data, the intended source, a defensible look-back window and Fully anonymous identity. Existing upgrades may preserve an older identity choice.
4. Verify an authorized eligible event and its public REST fields. Do not convert sample activity into a real customer claim.
5. Choose a conservative page scope and position, enable the widget, and test while logged out on desktop and mobile.

For WooCommerce, the step-by-step installation guide and diagnostic checklist cover eligible order statuses, cache, security and rendering. Do not copy a working site’s configuration blindly: another client can have different statuses, theme overlays or privacy expectations.

3. Check display rules without promising URL targeting

The paid selected-context options are front/posts page, blog posts, pages, WooCommerce products and archives. They are page-type tests, not arbitrary URL allowlists or visitor segments. Selecting Pages can include a normal WordPress checkout page; it is not a dedicated “exclude checkout” control. With a standard WooCommerce structure, product-only scope is a more restrained starting point, but inspect the actual cart and checkout rather than assuming all themes share that structure.

The event feed is not automatically matched to the product currently being viewed. If a client requires checkout-specific exclusions, per-product matching or other custom targeting, document the missing requirement rather than promising a feature the released plugin does not provide.

4. Keep activation and handover auditable

Each site activates its key against wptrueproof.com. The request includes the licence key, home URL and licence action; notification-source records are not part of the built-in licence request. Review the disclosed data flow with the client. A staging activation can consume a site allowance, so maintain an inventory of activated URLs and consult support if a migration leaves an unreachable old site.

For a replacement site, deactivate the old installation before activating the new one where possible. Do not assume WordPress Multisite sub-sites or staging URLs are exempt from limits. See licence movement and billing.

5. Measure client value honestly

Separate installation success from commercial results. Record eligible events, privacy approval, mobile obstruction checks and technical issues first. If the client has enough traffic, plan a comparison against a no-widget control using the conversion experiment worksheet. With little traffic, record the result as inconclusive rather than inventing an uplift.

A publishable case study needs the client’s permission, a dated configuration and clear limits. Never publish purchaser identities or licence keys, and do not reuse one store’s results as a universal promise.

Source evidence: released placement logic, per-site licence requests and the current Free versus paid feature table.