ConfigurationAdvanced Settings

Advanced Settings

The Advanced tab holds event bridges and inbound webhooks. Proxy and Google Signals settings live in other places.

The Advanced tab holds two things: Event Bridges and Inbound Webhooks. Everything on it can break tracking for the whole domain if you get it wrong, which is why the tab opens with a warning banner.

Analytics proxy settings and Google Signals are not on this tab. See Where proxy settings live and Google Signals below.

Accessing Advanced Settings

  1. Go to Configuration in the sidebar
  2. Select your domain
  3. Click the Advanced tab

Event Bridges

CleanClicks can receive events from iframe-based platforms (scheduling tools, booking widgets, embedded forms) through the browser's postMessage API. The bridge captures those events and routes them through CleanClicks.

Turn it on with Enable event bridges. When it's on, the tab shows the two things a bridge needs:

  • Allowed Origins: the origins a bridge will accept messages from
  • Event Mappings: a table of Source Event to Target Event, so the third-party event name becomes a CleanClicks event name

Click Save Event Bridges to apply a change.

Inbound Webhooks

The tab shows your inbound webhook URL:

https://cleanclicks.yourdomain.com/__cc/inbound

POST to it to send events from external systems (CRMs, backend pipelines, automation platforms). Expand Payload format & example curl command for the field list and a copy-ready curl call. The event field is required; value, currency, email, phone, orderId, sessionId, and a free-form properties object are optional.

Authentication uses an inbound integration key in the X-CC-API-Key header. Create and revoke those keys in the Inbound keys tab, not here. See Inbound Integration Keys and Inbound Webhooks.

Where proxy settings live

The first-party analytics proxy routes analytics requests through your CleanClicks subdomain instead of a third-party host. Its controls are on the platform you installed, not in the Advanced tab.

WordPress. The plugin's Analytics Proxies section holds the proxy controls:

  • GA4 First-Party Proxy: on by default. Skips itself automatically when that measurement ID is already firing on your site, to avoid double-counting.
  • GA4 Measurement ID: leave blank. It's pulled from your CleanClicks dashboard. Fill it only to override.
  • Usermaven Proxy
  • Plerdy Proxy

Shopify. GA4 first-party mode is under Configuration > Ecommerce > GA4 First-Party Mode (Signal and Clarity). It needs a theme snippet in theme.liquid; the Setup steps panel there has the exact steps.

A proxy only covers the browser request path. Server-side delivery to a vendor still needs that vendor configured under Configuration > Vendors for the same domain.

Google Signals

Google Signals is off by default. The only place to turn it on is the Turn on Google Signals checkbox in the GA4 connection flow during onboarding.

Our recommendation is to leave it off. Demographics data only comes from visitors signed into Google with Ads Personalization on, which is a fraction of your traffic, and turning it on may cause Google to hide report rows for small audience segments (thresholding). It does not affect your Google Ads results, because CleanClicks sends conversions to Google Ads directly.

UTM Attribution

CleanClicks captures UTM parameters from visitor URLs automatically. There is no toggle:

  • utm_source
  • utm_medium
  • utm_campaign
  • utm_term
  • utm_content

They are stored in first-party browser storage on your own domain and attached to conversion events.

For best results with Google Ads attribution, we recommend setting a Final URL suffix at the account level in Google Ads:

utm_source=google&utm_medium=cpc&utm_campaign={campaignname}&utm_term={keyword}&utm_content={creative}&matchtype={matchtype}&network={network}&device={device}&ad_id={creative}

Set this in Google Ads: Admin > Account Settings > Tracking > Final URL suffix.

Every ad click then arrives with UTM parameters that CleanClicks, your analytics platforms, and your conversion tracking can all use for attribution.

Data Retention

Conversion records are retained for 90 days. Session identification data follows the same 90-day period. After that they expire automatically.

Next: Inbound Integration Keys

Was this page helpful?