Source parameters

Source parameters are query parameters on the first campaign-entry link.

https://track.example/TRACK_ID?ext_click_id={fbclid}&sub1={placement}

Axalot stores only the supported parameter names below. Unknown parameters are ignored. The campaign entry does not accept browser attribution fields or internal click ids.

Campaign entry is not attribution collection

Do not pass fbp, fbc, or click_id on the first campaign URL. click_id is created by Axalot. fbp and fbc are collected later from landing, PWA, or flow requests when the browser attribution exists.

Supported parameters

Parameter	What it stores	Example value
`ext_click_id`	External click id from the ad platform.	`{fbclid}`, `{gclid}`, `{clickid}`
`cost`	Click or traffic cost.	`0.15`, `{cost}`
`currency`	Cost currency.	`USD`, `EUR`
`creative_id`	Ad or creative id.	`{ad.id}`, `creative_123`
`ad_campaign_id`	Campaign id from the ad platform.	`{campaign.id}`, `campaign_123`
`source`	Source, site, publisher, placement, or channel.	`facebook`, `{site}`
`keyword`	Keyword or targeting term.	`{keyword}`, `brand_term`
`utm_source`	UTM source.	`facebook`
`utm_medium`	UTM medium.	`cpc`
`utm_campaign`	UTM campaign.	`{campaign.name}`
`utm_term`	UTM term.	`{keyword}`
`utm_content`	UTM content.	`{ad.name}`
`sub1`	Custom slot 1.	`{placement}`
`sub2`	Custom slot 2.	`{adset.id}`
`sub3`	Custom slot 3.	`{campaign.name}`
`sub4`	Custom slot 4.	`{device}`
`sub5`	Custom slot 5.	`{geo}`
`sub6`	Custom slot 6.	`{browser}`
`sub7`	Custom slot 7.	`{os}`
`sub8`	Custom slot 8.	`{placement_type}`
`sub9`	Custom slot 9.	`{bid}`
`sub10`	Custom slot 10.	`{extra}`

Not accepted on campaign entry

Parameter	Why
`click_id`	Internal Axalot id. It is generated by Tracker and cannot be overridden from the campaign URL.
`fbp`	Browser/Facebook attribution value. It is accepted only after landing, PWA, or flow requests can provide it.
`fbc`	Browser/Facebook click attribution value. It is accepted only after landing, PWA, or flow requests can provide it.
Any other name	Not part of the campaign-entry allowlist. Ignored.

Value rules

Parameter	Accepted value
`cost`	Non-negative decimal, up to 6 decimal places. Max: `99999999999999.999999`.
`currency`	Exactly 3 letters. Axalot normalizes it to uppercase.
All other supported parameters	`A-Z`, `a-z`, `0-9`, `_`, `-`; 1-64 characters.

If a value does not match the rule, Axalot ignores that value. If the same parameter is sent more than once, Axalot uses the first valid value.

Correct setup

Put the platform macro in the value. Keep the GET parameter name canonical.

Good	Bad
`ext_click_id={fbclid}`	`fbclid={fbclid}`
`ad_campaign_id={campaign.id}`	`campaign_id={campaign.id}`
`creative_id={ad.id}`	`ad_id={ad.id}`
`sub1={placement}`	`placement={placement}`

Example links

/TRACK_ID?ext_click_id={fbclid}
/TRACK_ID?cost=0.15&currency=USD
/TRACK_ID?creative_id={ad.id}&ad_campaign_id={campaign.id}
/TRACK_ID?utm_source=facebook&utm_medium=cpc&utm_campaign={campaign.name}
/TRACK_ID?sub1={placement}&sub2={adset.id}&sub3={campaign.name}

Quick checklist

Use only the supported parameter names.
Put ad-platform macros in the value, not in the parameter name.
Use ext_click_id for source click ids like {fbclid}, {gclid}, or {clickid}.
Use sub1-sub10 for anything that does not fit a named field.
Do not add fbp, fbc, or click_id to the campaign-entry URL.