Macros supported by Display & Video 360

The following table contains all of the macros supported by Display & Video 360. How to use macros

Limitations

Display & Video 360 macros aren't supported in YouTube ads or data-driven creatives.
Studio dynamic creatives only support macros that are used in key-values in Campaign Manager 360 placements. If you use macros in landing page URLs directly in Studio dynamic creatives, they will not expand.

Ad serving macros

Macro	Description
`${CACHEBUSTER}`	This macro inserts a random number into the ad request URL, which is used to prevent visitors' browsers from serving a cached ad if they revisit a given page.
`${CLICK_URL}` `${CLICK_URL_ENC}` `${CLICK_URL_ENC_ENC}`	These macros will insert the Display & Video 360 click tracking URL. The `ENC` and `ENC_ENC` versions will provide the click tracking URL in encoded and double-encoded formats, respectively. Click tracking URLs contain information specific to each auction. Clicking on a creative will first direct users to the Display & Video 360 ad server (to record the click and associated auction information) before redirecting them to the advertiser's URL. The click tracking macro can be set equal to a creative's click tracking variable or inserted before a creative's internal clickthrough URL. Many times these macros replace a placeholder such as `[CLICK]` or will follow a string such as "&click=" in a URL. Please note these macros won't work with creatives hosted by Display & Video 360.
`${CLICK_POINTROLL}`	This macro inserts the click tracking URL used for PointRoll tags, and is encoded (similar to the `${CLICK_URL_ENC}` macro above).
`${DC_DBM_TOKEN}`	This macro is used to prevent duplicate impressions when using wrapped third-party ad tags with a Campaign Manager 360 tracking ad. The macro is only intended to be used for wrapped third-party ad tags. The tracking campaign’s impression and click events may be dropped if this macro is used in other creative types.
`${ifdbm:your_custom_value}`	This macro is used with Google Merchant Center-powered dynamic creatives to insert a custom, user-specified value to indicate that an ad was served by Display & Video 360. For example, if you inserted the `{ifdbm}` macro in the following URL: http://newurl.com/product.htm?source={ifdyn:GDN}{ifpla:Shp123}{ifdbm:DiD} … then, if a click on the ad is a result of the dynamic ad being served by Display & Video 360, the URL would expand to the following: http://newurl.com/product.htm?source=DiD Additionally, in this example, when clicks are coming from a dynamic ad served on the Google Display Network, the URL would expand to the following: http://newurl.com/product.htm?source=GDN And, when clicks are coming from Shopping ads, the URL would expand to: http://newurl.com/product.htm?source=Shp123

Auction-related macros

Macro	Description
`${ADSTXT_AD_SYSTEM_DOMAIN}`	Returns the domain associated with the ad system. This macro can be used along with `${ADSXT_PUBLISHER_ID}` to verify whether the impression is transacted through an authorized seller. It returns empty string if the inventory does not declare ads.txt.
`${ADSXT_PUBLISHER_ID}`	Returns the publisher ID specified in the bid request. This macro can be used along with `${ADSTXT_AD_SYSTEM_DOMAIN}` to verify whether the impression is transacted through an authorized seller.
`${AUCTION_ID}`	This macro inserts the unique ID of the auction into the URL. This number will be unique each time the macro is loaded. Generally this macros is used to ensure that outgoing requests are unique, thus enabling browsers the ability to issue and receive unique requests and responses on every ad call. Many times the cachebuster or auction ID macro will replace a placeholder such as `[CACHEBUSTER]` or `[TIMESTAMP]`.
`${BUNDLE_ID}`	Returns the platform-specific ID for the app associated with the bid request, if known. For example, on Android, the ID is typically a bundle or package name, such as `com.foo.mygame`. On iOS, it's typically a numeric ID.
`${CAMPAIGN_ID}`	Returns the ID of the line item that served the impression.
`${CREATIVE_ID}`	Returns the ID of the creative served.
`${EXCHANGE_ID}`	Returns the ID of the exchange associated with the bid request.
`${INSERTION_ORDER_ID}`	Returns the ID of the insertion order that served the impression.
`${INVENTORY_SOURCE_EXTERNAL_ID}`	Returns the ID of the deal that the impression was bid on and won.
`${PIXEL_ID_COMMA}` Deprecated July 1, 2020	As of July 1, 2020, this macro is no longer supported and will not expand.
`${PUBLISHER_ID}`	Returns the ID of the exchange associated with the bid request, except for Verizon Media Exchange, for which it returns the ID of the Verizon Media Exchange publisher.
`${SOURCE_URL}`	Returns the URL associated with the bid request, if known.
`${SOURCE_URL_ENC}`	Returns the encoded URL associated with the bid request, if known.
`${UNIVERSAL_SITE_ID}`	Returns the ID of the website associated with the bid request.

TCF macros

The IAB TCF v2.0 supports the use of macros in creative tags to indicate where in the URL the TC string should be inserted and sent onwards, as well as to identify which vendors are present. Advertisers who wish to integrate with the IAB TCF v2.0 should work with their pixel vendors to ensure they properly support the following macros. Learn more

Macro	Description
`${GDPR}`	`0` = traffic from a non-GDPR region, `1`= traffic from a GDPR region.
`${GDPR_CONSENT_xxxxx}`	Where `xxxxx` is the numeric Vendor ID of the vendor receiving the TC string: TC string received in bid request.
`${ADDTL_CONSENT}`	Where `ADDTL_CONSENT` is a dot-separated list of user-consented Google Ad Tech Provider (ATP) IDs.

Was this helpful?

How can we improve it?