Vendors

The Vendors tab in Configuration controls which ad and analytics platforms receive your conversion data. Each vendor can be enabled or disabled independently, and most require platform-specific credentials.

Accessing Vendor Configuration

1. Go to Configuration in the sidebar
2. Select the domain from the domain picker (if you have multiple)
3. Click the Vendors tab

Supported Vendors

Ad Platforms

These count against your plan's ad platform limit.

Analytics Platforms

Use the fields shown for the selected domain and supported connection path. The Usermaven server-side relay also requires an API Key and Server Token in its domain configuration; Tracking Host does not replace that token. If the needed credential is not exposed in your screen, ask support to verify the server-side configuration. Enabling a proxy alone does not configure server-side delivery.

GA4 and Usermaven are included in the current Signal and Clarity analytics layer and do not use an ad-destination slot.

Enabling a Vendor

1. Find the vendor card on the Vendors tab
2. Toggle the vendor on
3. Fill in the required fields
4. Click Save

Sensitive fields (access tokens, API secrets) are masked after saving. You'll see •••••••• instead of the actual value. To update a token, enter a new value and save again.

Platform Limits

GA4 and Usermaven are analytics connections and do not use an ad-destination slot. LinkedIn is not currently offered as a destination.

Beyond that allowance, the extra platform shows a Locked status on the Connections page with an upgrade prompt, and the connection itself is refused with a message that your plan's connection limit is reached.

Disabling a Vendor

Toggle a vendor off to stop sending it data. The credentials are retained, so you can re-enable later without re-entering them.

Vendor-Specific Notes

Google Ads

• Customer ID is the 10-digit Google Ads account number
• Conversion Action resource name is the API resource path for the conversion (format: customers/1234567890/conversionActions/123456789), not the AW-xxx/yyy gtag snippet ID
• Click conversions require a click ID (gclid, wbraid, or gbraid); conversions without one are recorded in CleanClicks but not uploaded to Google Ads
• The Developer Token is managed by CleanClicks; you don't need to provide one

Meta (Facebook)

• Use a System User Access Token, not a personal access token. Generate it in Meta Business Manager > Business Settings > System Users.
• The token needs ads_management and ads_read permissions
• Optionally set a Test Event Code to verify events in Meta's Events Manager before going live

TikTok

• Get your Access Token from TikTok Events Manager > Settings > Generate Access Token
• The Pixel Code is on the same page (format: CXXXXXXXXXXXXXXXXX)

Microsoft Ads

• Requires your Customer ID and Account ID from the Microsoft Ads dashboard
• Both are visible in the top-right of your Microsoft Ads interface

GA4

• Measurement ID is in G-XXXXXXXXXX format (found in GA4 Admin > Data Streams)
• API Secret is generated in GA4 Admin > Data Streams > your stream > Measurement Protocol API secrets

Usermaven

• Manual vendor configuration shows API Key and Tracking Host. The server-side relay separately requires a Server Token. Verify the intended workspace and complete credential configuration before testing delivery. Do not paste a token into the Tracking Host field.

---

Next: Triggers and Events