Skip to main content

Tracking Macros Supported

Turn Every Click and Impression Into Actionable Data

GSM360 Support avatar
Written by GSM360 Support
Updated over a week ago

Overview

Macros are dynamic placeholders that supercharge your tracking by pulling real-time data from every click and impression. Whether it’s Device ID, Publisher ID, country code, or other critical campaign details, macros help you capture the intel that matters.

Drop them into any third-party code (HTML tags, VAST tags, click URLs, pixels) and the GeoSpot Media platform automatically swaps them out with live values - no manual work, just actionable data at scale.

Macros and their Description

When a Macro is implemented, it will be replaced by a value that is generated each time a bid takes place for an impression or click.

The following categories are supported:

  • Mandatory Macro

  • Campaign-specific Macros

  • Publisher-specific Macros

  • User-specific Macros

  • Location-specific Macros

  • SKAdNetwork Macros

  • Other Macros

Mandatory Macro

Name

Description

Example

{CONVERSION_ID}

Mandatory Macro required to track unique bid ID.

This Macro is used to track your App/website events.

2167783501-152389708-822-1-3-130-jdezs-a2c0ee2d104b48a9ba102cd3abe1665c-34-143684-50257831

Campaign-specific Macros

Name

Description

Example

{CAMPAIGN_NAME}

Campaign name that is provided by advertisers during campaign setup

-

{CREATIVE_NAME}

Creative name that is provided by advertisers during creative setup

-

{CAMPAIGN_ID}

Internally generated by GSM360

Numeric digits like 12389

{CREATIVE_ID}

Internally generated by GSM360

Numeric digits like 12389

{CREATIVE_TYPE}

Internally generated by GSM360

video, img, html, native

{ORDER_ID}

Internally generated by GSM360

Numeric digits like 12389

{ADVERTISER_ID}

Internally generated by GSM360

Numeric digits like 12389

Publisher-specific Macros

Name

Description

Example

{EXCHANGE_NAME}

Name of the Exchange that was responsible to show the ad

Amazon

{EXCHANGE_ID}

GSM360's internal exchange ID.

It can be used to form {EXCHANGE_ID}_{APP_ID}, the value of which is used in whitelisting/blacklisting publisher apps.

23

{PUBLISHER_ID}

Exchange-specific alphanumeric ID for publishers

c475b45495a57e2e3a242542a98e249b.

{APP_NAME}

Publisher’s app name that is present in the bid request (including special characters)

{APP_ID}

Exchange-specific unique ID corresponding to the publisher app

3b3614b0d8814fceaad20

{APP_DOMAIN}

The domain of the publisher site/app

vrtcl.com

{APP_BUNDLE}

Publisher app bundle

iOS App Bundle: 234672221

Android App Bundle: com.whatsapp

{APP_NAME_ALPHANUM}

Publisher’s app name after removing all the non-alphanumeric characters

User-specific Macros

Name

Description

Example

{DEVICE_OS_NAME}

Operating System of the user's device

Android or iOS

{DEVICE_OS_VERSION}

Operating System Version of the user's device

10, 14.5

{DEVICE_TYPE}

User device category

phone, tablet

{MANUFACTURER_NAME}

Device Manufacturer’s Name

Samsung

{MODEL_NAME}

Device Model Name

Galaxy M01

{CARRIER_NAME}

Carrier Name of the user's network

Vodafone

{USER_IP}

User's IP Address for the impression or click

45.51.3.76

{USER_AGENT}

User Agent of the user's device (URL encoded)

Mozilla%2F5.0%20 (iPhone%3B%20CPU%20iPhone%20OS%2014_2%20like%20Mac%20OS%20X) %20AppleWebKit%2F605.1.15%20(KHTML%2C%20like%20Gecko)%20Mobile%2F15E148

{DEVICE_ID}

Device 15 digit IMEI number

123456789009876

{DEVICE_RAW_ID}

OS-specific Advertising ID of the device in RAW format (if available in the bid request)

7e9547bd-3459-4ad1-870d-0c40a51f57bc

{DEVICE_SHA1_ID}

OS-specific Advertising ID of the Device in SHA1 format (if available in the bid request)

7b23aeac50a2cc97b7e5c0afdaf1a6045080ba0f

{DEVICE_PLATFORM_ID}

Unique OS-specific Advertising ID of the Device (iOS - IOS_IDFA; Android - GAID).

This Macro might fetch you the Advertising ID in RAW, SHA1 or MD5 format depending on what is received in the bid request.

7e4567bd-3249-4dg1-876d-0c67j78o57df

{DEVICE_LANGUAGE}

Language of the user device.

IN, US

Location-specific Macros

Name

Description

Example

{COUNTRY_CODE}

User's Country Code as defined by ISO-3166-1 alpha 3 standard

USA

(for the United States of America)

{STATE_NAME}

User’s State name

California

{STATE_CODE}

State Code as defined by ISO-3166-2 standard of all countries coded in ISO 3166-1

US-CA

(California state of the United States of America)

{CITY_NAME}

User’s City name

San Francisco

{ZIP_CODE}

User’s Zipcode

94105

(San Francisco Zipcode)

{GPS_LAT}, {GPS_LON}

Latitude and Longitude coordinates of the user's device and Maxmind

GPS_Lat can be 52.521802 and GPS_lon can be 23.898763

{GPS_LAT_BID},

{GPS_LON_BID}

Latitude and Longitude coordinates of the user's device from bid request

Format same as {GPS_LAT}, {GPS_LON}

SKAdNetwork Macros

Name

Description

MMP

{SKAN_CAMPAIGN_ID}

SKAN campaign ID assigned by GeoSpot Media

Kochava, Adjust MMP integrations

{SKAN_NETWORK_ID}

4468km3ulz.skad network for GeoSpot Media Enterprise

Adjust

{SKAN_ADJUST_NETWORK_TOKEN}

xylyea2j143k for GeoSpot Media Enterprise

Adjust

Other Macros

Name

Description

Example

{TIMESTAMP}

Unix TimeStamp of the click or impression served

1,593,561,601

{DNT}

Boolean value for "Do not track" field in the bid request

True or False

{CACHEBUSTER}

Random number in the URL that is used to limit caching

Cachebuster can be 3468392872

{HTML_CLICK_URL}

Macro to be added in your HTML code in the place of your click URL

{CLICK_URL_ESC}

This Macro is added in the advertiser click URL. It is replaced by encoded escaped GSM360 Click URL

-

HTML sample

data-pixelId="OMMB15"

data-ios_idfa="{DEVICE_PLATFORM_ID}"

data-cid="{CAMPAIGN_ID}"

data-app="{APP_NAME_ALPHANUM}"

data-channel="inapp"

data-DNT="{DNT}"

data-ip="{USER_IP}"

data-userAgent="361"

data-ts="{TIMESTAMP}"

data-clickUrl="{HTML_CLICK_URL}">

</script>

Banner / Native sample

Video

Implement the Macros you might need to track in the Client VAST wrapper.


Did this answer your question?