Reference

Tracking macros for FroggyAds campaigns.

Tracking macros are placeholders FroggyAds replaces with real values at click time. Here is what each value is for, where to place macros, how to encode them, and how to fix placeholders that do not resolve.

Server to serverSource-level attributionWorks with compatible trackers
Key takeaways

Tracking macros for FroggyAds campaigns. at a glance

What does this page explain about Tracking Macros - Step-by-Step Guide?

Quick answer: Tracking Macros: a practical step-by-step guide for media buyers, with settings, examples and pitfalls. Tracking macros are placeholders FroggyAds replaces with real values at click time. Here is what each value is for, where to place macros, how to encode them, and how to fix placeholders that do not resolve. A tracking macro is a placeholder you add to your destination URL that FroggyAds replaces with a real value at click time. The click-ID macro is the most important one, because it is what postback tracking uses to match a conversion back to its click.

SectionDistinct excerpt from this page
What a tracking macro isInstead of hard-coding a source or creative into every link, you add a macro once and FroggyAds fills in the actual value for each click.
Where macros are placedMacros go into the destination URL or tracker click URL you set on the campaign, usually as query parameters.
Supported dynamic valuesThe table describes the value each macro carries and shows a generic placeholder.

Reference for Tracking Macros - Step-by-Step Guide: FTC guidance on online advertising and marketing.

Editorial review for Tracking Macros - Step-by-Step Guide: , .

  • Planning: What a tracking macro is.
  • Control: Where macros are placed.
  • Decision: Supported dynamic values.

What a tracking macro is

A tracking macro is a placeholder you add to your destination URL that FroggyAds replaces with a real value at click time. Instead of hard-coding a source or creative into every link, you add a macro once and FroggyAds fills in the actual value for each click. That is how a single campaign URL can report which source, creative and visit produced each click and conversion.

Use verified macros only. The placeholder tokens on this page are generic examples that describe the value each macro carries. FroggyAds uses specific macro names in your campaign setup. Copy the exact tokens from your FroggyAds dashboard or from the official guides, including the How to create a Postback URL guide. Do not assume a placeholder name here is the literal macro.

Where macros are placed

Macros go into the destination URL or tracker click URL you set on the campaign, usually as query parameters. When a user clicks, FroggyAds substitutes each macro with its value, and the visitor arrives at a URL that carries those values for your tracker or landing page to read.

Supported dynamic values

FroggyAds can pass a range of dynamic values through macros. The table describes the value each macro carries and shows a generic placeholder. Always confirm the exact token in your dashboard.

Dynamic valuePurposeGeneric placeholder
Click IDUnique ID for the visit, required for postbacks{click_id}
Campaign identifierIdentifies the campaign{campaign_id}
Source identifierIdentifies the traffic source or zone{source_id}
Creative identifierIdentifies the creative or ad{creative_id}
GEOCountry or region of the visit{geo}
DeviceDevice type{device}
Operating systemOS of the visit{os}
BrowserBrowser of the visit{browser}
CarrierMobile carrier where available{carrier}

This list is generic. Your campaign setup shows the exact macros FroggyAds supports and their precise names.

The click-ID macro

The click-ID macro is the most important one, because it is what postback tracking uses to match a conversion back to its click. Pass it into your tracker and store it so you can return it on conversion. See Postback Tracking for the full flow.

Campaign, creative and source identifiers

Campaign, creative and source macros let your tracker break performance down by exactly which campaign, ad and traffic source produced each click. Pairing creative and source data is what makes source-level optimization possible: you can see which creative works on which source and cut the rest.

GEO, device and other dynamic values

GEO, device, OS, browser and carrier macros let you segment performance and tune landing pages by context. For example, you can route mobile visitors to a mobile-optimized page or compare conversion rates by country, all from values carried in the URL.

URL encoding

Any value that may contain spaces or special characters should be URL encoded so the link and your tracker parse it correctly. Most trackers handle standard parameters cleanly, but custom values you append yourself should be encoded to avoid broken links and misread parameters.

https://your-tracker.example/click?cid={click_id}&src={source_id}&cr={creative_id}&geo={geo}

Passing macros into trackers and landing pages

To send values to a tracker, map each macro to the tracker's matching parameter in the campaign click URL. To use a value on your own landing page, read it from the query string after the visitor lands. Keep parameter names consistent so reporting stays clean.

Safe example URL structures

A clean structure keeps one parameter per value, uses lowercase parameter names, and encodes dynamic values. Avoid stuffing multiple values into one parameter, which makes parsing fragile.

https://your-landing.example/offer?froggy_click={click_id}&source={source_id}&creative={creative_id}

Troubleshooting unresolved placeholders

If your tracker logs the literal placeholder text instead of a value, the macro did not resolve. The usual causes are a macro name that does not match what FroggyAds expects, a typo in the braces, or copying a placeholder from a generic example rather than the exact token from your dashboard. Replace it with the verified macro and test one click.

Case sensitivity

Some macro systems treat tokens as case sensitive, so a macro typed in the wrong case may not resolve. Match the exact case shown in your FroggyAds dashboard or official guide rather than retyping from memory.

If a macro cannot be verified, treat it generically: use the value type you need, such as a click-ID macro, and copy the exact current token from your FroggyAds dashboard or the official guide before going live.

Frequently asked questions

Why use tracking macros in a FroggyAds campaign URL?

Tracking macros insert campaign values into a destination URL at delivery time. They help a tracker or landing page connect a visit with the campaign, creative, source or other supported dimension.

Where should a tracking macro be placed?

Place each macro in the destination or tracking URL parameter intended to receive that value. Keep the surrounding parameter name and separators intact so the expanded URL remains valid.

How does a click-ID macro support conversion tracking?

A click-ID macro can pass a unique visit reference into the tracking flow. Store that reference with the conversion event so later reporting can connect the accepted action with its originating click.

Why pass campaign, creative and source identifiers separately?

Separate identifiers let reports distinguish the overall campaign from the message and supply source. That detail is useful when one creative performs differently across placements.

How can GEO and device macros help a tracking review?

Supported GEO and device values can add delivery context to a visit record. Compare them with destination and analytics data carefully because tools may classify locations or devices differently.

When do tracking macro values need URL encoding?

Encode values when reserved characters, spaces or non-ASCII text could change the URL structure. Test the final expanded address because double encoding can be as disruptive as missing encoding.

Why does macro case sensitivity matter?

A macro must match the supported spelling and capitalization expected by the platform. A case mismatch may leave a literal placeholder in the URL instead of inserting the intended value.

What causes a tracking macro to appear as literal text?

Literal macro text can indicate an unsupported token, incorrect case, unsuitable placement or a test that did not pass through live delivery. Check the exact token before changing the whole URL.

How should a tracking macro URL be tested before launch?

Open a controlled test click, inspect the expanded URL and confirm that the receiving tracker stores each value once. Also test redirects, encoding and the final conversion record.

Which privacy rule applies to tracking macro design?

Pass only the identifiers needed for campaign measurement and avoid placing personal data in URL parameters. Document retention and access rules for values that can be linked across systems.

Launch a tracked campaign from $50

Create a free account, set up tracking, and optimize to real conversions with SmartCPC and Adscore and internal traffic-quality controls.