Ad Platforms Integration & Routing
ClickerVolt's Ad Platforms integration allows you to send conversion data back to your advertising platforms (Google Ads, Facebook/Meta, TikTok, etc.) to optimize your campaigns. This feature supports both server-side tracking (CAPI) and offline conversion imports.
You can configure a default integration that applies to all conversions and events, or use routing rules to customize how specific traffic segments are reported—either to different ad accounts or to different conversion actions within the same account.
Default Integration
The "Default Integration" tab is where you configure the primary ad account for this target. This configuration applies to all traffic unless a routing rule overrides it.
Select the Ad Platform (e.g., Google Ads) from the tabs.
Choose your Ad Account from the dropdown list. (Accounts must be connected in Settings first).
Configure Event Mapping: the logical link between ClickerVolt events and your Ad Platform conversion actions.
For example, you can map the ClickerVolt "Conversion" event to your "Purchase" conversion action in Google Ads.
Routing Rules (Advanced)
Routing rules allow you to customize how conversions and events are reported based on UTM parameters. You can send data to different ad accounts, or map to different conversion actions/pixels within the same account. This is useful for:
Agency setups managing multiple client accounts
Affiliates running traffic from multiple ad accounts to the same offer
Segmenting traffic by campaign or source
To create a rule:
Click "Add New Rule"
Define Conditions: e.g., "utm_source contains agency_a"
Enable the platform(s) you want to fire for this rule
(Optional) Override the Ad Account for this traffic segment, or leave it to use the Default Integration account
Configure event mappings to specify which conversion actions/pixels to use
Rules are processed from top to bottom. The first matching rule will be applied.
Event Mapping
For each integration, you can map specific ClickerVolt events to platform actions:
Main Conversion: Usually mapped to "Purchase" or "Lead"
Events 1-10: Can be mapped to other actions like "Add to Cart", "Begin Checkout", etc.