Pass Information from a Traffic Source to ClickFlare
When a user clicks an ad, the traffic source can send valuable data about the visit, such as the campaign ID, placement, and cost. This information is passed to ClickFlare through the campaign URL, allowing for precise tracking and optimization. ClickFlare captures these details and can forward them to an affiliate network if needed.
How It Works
To pass information from a traffic source to ClickFlare, you need to map the traffic source’s parameters to ClickFlare’s tracking tokens. This ensures that ClickFlare correctly captures and processes the incoming data.
Traffic Source Macros/Parameters
Traffic source macros and parameters are captured by ClickFlare and stored in tracking fields (trackingField1 to trackingField20). Users can capture up to 20 traffic source parameters via the campaign URL. To see the captured values, users need to group by the respective tracking field in ClickFlare.
Example: Passing The Ad Placement Id
If you want to track which ad placement generated a click, you need to use the traffic source’s parameter for placement. Refer to the traffic source’s documentation to find the correct parameter name.
For example, if a traffic source uses {placement_id} to identify placements, you would map it to ClickFlare’s {placement} token.
The campaign URL would look like this:
https://your_clickflare_domain.com/cf/r/67aaee743692e20252ed03c3?cost={cost}&placement={placement_id}When a user clicks the ad, the traffic source replaces tokens with real values:
https://your_clickflare_domain.com/cf/r/67aaee743692e20252ed03c3?cost=0.50&placement=xyz123Tracking Parameters in ClickFlare
ClickFlare allows you to track various parameters sent by traffic sources, including:
| Parameter Type | Example Parameter Name | Example Token | Description |
|---|---|---|---|
| Click ID | clickid | {clickid} | Unique identifier for each click. |
| Cost | cost | {cost} | Tracks ad spend dynamically. |
| Placement ID | placement | {placement_id} | Identifies the ad placement. |
| Campaign ID | campaign | {campaign_id} | Tracks which campaign generated the click. |
Custom Variables in Reports
Once mapped, these parameters appear in ClickFlare’s reports, helping you analyze campaign performance. You can group reports by placement ID, campaign ID, or other traffic source data points for better insights.
This grouping will appear based on what the macro is mapped to in ClickFlare’s reporting, labeled as Tracking Field 1 through Tracking Field 20. For example, if the campaign ID is the first mapped macro in the traffic source template, grouping by Tracking Field 1 will show a report of the traffic source’s campaign IDs captured.
Setting Up Traffic Source Parameters in ClickFlare
To configure these parameters in ClickFlare:
- Add a new traffic source or edit an existing one.
- In the Tracking Parameters section, match the traffic source’s parameters with ClickFlare’s tokens.
- Save the configuration
FREQUENTLY ASKED QUESTIONS
Got questions? Find the answers below:
What if my traffic source doesn’t provide certain parameters?
Not all traffic sources support dynamic tokens for every parameter. Check the traffic source’s documentation to see which parameters are available for mapping.
Do I need to manually update my campaign URL for each campaign?
No, ClickFlare automatically appends tracking parameters based on your traffic source setup, so you don’t have to adjust the URL for every campaign.
How can I track costs dynamically?
If your traffic source supports cost tracking, use the {cost} token in your campaign URL. ClickFlare will automatically pull and track the cost data.
How do I view custom variables in reports?
You can group reports by placement ID, campaign ID, or other traffic source data points for better insights. This grouping will appear in ClickFlare’s reporting as Tracking Field 1 through Tracking Field 20, depending on how the macros are mapped in your traffic source setup. For example, if campaign ID is mapped to the first tracking field, grouping by Tracking Field 1 will display the campaign IDs captured from the traffic source.
