RoasProof for WooCommerce is a small plugin that bridges your store into RoasProof: it injects the tracking snippet, stamps the browser's identity onto each order, and sends paid orders to RoasProof automatically — no theme edits required.
1. Install the plugin
Download the plugin zip from https://app.roasproof.com/downloads/woocommerce-plugin, then in your WordPress admin go to Plugins → Add New → Upload Plugin, choose the zip, and activate RoasProof for WooCommerce.
2. Configure it
Open WooCommerce → RoasProof (or Settings under the plugin's row on the Plugins page) and fill in three values, all found in RoasProof under Setup & API keys:
- RoasProof URL — your app URL, e.g.
https://app.roasproof.com. - API key — create one with Create API key and paste it here immediately; it is shown only once.
- Site key — the tracking key of the website this store maps to (the
data-sitevalue from your snippet).
Leave Inject the RoasProof snippet on every page checked unless you already load it yourself through Google Tag Manager or your theme — turning it off without another install source means no visitor identity is ever captured. Leave Send a server-side purchase to RoasProof when an order is paid checked to actually deliver conversions; unchecking it keeps only the browser-side snippet active.
Save, and the settings page confirms Connected. Paid orders will be sent to RoasProof.
How it works
The plugin hooks into checkout to stamp the visitor's identity — the _rp_vid cookie, Meta's _fbp/_fbc, and any recovered click ID — onto the order as it is created. When the order is paid (or moves to processing/completed), the plugin sends a purchase event carrying that identity, the order value, currency and hashed email/phone to your ingest endpoint. Because the identity was already saved on the order, this works even when a payment gateway completes the order through an off-site webhook where no browser cookies are present.
Cookie consent
The plugin supports the WP Consent API, the WordPress standard that consent management plugins (Cookiebot, Complianz, CookieYes and most others) use to signal a visitor's choice. When a compatible consent plugin is active, the RoasProof snippet automatically loads in consent mode: nothing is sent until the visitor grants the Marketing consent category, a grant starts tracking on the spot (including the events queued while the banner was open), and a withdrawal stops it immediately. No configuration is needed — the plugin's Consent management section on its settings page shows which mode your store is in.
If you don't have a consent management plugin active, the snippet loads and tracks by default. The snippet's cookies (_rp_vid and friends) are registered with the WP Consent API, so consent plugins can list them in your cookie policy.
Verify
Place a test order, then check Conversion events in RoasProof for a purchase event from your site — open it to see the payload the plugin sent. From there, delivery, deduplication and platform matching work exactly as described in Verify delivery and troubleshoot failed events.
Not on WooCommerce?
Shopify has a one-click app install. Any other stack sends orders through the events API with one authenticated request.