Yandex.Direct API

Related keywords get even simpler
23 June, 05:59

Managing your Related keywords and Additional relevant phrases is now even simpler — as of today, they have combined into one easy-to-use tool:

1. Changes to settings in the Campaigns service for impressions for related keywords in “Text & Image Ads” campaigns:

  • The BudgetPercent parameter in the RelevantKeywords structure supports any integer values from 1 to 100.
  • The Mode parameter in the RelevantKeywords structure is not supported and its value is ignored.
  • The ENABLE_RELATED_KEYWORDS setting in the Settings structure is not supported.

2. The Reports service has the new fields MatchedKeyword, Criterion, and CriterionId.

No comments
news,api5
Data for new Premium Placement positions
20 June, 16:04

Support for new Premium Placement positions has been added to the Bids service. The AuctionBids array, returned via the Bids.get method, now features the element 'P14' (fourth position in Premium Placement) with the minimum bids and click prices for the extra ad. The SearchPrices array for Position="PREMIUMBLOCK" also gives the value 'P14' — the entry price for Premium Placement. Also the 'P14' has been added as the query parameter Position of the Bids.setAuto method.

No comments
news,api5
Regional bid adjustment
3 May, 16:27

The BidModifiers service now supports regional bid adjustments. You can use the BidModifiers.add method (see the RegionalAdjustments array) to add a set of regions and bid coefficients that are applied when displaying ads in these regions on the campaign level.

No comments
news,api5
The KeywordsResearch service
18 April, 19:04

Added the KeywordsResearch service for getting a forecast of impressions for keywords. Use the hasSearchVolume method to generate an approximate forecast of impressions for the specified keywords and regions, broken down by device type.

No comments
news,api5
API 5: Statistics for your whole account, custom reports, and much more
23 March, 18:12

At last, the Reports service has come to the Yandex.Direct API.

You can find a description of the parameters and instructions on how to use them in the technical documentation. Several new report types, from statistics for individual ads to full account summaries, are now available. You can even get statistics for search queries. In addition, CUSTOM_REPORT allows you to choose any combination of fields and criteria to make your own customized report.

Please send any questions or feedback you have through the feedback form.

Good luck with your campaigns!

No comments
news,api5
Changes to minimum payment amount coming on March 22
15 March, 13:01

We“d like to remind you that as of March 22, the minimum payment amount in Yandex.Direct will increase from 300 RUB to 1000 RUB (without VAT). To find out the minimum payment values for other currencies, please consult the table below.

Please note that this change only affects the minimum payment amount when you add funds to your account balance (for example, topping up your shared account, making credit transfers, or transferring funds between campaigns and clients). All other financial values, including your minimum CPC and minimum weekly budget, will remain unchanged.

The introduction of this new threshold can affect applications that perform financial operations using the Yandex.Direct API. Apps often use the minimum payment amount to allocate funds between Yandex.Direct and other advertising systems. Given that the minimum payment amount applies to each one of these operations, it is a good idea to begin preparing your applications for its implementation.

Currency:    New minimum  –  Previous minimum
Russian Ruble 1000 RUB w/o VAT – 300
Ukrainian Hryvnia 250 hryvnia w/o VAT – 80
Belorussian Ruble 30 – 9
Kazakhstani Tenge 5000 tenge w/o VAT – 1300
Turkish Lira 50 lira w/o VAT – 17
US Dollar 15 – 10
Euro 15 – 10
Swiss Francs 15 – 10
Yandex Units 15 with VAT – 10 with VAT

To find more detailed descriptions how to work with financial methods and shared account, please refer to the technical documentation.

No comments
news
The AgencyClients service for agencies
6 March, 18:16

We’ve released the new service for agencies — the AgencyClients service for API version 5. This service allows advertising agencies to manage their clients.

You can use the get method. This method of the AgencyClients service returns a list of advertisers who are agency clients, their parameters, and settings for each advertiser‘s chief representative.

Please note:
For requests to this service:
In the Authorization header, specify the access token you received for the agency representative. Don't specify the Client-Login header. You can find more details about roles of Yandex.Direct users in the documentation.

No comments
news,api5
Targeting by mobile app interests
28 February, 19:23

You can now target mobile app ads by user interests in API version 5:

  • The Dictionaries.get method returns a reference list of mobile app categories to use as interests.
  • Methods of the AudienceTargets service now have the InterestId parameter (ID of an app category interest).
  • Added the InterestsChanged response parameter to the Changes.checkDictionaries method.
No comments
news,api5
Added support for negative keywords
15 February, 15:07

You can now add phrases 2-7 words (separated by spaces) in length to your campaigns and ad groups as negative keywords. Added support for negative keywords:

  • In the AdGroups service — in the NegativeKeywords ad group parameter.
  • In the Campaigns service — in the NegativeKeywords campaign parameter.
The CreateNewWordstatReport and CreateNewForecast (Live) methods now support negative keywords in the Phrases parameter.
No comments
news,api5,api4live
Added support for the “rarely served” status
26 January, 11:13
Added support for the “rarely served” status: the methods AdGroups.get, Keywords.get and Bids.get now have the request parameter ServingStatuses and the response parameter ServingStatus.

The following keyword data is unavailable in groups with the “rarely served” status:

  • StatisticsSearch and StatisticsNetwork in the Keywords.get method.
  • CompetitorsBids, SearchPrices, ContextCoverage, AuctionBids, MinSearchPrice, and CurrentSearchPrice in the Bids.get method.
No comments
news,api5
Upcoming changes to minimum payment amount
19 January, 20:02

In March, the minimum payment amount in Yandex.Direct will increase from 300 RUB to 1000 RUB (without VAT). To find out the minimum payment values for other currencies, please consult the table below.

Please note that this change only affects the minimum payment amount when you add funds to your account balance (for example, topping up your shared account, making credit transfers, or transferring funds between campaigns and clients). All other financial values, including your minimum CPC and minimum weekly budget, will remain unchanged.

The introduction of this new threshold can affect applications that perform financial operations using the Yandex.Direct API. Apps often use the minimum payment amount to allocate funds between Yandex.Direct and other advertising systems. Given that the minimum payment amount applies to each one of these operations, it is a good idea to begin preparing your applications for its implementation.

Currency:    New minimum  –  Previous minimum
Russian Ruble 1000 RUB w/o VAT – 300
Ukrainian Hryvnia 250 hryvnia w/o VAT – 80
Belorussian Ruble 30 – 9
Kazakhstani Tenge 5000 tenge w/o VAT – 1300
Turkish Lira 50 lira w/o VAT – 17
US Dollar 15 – 10
Euro 15 – 10
Swiss Francs 15 – 10
Yandex Units 15 with VAT – 10 with VAT

You will receive a reminder about these changes several weeks before they come into effect.

To find more detailed descriptions how to work with financial methods and shared account, please refer to the technical documentation.

No comments
news
Serving status for ad groups, keywords and bids in Yandex.Direct API
20 December 2016, 16:55

We’d like to let you know about the upcoming changes in our API.

By the end of January we are going to introduce a new Serving Status parameter with ELIGIBLE and RARELY_SERVED values. This Status highlights ad groups and targeting criteria with very low amount of impressions.

Here are details on upcoming changes:

  1. Method get of the AdGroups, Keywords and Bids services will return new “ServingStatus” parameter with ELIGIBLE and RARELY_SERVED values.
  2. Keywords and bids with “ServingStatus” parameter equal to RARELY_SERVED will not have or return null values in the following parameters: StatisticsSearch, StatisticsNetwork, CompetitorsBids, SearchPrices, AuctionsBids, ContextCoverage, MinSearchPrice, CurrentSearchPrice.
  3. The “ContextCoverage” parameter will always return “null” for search-only campaigns or campaigns that have “Separately manage bids on network and on search” option enabled in bid strategy settings.
No comments
news,api5
Expanded use of negative keywords in Yandex.Direct API
6 December 2016, 08:00

Changes are coming to Yandex.Direct that will increase the flexibility of negative keywords. Previously, advertisers used negative keywords to prevent ads from appearing in response to search queries containing specific words, but now they will be able to use phrases 2-7 words in length to filter out users not part of their target audience.

To illustrate, let's say that you advertise a low-cost airline using the keyword (plane tickets). You could avoid showing ads to customers looking for more expensive tickets by adding the phrase (-business class) to your negative keyword list. This is more effective than using individual negative keywords (-business -class) as they would exclude search queries like (plane tickets business trip) or (plane tickets economy class). You'll be able to use phrases as negative keywords on the campaign or ad group level in the usual field.

The Yandex.Direct API will support multi-word negative keywords as well. You'll be able to add up to 7 words (separated by spaces) into the NegativeKeywords parameter of the Campaigns and AdGroups services as elements of an array. The get method will return these negatives too.

Note: These new settings will not affect the negative keywords already in use in your campaigns. After launching a new campaign, the phrase (VIP first class luxury) will function as one single negative keyword. This means that Yandex.Direct will only exclude search queries that contain every one of these words.

Now you can begin to prepare for these changes, and we’ll let you know once they’ve launched. Please stay tuned!

No comments
news,api5
Deprecated API Live 4 methods have been disabled
5 December 2016, 23:22

The following API version Live 4 methods have been disabled:

  • CreateOrUpdateCampaign (Live), GetCampaignsList (Live), GetCampaignsListFilter (Live), GetCampaignsParams (Live), GetCampaignParams (Live), DeleteCampaign (Live), ResumeCampaign (Live), StopCampaign (Live), ArchiveCampaign (Live), UnArchiveCampaign (Live).
  • CreateOrUpdateBanners (Live), GetBanners (Live), DeleteBanners (Live), ModerateBanners (Live), ResumeBanners (Live), StopBanners (Live), ArchiveBanners (Live), UnArchiveBanners (Live).
  • Keyword (Live), GetBannerPhrases (Live), GetBannerPhrasesFilter (Live), SetAutoPrice (Live), UpdatePrices (Live), GetChanges (Live).

In the “Migration guide” you will find all the necessary information on method equivalents and campaign parameters for API version Live 4 and API 5.

No comments
news,api4live
Disabling deprecated methods in API Live 4
25 November 2016, 11:55

As we continue to develop version 5 of the Yandex.Direct API, we are phasing out the previous API versions.

As you know, some of the deprecated methods in version 4 were disabled this summer, and the same methods were restricted to limited use in version Live 4. We are planning to completely disable these methods in the Live 4 version of the API on December 5.

Please see the full list of these API Live 4 methods below:

CreateOrUpdateCampaign (Live), GetCampaignsList (Live), GetCampaignsListFilter (Live), GetCampaignsParams (Live), GetCampaignParams (Live), DeleteCampaign (Live), ResumeCampaign (Live), StopCampaign (Live), ArchiveCampaign (Live), UnArchiveCampaign (Live), CreateOrUpdateBanners (Live), GetBanners (Live), DeleteBanners (Live), ModerateBanners (Live), ResumeBanners (Live), StopBanners (Live), ArchiveBanners (Live), UnArchiveBanners (Live), Keyword (Live), GetBannerPhrases (Live), GetBannerPhrasesFilter (Live), SetAutoPrice (Live), UpdatePrices (Live), GetChanges (Live).

Please note: If you are using the deprecated methods in your applications, you need to transition to version 5 of the API as soon as possible. Otherwise, your applications could lose API access.

See our Migration Guide for information on switching to version 5.

No comments
news,api4live
The Clients service for getting client information
9 November 2016, 17:27

We’ve released the new service for getting client information — the Clients service for API version 5.

You can use the get method. An advertiser's representative can get the advertiser's parameters and personal settings. An agency's representative can get parameters for their client advertiser and the user settings for the username specified in the HTTP Client-Login header.

You can find more details about clients and roles of Yandex.Direct users in the documentation. See output client parameters in the method's documentation.

No comments
news,api5
Switchover from conventional units to payment currency
18 October 2016, 12:34

Account access may be suspended for advertisers using Yandex units who haven't made payments for over a year. In this case, calling API methods results in the error 54, and the web interface doesn't allow access to any operations except switching to a currency.

To continue using the API, you need to switch your account to a payment currency. To do this, click “Switch now” in the Yandex.Direct web interface. For more information about switching to a currency, see the Help for Yandex.Direct: Russian rubles or other currency.

No comments
news
News Digest
17 October 2016, 13:40
  • The reference list of regions has been changed. We recommend calling the GetRegions (Live) method or the get method of the Dictionaries service to get an updated list of regions.
  • The methods for the Ads service have an extended set of possible values for the Action parameter for mobile app ads. The list of the button label: DOWNLOAD — “Download, GET — “Get”, INSTALL — “Install”, MORE — “More”, OPEN — “Open”, UPDATE — “Update”, PLAY — “Play”, BUY_AUTODETECT — “Buy”.
  • In a week, there will be added a restriction for keywords: the maximum length of each word or negative keyword in a keyword is 35 characters.
  • As of October 10, 2016, advertising agencies can only register clients who are using a real currency. Registration of clients who use Yandex units has been disabled. Accordingly, the logic of the CreateNewSubclient (Live) method has changed.
No comments
news,api4live,api5
Coming Soon: Structural Changes to Geotargeting Tree for Ukraine and Baltic Countries
5 October 2016, 18:09

In about a week, the structure of the geotargeting tree in Yandex.Direct will undergo some important changes.

Updates to the geotargeting tree involve changes to the geobase, sent using the get method of the Dictionaries service or the GetRegions method. If your app does not support automatic updates to the geotargeting tree, you’ll have to make these changes manually as soon as the new data become openly available. We will notify you when these updates are ready.

For more information about the changes and new region's IDs, have a look at the documentation.

What’s changing?

1. The region tree for Ukraine will be simplified by removing one nesting level: Center, West, East, South, North.
As a result, the geotargeting tree settings will change from “Ukraine -> East -> Kharkiv Region” to “Ukraine -> Kharkiv Region”.

Please note that statistics linked to this additional nesting level will “jump” one level higher when these changes come into effect. To continue using our example, data for the region “East” will move up to the “Ukraine” level. Statistics of other nesting levels (sublevels) will remain unchanged.

2. Recent official changes to the names of several cities in Ukraine will be reflected in the interface.

3. The region tree for the Baltic countries will also be simplified, removing the “Baltic” nesting level:
As a result, the settings will change from “Europe -> Baltic -> Latvia, Lithuania, Estonia” to “Europe -> Latvia, Lithuania, Estonia”.

4. Romania and Portugal will be added to the geotargeting tree.

Please note when these changes take effect, the parent region ID of some cities in the API will also change. For example, the city of Kharkiv will have “Ukraine” as its ParentID instead of “East” as in the current version.

No comments
news,api4live,api5
API News
4 October 2016, 12:39

In statistics provided by the GetBannersStat (Live) and CreateNewReport (Live) methods, the time range of available data has changed for an ad's average position and the device type. Data is now available beginning from November 1, 2014.

No comments
news,api4live