Know who replaces each value
Start with attribution and source tokens
These Metricanic macros are the most common in landing and offer URLs:
Use the numbered macro even if you named the token. For example, use
{token1} for Token 1 named Creative.
subid. See Incoming events.
Pass visitor details
Use the macro picker beside a URL to see the supported values. Landing and offer URLs support visitor fields such as:{lp_key} to protect a landing page.
For Direct script, use the generated Traffic URL and tracking script functions to read visit values on your page.
Add event values to outgoing postbacks
Use these macros in outgoing postbacks:{payout} does not always equal the revenue recorded in reports. For example, incoming payout=100 with Revenue set to Fixed amount = 80 records USD 80 revenue but sends 100 through {payout}.
{profit} is the outgoing payout minus event cost. Visit cost is excluded.
Follow Outgoing postbacks to set up the receiving URL.
Send a short token code to a partner
Use{token1:hash} through {token15:hash} when a partner needs a short code for a token value. These macros work in landing, offer and outgoing postback URLs:
- Group a report by that token and click Apply.
- Open Columns and enable Token hashes.
- Find the code beside the token in Flat, or in Hash on a token row in Drill. Check other pages or narrow the report if needed.
{click_id} for conversion attribution.