ALTER TABLE table_name CHANGE column_name column_name TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;

From now on, when any column value in a row changes, the value in the TIMESTAMP column will automatically update with the CURRENT_TIMESTAMP.

For more information on the TIMESTAMP column type in MySQL, visit http://dev.mysql.com/doc/refman/5.0/en/timestamp.html.

<xml version=”1.0″ encoding=”UTF-8″?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ns1=”https://adcenter.microsoft.com/api/customermanagement”>

<SOAP-ENV:Header>

<ns1:ApplicationToken></ns1:ApplicationToken>

<ns1:DeveloperToken>XXXXXXXX</ns1:DeveloperToken>

<ns1:Username>XXXXXXXXXX</ns1: Username >

<ns1:Password>XXXXXXXXXX</ns1:Password>

<ns1:CustomerAccountId>XXXXXX</ns1:CustomerAccountId>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<ns1:GetAccountsInfoRequest/>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

<s:Envelope xmlns:s=”http://schemas.xmlsoap.org/soap/envelope/”>
<s:Header>
<h:TrackingId xmlns:h=”https://adcenter.microsoft.com/api/customermanagement”>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</h:TrackingId>
</s:Header>
<s:Body>
<GetAccountResponse xmlns=”https://adcenter.microsoft.com/api/customermanagement”>
<Account i:type=”a:AdvertiserAccount” xmlns:a=”https://adcenter.microsoft.com/api/customermanagement/Entities” xmlns:i=”http://www.w3.org/2001/XMLSchema-instance”>
<a:AccountType>Advertiser</a:AccountType>
<a:BillToCustomerId>XXXXXX</a:BillToCustomerId>
<a:CountryCode>US</a:CountryCode>
<a:CurrencyType>USDollar</a:CurrencyType>
<a:FinancialStatus>ClearFinancialStatus</a:FinancialStatus>
<a:Id>XXXX</a:Id>
<a:Language>English</a:Language>
<a:LastModifiedByUserId>XXXXXX</a:LastModifiedByUserId>
<a:LastModifiedTime>2010-10-18T18:51:00.03</a:LastModifiedTime>
<a:Name>XXXXXXX</a:Name>
<a:Number>XXXXXXX</a:Number>
<a:ParentCustomerId>XXXXX</a:ParentCustomerId>
<a:PaymentMethodId>XXXXXXX</a:PaymentMethodId>
<a:PaymentMethodType i:nil=”true”/>
<a:PrimaryUserId>XXXXXXX</a:PrimaryUserId>
<a:Status>Pause</a:Status>
<a:TimeStamp>AAAAAANRv8U=</a:TimeStamp>
<a:TimeZone>EasternTimeUSCanada</a:TimeZone>
<a:AgencyContactName i:nil=”true”/>
<a:AgencyCustomerId i:nil=”true”/>
<a:SalesHouseCustomerId i:nil=”true”/>
</Account>
</GetAccountResponse>
</s:Body>
</s:Envelope>

As you can see, I X’ed out some of the confidential values that are passed back. You may also noticed that some of the element values are passed back as nil.

To see what the production SOAP request for the GetAccount call from the adCenter Customer Management service might look like, click http://shevnock.com/blog/2010/10/msn-adcenter-sample-customermanagement-getaccount-raw-soap/

<?xml version=”1.0″ encoding=”UTF-8″?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ns1=”https://adcenter.microsoft.com/api/customermanagement”>
<SOAP-ENV:Header>
<ns1:ApplicationToken></ns1:ApplicationToken>
<ns1:DeveloperToken>XXXXXXXXXXXXX</ns1:DeveloperToken>
<ns1:UserName>XXXXXXXXXXXXX</ns1:UserName>
<ns1:Password>XXXXXXXXXXXX</ns1:Password>
<ns1:CustomerAccountId>XXXXXXXXX</ns1:CustomerAccountId>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:GetAccountRequest>
<ns1:AccountId>XXXXXXXX</ns1:AccountId>
</ns1:GetAccountRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

{param1} – at most, this parameter can contain up to 1,022 characters. While this parameter does not have to be used as destination URLs for keywords, using this param1 parameter for keyword destination URLs does make the most sense.

{param2}, {param3} – these two parameters can hold up to 70 characters each. This parameter could be used for ad copy titles, ad copy text, display URLs or destination URLs.

A couple other general notes:

• Even though {param2} and {param3} can hold up to 70 characters each, use caution when using it for ad copy titles and text. For example, even though {param2} can hold up to 70 characters, the expanded ad copy title can only be 25 characters long.
• You can not nest user defined parameters (param1, param2, param3) inside each other. You can nest the adCenter defined parameters inside of the user defined parameters however.

{AdId} – the ad id value of the ad copy that triggered the click. By inserting this into the destination URL of your ad copy or keyword, you can track what ad consumers are clicking on. If you track and store this value on your end, in a MySQL database for example, you can perform your own A/B tests.

{OrderItemId} – this is the keyword that triggered the ad to be displayed (not what the user typed into to search for)

{QueryString} – what the consumer typed into the search. Tracking this value on your end will allow you mash up your own search query reports.

{MatchType} – the match type that was triggered to display your ad copy. Using this in conjunction with the {OrderItemId} and the {QueryString} can be very powerful when determining which keywords and match types are triggering which ad copies.

There are also three other parameters that the advertiser can define (called user defined parameters). These three parameters are aptly named:

{param1}

{param2}

{param3}

These user defined parameters are much like free form fields that can be used by the advertiser for (almost) any purpose they desire. For more information and restrictions on user defined parameters, check out this articles: http://shevnock.com/blog/2010/10/msn-adcenter-parameter-restrictions-param1-param2-param3/

Administration Service -

https://adcenterapi.microsoft.com/Api/Advertiser/v7/Administration/AdministrationService.svc?wsdl

Campaign Management – https://adcenterapi.microsoft.com/Api/Advertiser/v7/CampaignManagement/CampaignManagementService.svc?wsdl

Customer Billing Service -

https://sharedservices.adcenterapi.microsoft.com/Api/Billing/v7/CustomerBillingService.svc?wsdl

Customer Management Service – https://sharedservices.adcenterapi.microsoft.com/Api/CustomerManagement/v7/CustomerManagementService.svc?wsdl

Notification Management Service – https://adcenterapi.microsoft.com/Api/Advertiser/v6/NotificationManagement/NotificationManagement.asmx?wsdl

Reporting Service – https://adcenterapi.microsoft.com/Api/Advertiser/v6/Reporting/ReportingService.svc?wsdl

Secure Data Management Service – https://securityservices.adcenterapi.microsoft.com/Api/SecureDataManagement/v7/SecureDataManagementService.svc?wsdl

As mentioned above, these are the Web Service Addresses for the production version of the MSN adCenter API version 7. The sandbox addresses are slightly different which will be posted shortly.

For more detailed information about these web service addresses for the adCenter API v7, following this link:

http://msdn.microsoft.com/en-US/library/dd796925.aspx

Accounts per Customer – 6

Account Campaigns – 10,000

Campaign AdGroups – 10,000

AdGroup Ads – 20

Account Keywords – 100,000

AdGroup Keywords – 10,000

You can find more MSN adcenter account limitations here: Entity Limits in Microsoft (MSN) adCenter

REQUEST

<?xml version=”1.0″ encoding=”UTF-8″?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ns1=”https://adwords.google.com/api/adwords/cm/v201003″ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<SOAP-ENV:Header>

<ns1:RequestHeader>

<ns1:authToken>..AUTH_TOKEN…</ns1:authToken>

<ns1:developerToken>…DEVELOPER_TOKEN…</ns1:developerToken>

<ns1:userAgent>..USER_AGENT…</ns1:userAgent>

<ns1:clientEmail>…CLIENT_EMAIL…</ns1:clientEmail>

</ns1:RequestHeader>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<ns1:mutate>

<ns1:operations>

<ns1:operator>ADD</ns1:operator>

<ns1:operand>

<ns1:campaignId>…CAMPAIGN_ID…</ns1:campaignId>

<ns1:name>..ADGROUP_NAME…</ns1:name>

<ns1:status>ENABLED</ns1:status>

<ns1:bids xsi:type=”ns1:ManualCPCAdGroupBids”>

<ns1:keywordMaxCpc>

<ns1:amount>

<ns1:microAmount>1000000</ns1:microAmount>

</ns1:amount>

</ns1:keywordMaxCpc>

<ns1:keywordContentMaxCpc>

<ns1:amount>

<ns1:microAmount>0</ns1:microAmount>

</ns1:amount>

</ns1:keywordContentMaxCpc>

<ns1:siteMaxCpc>

<ns1:amount>

<ns1:microAmount>0</ns1:microAmount>

</ns1:amount>

</ns1:siteMaxCpc>

</ns1:bids>

</ns1:operand>

</ns1:operations>

</ns1:mutate>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

RESPONSE

<soap:Envelope xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/”>

<soap:Header>

<ResponseHeader xmlns=”https://adwords.google.com/api/adwords/cm/v201003″>

<requestId>…REQUEST_ID…</requestId>

<operations>1</operations>

<responseTime>557</responseTime>

<units>1</units>

</ResponseHeader>

</soap:Header>

<soap:Body>

<mutateResponse xmlns=”https://adwords.google.com/api/adwords/cm/v201003″>

<rval>

<ListReturnValue.Type>AdGroupReturnValue</ListReturnValue.Type>

<value>

<id>…ADGROUP_ID…</id>

<campaignId>…CAMPAIGN_ID….</campaignId>

<campaignName>…CAMPAIGN_NAME…</campaignName>

<name>…ADGROUP_NAME…</name>

<status>ENABLED</status>

<bids xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:type=”ManualCPCAdGroupBids”><AdGroupBids.Type>ManualCPCAdGroupBids</AdGroupBids.Type>

<keywordMaxCpc>

<amount>

<ComparableValue.Type>Money</ComparableValue.Type>

<microAmount>1000000</microAmount>

</amount>

</keywordMaxCpc>

<enhancedCpcEnabled>false</enhancedCpcEnabled>

</bids>

</value>

</rval>

</mutateResponse>

</soap:Body>

</soap:Envelope>

stdClass Object
(
[rval] => stdClass Object
(
[ListReturnValue.Type] => AdGroupReturnValue
[value] => stdClass Object
(
[id] => 9999999999
[campaignId] => 999999999
[campaignName] => CAMPAIGN_NAME
[name] => ADGROUP_NAME
[status] => PAUSED
[bids] => stdClass Object
(
[AdGroupBids.Type] => ManualCPCAdGroupBids
[enhancedCpcEnabled] =>
)

)

)

)