Archive

Posts Tagged ‘Yahoo’

Search Marketing API GeoTargeting Limitations

May 7th, 2009 Comments off

I have had the ‘priviledge’ of spending a good amount of time with the Yahoo Search Marketing API as of late, and I must say, while having the ability to use an API to connect to a Yahoo Search Marketing account is awesome, I am less then impressed with how Yahoo has implemented many of it’s services and operations.  One topic area that has had my attention recently is working with the TargetingService operations and being able to programmatically update the GeoLocations of a campaign and/or adgroup. Maybe I am taking this ability for granted, but it would definitely be nice to geotarget more than 250 geolocations at once within a campaign/adgroup. Not only that, I w0uld highly suggest to Yahoo, and I have, that this limit be specifically stated in the Yahoo Search Marketing API documentation.  I have checked the release notes, the updateTargetingProfileForCampaign operation notes, and all of the child documentation for that operation. Even when you log into the Yahoo! Marketing Solutions user interface and drill down into the Campaign Settings for a campaign, there is no mention of any sort of limitation on the number of locations you can geotarget.

Downloading and Converting EWS BulkDownload TSV Files

April 28th, 2009 Comments off

For the longest time, I avoided using the BulkDownload service of Yahoo’s Enterprise Web Services (EWS) for managing our daily pay per click (PPC) account. Now this wasn’t because I did not want to use it, I just thought it was was going to be a severe pain to get it implemented. The reasoning for my hesitation in implementing the BulkDownload feature was because I was pretty ignorant to different encodings. Now that my knowledge of encoding types has blossomed over time, I felt I was ready to tackle the project of using and implementing Yahoo’s BulkDownload service in a complete daily account synchronization for avery large PPC account structure.

When using Yahoo’s EWS BulkDownload service, you can request one of two file formats to be returned to you. These two file formats are:

  • EXCEL_XML – an Excel 2003 XML format
  • TSV (tab seperated value)

Here is the trickey part: the EXCEL_XML files are UTF-8 encoded and the TSV files are returned in UTF-16LE encoding.  Normally, I like to use comma seperated value (CSV) file formats and use the LOAD DATA [LOCAL] INFILE  syntax of MySQL. (One can just as easily use TSV file formats with the LOAD DATA [LOCAL] INFILE syntax. You just need to make sure you specify

FIELDS TERMINATED BY '\t'

instead of

FIELDS TERMINATED BY ','

in your SQL statement.) Bacause of the TSV file coming in as UTF-16LE encoded, simply grabbing the tab seperated value file and loading it right into MySQL would not work. My solution would just involved a couple extra steps; once I retrieved the account structure file from Yahoo, I would simply loop back through the file and convert the data of the file from ‘utf-16′ to ‘ascii’ using PHPs iconv() function. This can obviously be done in multiple ways, but here would be one way to accomplish the task:

while (!feof($handleIn))
 {
    $content = iconv('utf-16', 'ascii', fread($handleIn, 8192));
    fwrite($handleOut,$content);
 }

Once the file has been successfully converted over to ascii, I can then run a LOAD DATA [LOCAL] INFILE to get the TSV file into a MySQL table:

LOAD DATA local INFILE '[file_name]'
INTO TABLE [table_name]
FIELDS TERMINATED BY '\t' optionally ENCLOSED BY '\"' LINES TERMINATED BY '\n'
IGNORE 2 LINES;

The reason for the IGNORE 2 LINES is because the first two lines of TSV file are basically header rows and I consider them to be junk rows.