Axalot
Traffic Sources

Traffic Sources FAQ

Common questions about Axalot Traffic Sources, parameter mapping, macros, campaign URLs, and stream filters.

Console path

Console / Tracker / Sources

Basics

Source

Reusable tracking profile for an ad platform or traffic network.

Parameter name

GET key that appears in the generated campaign URL.

Parameter value

Macro or static value placed into that GET key.

Stream filter

Campaign routing rule that can use mapped source fields.

What does a Traffic Source do?

It defines which source values should be appended to campaign tracking links. When a campaign uses the source, Axalot builds the URL from the campaign domain, track id, and filled source parameter values.

No. Axalot appends only fields with filled values. Empty source values are skipped.

Can I rename GET parameters?

Yes. Each field can use a custom parameter name. If the custom name is empty or default, Axalot uses the default field name.

Axalot field: creative_id
GET parameter name: cid
Value: {creative.id}

This produces a URL parameter like:

?cid={creative.id}

What should I put into sub1-sub10?

Use sub1-sub10 for values that do not fit the named fields. Good examples are buyer-specific IDs, placement labels, funnel names, or custom network dimensions.

Use named fields first: creative_id, ad_campaign_id, keyword, source, utm_*, ext_click_id.

Why is my source-parameter stream filter not matching?

Check these in order:

  1. The campaign uses the expected Traffic Source.
  2. The generated campaign link contains the expected GET key.
  3. The ad platform sends a real value for that key.
  4. The stream filter uses the mapped Axalot field.
  5. The filter value matches the incoming value format.

What is the difference between cost and campaign cost model?

cost is a source value in the URL. The campaign cost model tells reports how spend should be interpreted: CPC, CPM, or CPA.

Use both consistently. A campaign can only report cleanly when source values and cost model describe the same buying model.

Should I create one source for every campaign?

No. Reuse a source when the platform macro contract is the same. Create a new source when the platform, account, buyer, or macro syntax differs.

Can I use static values?

Yes. A source value can be a static value or a platform macro. Static values are useful for fixed labels such as source names, buyer labels, or test markers.

How do I test a source?

  1. Save the source.
  2. Select it on a campaign.
  3. Save the campaign.
  4. Copy the generated link.
  5. Check the query string.
  6. Send a test click with real-looking values.
  7. Confirm reports show the expected source fields.

Save before copying

If you edit a Traffic Source used by a campaign, save the source and then save or refresh the campaign link flow before relying on copied URLs.

Traffic Sources best practices

Recommended Traffic Source setup rules for Axalot: names, parameters, macros, campaign links, filters, and QA.

Source parameters

Campaign-entry query parameters that Axalot accepts from traffic sources.

On this page

Console pathBasicsWhat does a Traffic Source do?Does Axalot add every source field to the campaign link?Can I rename GET parameters?What should I put into sub1-sub10?Why is my source-parameter stream filter not matching?What is the difference between cost and campaign cost model?Should I create one source for every campaign?Can I use static values?How do I test a source?Related pages