Connecting Usermaven
Connect Usermaven to CleanClicks for server-side event delivery and first-party client-side script proxying.
CleanClicks sends conversion and ecommerce events to Usermaven via the server-side API and can proxy Usermaven's client-side tracking through your first-party subdomain.
Plan Requirements
Usermaven is available on the current Signal and Clarity plans. It is an analytics connection and does not use an ad-destination slot.
Configuration
Configure the intended domain in Configuration > Vendors. The manual Usermaven card shows API Key and Tracking Host.
- Select the intended domain and review its Usermaven configuration.
- Enter the API Key and the Tracking Host for that workspace.
- Save the configuration.
- Verify the browser path and a supported server-side event separately.
Finding Your API Key and Server Token
- Log in to Usermaven
- Go to your workspace Settings > API Keys
- Copy both the API Key (workspace key) and the Server Token (used for server-to-server event ingest)
Server-Side Credentials
The Usermaven server-side relay requires both an API Key and a Server Token in the domain configuration. Without either value, that relay reports missing credentials. Tracking Host is not a replacement for Server Token.
The Vendors tab has no Server Token field. To turn on server-side Usermaven delivery, send your Server Token to support, who adds it to your domain configuration. Never paste a Server Token into the Tracking Host field. Then confirm the event in the intended Usermaven workspace.
Server-Side Events
With Usermaven configured, CleanClicks sends ecommerce and conversion events server-side. This populates Usermaven's dashboards with revenue data, product analytics, and conversion metrics.
WordPress sites: the CleanClicks WordPress plugin sends Usermaven events directly. To avoid double-counting, the CleanClicks edge worker skips its own Usermaven dispatch when the WordPress plugin is active and lets the plugin handle it.
WooCommerce / Shopify Dashboards
If you're tracking ecommerce events, Usermaven receives order data with:
- Order totals and revenue
- Product details
- Customer information (hashed)
Note: Usermaven's WooCommerce dashboard widgets require manual setup inside Usermaven. Each widget needs to be configured with the event name, metric source, and aggregation. If you see $0 revenue in Usermaven but events are being sent, the issue is widget configuration, not CleanClicks.
Usermaven First-Party Proxy (WordPress, Signal or Clarity)
A first-party subdomain can reduce dependence on known third-party request paths. Browser rules, blockers, consent choices, CSP, caching, and site configuration can still affect collection.
The Usermaven proxy is a WordPress plugin feature. There is no Usermaven proxy switch on the Configuration > Advanced tab, which holds Event Bridges and Inbound Webhooks only, and the Shopify pixel carries no Usermaven path.
Enabling the Proxy
- In WP Admin, open CleanClicks.
- Expand Advanced settings.
- Under Analytics Proxies, tick Usermaven Proxy ("Inject Usermaven tracking via CleanClicks proxy").
- Save.
- Check the subdomain, consent state, browser request path, intended Usermaven workspace, and one real event.
Recommended Usermaven settings
| Setting | Recommended | Why |
|---|---|---|
| API Key + Server Token | Verify both in the server-side domain configuration | The server-side relay requires both; check the server credential with support if your screen does not expose it |
| Workspace domain | Match the domain CleanClicks tracks | Events carry your domain as source; a mismatch orphans them |
| First-party proxy | WordPress only, in the plugin's Analytics Proxies section | Confirm the subdomain, consent state, browser request path, intended workspace, and one real event |
| Dashboard widgets | Configure per event/metric after first events arrive | Usermaven widgets don't auto-build; $0 revenue with events flowing = widget config, not data |
Session Stitching
CleanClicks automatically stitches sessions between its own tracking and Usermaven. When a server-side conversion event is sent to Usermaven, it includes the visitor's Usermaven anonymous ID so the event joins the correct analytics session.
Troubleshooting
| Issue | Solution |
|---|---|
| Events not in Usermaven | Verify both the API Key and Server Token are entered. Check that Usermaven is enabled in Configuration > Vendors. |
| Revenue shows $0 | Usermaven dashboard widgets need manual configuration. Set up each widget to pull from the correct event and metric field. |
| Proxy not working | Check that Usermaven Proxy is ticked under Analytics Proxies in the WordPress plugin's Advanced settings. Then check browser DevTools for Usermaven requests routing through your subdomain. |
Next: Traffic Analytics