Continuing questions on customer ID issues in adCenter API
- Jeff Dillon wrote this great post on how to address issues with CustomerID in the API SOAP header. We heard today that this continues to be a frequent driver of e-mail to our support team.
Check out Jeff's post if you're encountering these issues and let us know if you have more questions.
http://community.microsoftadvertising.com/blogs/api/archive/2009/09/29/information-on-customerid.aspx
We have received several support requests regarding CustomerID that is used in the adCenter API SOAP header. I was hoping to clear up some of the qeustions for those of you upgrading to adCenter API version 6 by our Oct0ber 31 deadline. The CustomerID is only needed for a small number of adCenter API calls, specifically the targeting library calls such as CampaignManagement AddTargetsToLibrary. If you are not using the target libraries, you won't need it, and you can leave the value as null or an empty string, which would produce a SOAP element such as:
<h:CustomerId i:nil="true" xmlns:h="https://adcenter.microsoft.com/v6" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"/>
If you are using the targeting libraries, then you will need to contact support to retrieve your CustomerID. It is possible to obtain your own parent CustomerID via the adCenter Web UI. After you initially log on with your username and password, choose View Source on the web page for the Home tab. Then search for:
campaignsummary-customer=nnnnn
Your CustomerID is the nnnnn value. This format may change in the future.
If you are a reseller and creating customers via the call to CustomerSignUp, then you would want to store the CustomerID that is returned by this method.There is more information on the CustomerID and other identifiers on MSDN at:
Microsoft adCenter Search Advertising Community. This posting is provided "AS IS" with no warranties
