HI!

I'm trying to book an image Ad.
I successfully added new LibraryImageAd and then create an order, adgroup and ad objects.
But I can't add a Placement (for AdGroup) because of guaranteed/nonGuaranteed Settings of Placement.

What shall I pass via placementTarget of PlacementGuaranteedSettings? How do I know the ID ?

Aditionnally please check that my booking scenario is right:
1. Add/Locate advertiser account
2. add ImageCreative
3. add LibraryImageAd
4. add an Order
5. add AdGroup
6. add Ad
7. add Placement <<< have a problem here
8. activate an Order


Any help is highly appreciated!
Thanks!!!

I've tried to invoke searchForAccount of AccountService service, but it always returns invalid data (on sandbox):
com.yahoo.marketing.apt.AccountDescriptor
accountID = 4768278156447053234
accountType = Network
companyName = Account-null4768278156447053234

com.yahoo.marketing.apt.AccountDescriptor
accountID = null
accountType = Network
companyName = Account-null-5656444650805239530

com.yahoo.marketing.apt.AccountDescriptor
accountID = null
accountType = Network
companyName = Account-null-6958264449917781382

It is always 3 items (AccountDescriptor) with accountID is null or value, that Placement can't be referenced to.

Could somebody explain me what the following error means:

E3897 Account Id not found. Account ID could not be found. An error occurred while processing your request.

Thanks!

The error occurs at OrderService.activateOrder method invocation

Hi Dmitry,

The sandbox environment provides dummy results when calling AccountService.searchForAccounts.

We are in the process of noting this in the documentation.

Sorry for the inconvenience,
-Mark

sr. technical account manager
APT from Yahoo!

Thanks for info!

But I think that it's better to have some fake network on sandbox for testing purposes.
Today I have to make all tests on production env and increase prod server load.

Hi Dmitry,

Apologies for the inconvenience when working in SBX. The lack of sample data in SBX is something that has been noted and we've passed this along to the Product team for them to consider incorporating into a future build.

Thanks,
APT Technical Solutions Team