Note: This list is relevant to both the Yandex.Direct → Google Analytics and Yandex.Direct → Google BigQuery pipelines.
Supported parameters:
| Name | Description | Values |
|---|---|---|
{ad_id} |
ID of ad | Number |
{banner_id} |
ID of banner ad | Number |
{addphrases} |
Whether the impression was initiated by related keywords | yes — ad impression according to related keywordno — ad impression according to one of the source keywords |
{campaign_name} |
Ad campaign name | Text up to 60 characters |
{campaign_name_lat} |
Transliterated campaign name. | Latin text, up to 60 characters. Note: This parameter will be processed only if the campaign name in the Yandex.Direct account contains Latin text, numbers and/or special symbols. If it contains any other text (for example, Cyrillic), the parameter won't be processed. |
{campaign_type} |
Campaign type | type1 — Text & Image adstype2 — Ads for Mobile Appstype3 — Dynamic adstype4 — Smart banners |
{campaign_id} |
Ad campaign ID | Number |
{device_type} |
Device type on which impression was made | desktop / mobile / tablet |
{gbid} |
Group ID | Number |
{keyword} |
The keyword for which the ad was displayed (Text & Image Ads or Ads for Mobile Apps) | keyword text without negative keywords |
{phrase_id} |
The ID of the keyword for the Text & Image Ads or Ads for Mobile Apps | Number |
{retargeting_id} |
Audience target ID that links an ad group with a retargeting list or mobile app interests. Supported only if an ad contains AUDIENCE_TARGET or KEYWORD as a CriteriaType. |
Number |
{coef_goal_context_id} |
Bid adjustment ID for the retargeting list | Number |
{match_type} |
Type of match between impression criteria and search query |
|
{adtarget_name} |
Dynamic text ad target | Name of a dynamic text ad target |
{adtarget_id} |
Идентификатор условия нацеливания динамического объявления | Number |
{position_type} |
Ad block type if the ad appeared on a Yandex search results page | premium — premium placementother — block to the right or at the bottomnone — ad was displayed in the ad networks (YAN or ad exchanges) |
{source} |
Placement | Ad network publisher domain (for example, travel.ru) for impressions in ad networks (YAN or ad exchanges)none — for impressions on Yandex search |
{source_type} |
Ad network type | search — search sitecontext — ad network site |
{region_name} |
Name of the region where the ad has been displayed | Name of the region |
{region_id} |
ID of the region where the ad has been displayed | Number |
{param1} |
Custom parameter 1 | |
{param2} |
Custom parameter 2 |
However, Yandex Direct doesn’t provide some parameters via the API:
| Name | Description | Values |
|---|---|---|
{addphrasestext} |
The text of related keyword | keyword text — when serving ads for the related keywordnone if this impression was not triggered by a related keyword |
{creative_id} |
Creative ID from the Ad Builder | Number |
{interest_id} |
ID of a mobile app interest | Number |
{matched_keyword} |
Matched keyword (use with {match_type}) |
Text of a selected keyword, synonym or related keyword |
{position} |
Exact position of an ad within a block. Passes only the position number, which doesn't define the block type where the ad is displayed | position number in a block (for example 1) |
If you use some of those unsupported parameters in UTM-tags you’ll see the parameter names instead of their values, for example: {source} instead of go.mail.ru.
In order to keep matching visits and ad expenses in the Cost Analysis report, move the unsupported parameters from UTM-tags to additional custom GET-parameters and collect them to custom dimensions in Google Analytics:
- Cost data will be available only for UTM-tags values.
- Session data will be available for unsupported parameters (through custom dimensions) and UTM-tags values.
* The {keyword}, {phrase_id} and {retargeting_id} parameters are being supported partially. With all three in one link, the dynamic values of some of these parameters won't be collected. If not having one or two of these parameters is not critical for your campaign, just remove it from the links to get all dynamic values correctly.
0 Comments