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 Signal, Clarity, and Command plans.
Usermaven is an analytics-layer connection (Signal and up) and does not count against your ad-platform connection limit.
Configuration
No OAuth or connection step needed. Configure directly in vendors.
- Go to Configuration > Vendors tab
- Enable Usermaven
- Enter your Workspace API Key and your Server Token
- Save
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)
CleanClicks needs both values — it combines them when sending events to Usermaven's server-side API. With only one of the two, events are skipped.
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 (Signal+)
CleanClicks can proxy Usermaven's client-side tracking script through your first-party subdomain.
Enabling the Proxy
- Go to Configuration > Advanced tab
- Enable Usermaven Proxy
- Save
Benefits:
- Usermaven tracking survives ad blockers
- First-party cookie lifetime (no ITP restrictions)
- Single tracking subdomain for all your analytics
Recommended Usermaven settings
| Setting | Recommended | Why |
|---|---|---|
| API Key + Server Token | Enter both | With only one of the two, events are skipped entirely |
| Workspace domain | Match the domain CleanClicks tracks | Events carry your domain as source; a mismatch orphans them |
| First-party proxy | On (Configuration > Advanced in CleanClicks) | Usermaven's client script survives ad blockers only when served from your subdomain |
| 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 | Verify the proxy is enabled in Configuration > Advanced. Check browser DevTools for Usermaven requests routing through your subdomain. |
Next: Traffic Analytics