The ClickFlare integration enables you to send conversion data from CallGrid to ClickFlare for accurate attribution tracking. When a qualifying call event occurs in CallGrid, a postback is automatically sent to ClickFlare, closing the attribution loop and enabling accurate campaign optimization.
Prerequisites
Before setting up this integration, ensure you have:
- An active ClickFlare account
- Your ClickFlare tracking domain (e.g., mylandingpage.com)
- The click ID parameter name used in your ClickFlare campaigns (typically "clickid")
- Understanding of which conversion events you want to track
Configuration Steps
Step 1: Capture the ClickFlare Click ID
Before CallGrid can send conversions back to ClickFlare, you need to capture the ClickFlare click ID when visitors arrive at your landing page.
Landing Page Setup:
Ensure your CallGrid DNI (Dynamic Number Insertion) script is configured to capture the ClickFlare click ID parameter by ensuring the parameter is added as a Tag on your Tags page.
Pro Tip: Use the “Media Buying” tags template on the Integrations->Tags page to speed run your tag setup and automatically track the most commonly used tracking parameters.
Important: The parameter name must match what you configure in the ClickFlare template (default is "clickid").
Step 2: Configure CallGrid Webhook
Option A: Using Template Mode (Recommended)

- Navigate to Webhooks in the left navigation
- Click + New Webhook
- Enable Template Mode (toggle on)
- Under "Filter by Template Type," select Conversion Pixel
- Select ClickFlare from the template dropdown
Configure Template Variables:
- Enter a Name for your webhook (e.g., "ClickFlare Conversions")
- Select the Event that should trigger the conversion (e.g., "Call Ended" or "Call Paid")
- Click Save Webhook
Option B: Manual Configuration (Advanced)
If you need more control over the webhook configuration:
- Navigate to Webhooks in the left navigation
- Click + New Webhook
- Disable Template Mode (toggle off)
- Configure the following:

Replace:
- YOUR_CLICKFLARE_DOMAIN with your ClickFlare tracking domain
- YOUR_EVENT_NAME with your custom conversion event name
Testing Your Integration
Step 1: Use the Webhook Testing Tool

After saving your webhook, CallGrid provides a testing interface:
- Fill in test values for each variable:
- tag:clickid - Enter a test click ID from ClickFlare
- tag:CallPayout - Enter a test payout amount (e.g., 25.00)
- tag:CallId - Enter a unique test ID
- tag:InboundNumber - Enter a test phone number
- Click Run Webhook to send a test postback
- Check ClickFlare to verify the conversion was recorded
Step 2: Live Traffic Validation
- Generate a test click through your ClickFlare campaign
- Place a test call to your tracking number
- Verify the conversion appears in ClickFlare with correct attribution
Event Selection Guide
Choose the appropriate CallGrid event based on your conversion criteria:
Call Inbound
Track calls the moment the inbound call is received
Call Paid
Track only calls that met payout criteria
Call Answered
Track when caller connects to a buyer
Pro Tip: For most performance marketing use cases, "Call Paid" is recommended as it only fires when a call meets your defined conversion criteria.
Adding Filters
To send conversions only for specific sources or campaigns:

- Click Add Filter at the bottom of the webhook configuration
- Select a filter condition (e.g., "Source Name Equals")
- Choose the specific source from the dropdown
- Click Save Webhook
This ensures ClickFlare only receives conversion data for the relevant traffic.
Troubleshooting
Click ID Not Capturing
Symptom: Click IDs not appearing in CallGrid call records
Solutions:
- Verify your the clickid parameter is a Tag on your Tags page.
- Ensure the parameter name matches exactly (case-sensitive)
- Check that ClickFlare is passing the click ID in the landing page URL
Conversions Not Appearing in ClickFlare
Symptom: Webhook fires but conversions don't show in ClickFlare
Solutions:
- Verify your ClickFlare domain is correct
- Ensure the click ID value matches a valid click in ClickFlare
- Check that the conversion event name matches your ClickFlare configuration
- Review CallGrid webhook logs for error responses
Duplicate Conversions
Symptom: Same conversion appearing multiple times in ClickFlare
Solutions:
- Ensure the txid parameter is mapped to [[tag:CallId]]
- ClickFlare uses the transaction ID to deduplicate conversions
Revenue Not Matching
Symptom: Payout values differ between platforms
Solutions:
- Verify [[tag:CallPayout]] is correctly mapped to the payout parameter
- Check that revenue is calculated at the time the webhook fires
- Ensure currency formats match between platforms
Best Practices
- Always use transaction IDs - Include the txid parameter to prevent duplicate conversion tracking
- Test before going live - Use CallGrid's webhook testing tool before routing live traffic
- Match domains - Ensure your CallGrid webhook domain matches your ClickFlare tracking domain
- Filter by source - Add source filters if you're only using ClickFlare for specific traffic sources
- Monitor regularly - Compare conversion counts between CallGrid and ClickFlare weekly to catch discrepancies early
Related Articles
Continue exploring with these related insights
CallGrid Bid API - Advanced RTB Integration Guide
The CallGrid Bid API allows custom platforms and developers to send real-time bid requests to CallGrid campaigns.
Read ArticlePosting Bids from CallGrid to CallGrid using RTB
This guide will walk you through setting up your CallGrid campaign to send bid requests to another CallGrid customer.
Read ArticleCall Recording Best Practices
Call recording laws vary by state. Some states require only your consent, while others require everyone's consent (all-party consent).
Read ArticleGetting Started with CallGrid
Welcome to CallGrid! This guide will walk you through your first steps to get your account up and running quickly.
Read ArticleAuthor
CallGrid Team
Article Info
Categories
Topics