ValueTrack reference
Every ValueTrack macro WhichClick recognises, the query key to use in the template and the click column it is stored in.
Updated 2026-09-02
Any of these keys can appear in the tracking template. Values are stored on the click and exposed through GET /api/v1/clicks, the pivot report and the MCP list_clicks tool.
| Macro | Query key | Description | Campaign types | Click column |
|---|---|---|---|---|
{gclid} | gclid | Google click identifier (auto-tagging) | All (limited in Performance Max) | gclid |
{campaignid} | campaignid | Campaign ID | All | campaignExtId |
{adgroupid} | adgroupid | Ad group ID | All | adGroupExtId |
{creative} | creative | Unique ad ID | All | creativeId |
{keyword} | keyword | Matched keyword (blank for DSA / Performance Max) | Search, Display | keyword |
{matchtype} | matchtype | e = exact, p = phrase, b = broad, a = AI Max | Search | matchType |
{network} | network | g = Google Search, s = partners, d = Display, ytv/yts = YouTube | Most | network |
{device} | device | m = mobile, t = tablet, c = computer | All | device |
{placement} | placement | Content site / placement | Display, Video | placement |
{targetid} | targetid | Keyword / audience / product group ID | Most | targetId |
{loc_physical_ms} | loc_physical_ms | Geo ID of the click location | All | locPhysical |
{loc_interest_ms} | loc_interest_ms | Geo ID of the location of interest | All | locInterest |
{adposition} | adposition | Ad position (e.g. 1t2) | Search | adPosition |
{feeditemid} | feeditemid | Legacy asset ID | Not Display | — |
{extensionid} | extensionid | Asset-based extension ID | Not Display | — |
{random} | random | Random number for cache busting | All | — |
{assetgroupid} | assetgroupid | Performance Max asset group | Performance Max | — |
{merchant_id} | merchant_id | Merchant Center ID | Shopping | — |
{product_id} | product_id | Product ID from Merchant Center | Shopping | — |
{product_partition_id} | product_partition_id | Product group ID | Shopping | — |
Google click identifiers#
gclid, gbraid and wbraid are captured from both the tracking template and the landing-page query string. gbraid / wbraid appear for iOS app campaigns where gclid is withheld; the attribution engine matches on whichever is present.
Value normalisation#
| Field | Stored as |
|---|---|
matchtype | e, p, b, a (lower-case, single letter) |
network | g, s, d, ytv, yts, vp, x |
device | m, t, c |
keyword | Trimmed, max 256 chars, empty string → null |
loc_physical_ms, loc_interest_ms | Numeric geo criteria id as string |
Unknown keys are ignored, never stored, and never forwarded to the landing page.
Reporting dimensions#
The pivot report and MCP get_pivot_report accept campaign, network, device, os, country, keyword, matchType, creative and day. Campaign names resolve through campaignid → Campaign.externalId; set the external id on each campaign so ValueTrack clicks group correctly.