Connections Overview
Manage OAuth and manual token connections that let CleanClicks send conversion data to your ad platforms.
The Connections page manages how CleanClicks authenticates with your ad platforms. This is separate from the vendor configuration (which controls what data is sent). Connections handle the credentials that allow CleanClicks to send data on your behalf.
Accessing Connections
Go to Connections in the sidebar. Select a domain from the domain picker if you have multiple.
Two Connection Methods
CleanClicks supports two ways to connect ad platforms:
One-Click OAuth
Available for Google Ads and Microsoft Ads. Click the Connect button, sign in with your ad platform account, and authorize CleanClicks. Credentials are managed automatically, including token refresh.
Manual Token Entry
Required for Meta (Facebook) and TikTok. You generate an access token in the platform's interface and paste it into CleanClicks.
Connection Status
Each connected platform shows:
| Status | Meaning |
|---|---|
| Connected | Credentials are valid and working |
| Needs Reconnection | Token expired or was revoked. Re-authenticate to restore. |
| Error | Something went wrong. Check the error message for details. |
Platform Limits
| Current plan | Current ad-destination allowance |
|---|---|
| Signal | Any 3 of Google Ads, Meta, TikTok, and Microsoft Ads |
| Clarity | All 4 current ad destinations |
GA4 and Usermaven are analytics connections and do not use an ad-destination slot. LinkedIn is not currently offered as a destination.
Once you reach your plan's ad-destination allowance, the remaining platform cards show a Locked status with an Available on line naming the next tier and its monthly price, plus an upgrade link. Connecting anyway is refused with a message that your plan's connection limit is reached.
Disconnecting a Platform
Click Disconnect on any connected platform. This removes the stored credentials. CleanClicks will stop sending data to that platform immediately.
You can reconnect at any time by going through the OAuth flow or re-entering your token.
Security
All credentials are encrypted at rest using AES-256-GCM encryption with per-customer keys. Tokens are never logged, never exposed in API responses, and automatically refreshed (for OAuth platforms) to maintain connectivity.
Next: Google Ads