Subscribe to our RSS Feeds

Welcome to Home of Microsoft Updates and News!

Do you want all updates from Microsoft, MSN, and Windows? this is your blog. We gathered all posts from original sources for you in one place!

KEY FEATURES & CHANGES IN REPORTING API V6 FROM API V51

Add comments

With the recover of adCenter API v6, you have introduced the little pass facilities similar to brand brand brand brand brand new inform types, bulk inform era etc. This post highlights these brand brand brand brand brand new facilities as good as the little differences from the adCenter API v51.

Bulk Report Generation:

In adCenter API v6, you have been introducing two brand brand brand brand brand new facilities in the Reporting Service to promote the bulk download of reports. Before API v6, you limited the user to job the extent of 10 adCenter accounts in the single call. With API v6, the extent is increasing to 300 for accounts per call. Additionally, with the API v6 you have been introducing the idea of nothing accounts, where if the AccountIds component is NULL, all accounts have been returned for all business which have been purebred to the comment which is creation the call. Hence SMB resellers have been potentially not compulsory to have mixed calls in sequence to collect their stating data. Instead, they can make make use of of NULL Account Ids to get inform interpretation for all customers.

Here is the collection distance of opposite fields inside of range object:

Type

Size

Description

Maximum allowed  Accounts for BudgetSummaryReport

50

Only current for Budget Summary Report.

Max Accounts for any alternative reports

300

Valid for all alternative reports where Accounts is authorised in inform scope, solely Budget Summary.

Maximum authorised campaigns

300

Valid for reports where Campaigns is authorised in inform scope.

Maximum authorised Ad Group

300

Valid for reports where Ad Groups is authorised in inform scope.

Maximum authorised Behavioral filter

300

Valid for Behavioral Target as well as Behavioral Performance Report.

Maximum authorised Site filter

300

Valid for Site Bidding Performance Report.

Recommendation: We inspire API users to make make use of of comment extent of 300, instead of creation particular API calls. SMB Resellers if you have some-more than 10K account, check with us prior to regulating Null AccountIds.

New Reports:

We have combined await for 4 brand brand brand brand brand new inform types. Users can right away question the adCenter stating API for these one some-more reports:

Rich Media Ad Type:

We have combined await for Rich Media as the brand brand brand brand brand new Ad Type. The Ad Type worth set is used as the set of flags. You can mix the values around the OR user when environment an component of the AdTypeReportFilter interpretation type.

Ability to lapse primogenitor ids for any report:

For e.g. with the AdGroupPerformanceReport, you will lapse Parent Campaign ID for the compared Ad Group ID. This is loyal for all reports.

Error Codes:

With API v6, you have combined fibre blunder codes to all of the blunder types. This includes both OperationError as well as BatchError interpretation types.

ProductName column:

ProductName mainstay is deprecated from all the API reports.

Changes to Error handling:

With API v6, all authentication as well as share failures will be returned as an intent sort FaultException<AdApiFaultDetail>, whilst any alternative user or complement blunder will be returned as FaultException<ApiFaultDetail>. All adCenter API-enabled business should locate both of these blunder sorts in their application. In adCenter API v5.1, you regularly returned FaultException of sort ApiFaultDetail.

New API names:

In sequence for us to have attention relation as well as coherence inside of the Ad Platform, you have renamed the APIs. Please demeanour during the MSDN Documentation as well as generated WSDLs for the some-more in abyss explanation.

Old API Name

New API Name

QueueReport

SubmitGenerateReport

GetReportStatus

PollGenerateReport

 

Microsoft AdCenter May 28th 2009

Leave a Reply

Spam Protection by WP-SpamFree