615-745-3094 info@workmedia.net

Today we will continue with our series of posts chronicling the development of our proprietary Google AdWords management application.

One thing that’s a little unwieldy about using the Google AdWords API via its various Web Services is that every time a Web Service is called, you have to pass in a number of variables, such as the account email and password, the client email, and the developer and application tokens. And it’s not as simple as setting properties of an object to these values. The values have to be set as arrays, so I have to create a variable to hold each value, then pass that value into a single element array, etc. etc. This can result in a lot of code just that doesn’t really DO anything. To get around this, all of the code that actually involves using the Web Services is placed in separate classes that my web user controls call.

Which brings us to another key development strategy, which is breaking major chunks of user interface and functionality into their own web user controls. This way, those same elements can be easily reused on other web pages. It takes more time early in the development process to set things up this way, but it will save us a lot of time down the road.

One thing that seems odd about the way the Google AdWords API works is that it has a service called Criterion Service that is used to do things like add or remove keywords or web sites from a campaign, or add new keywords. To me, it seems like it would make more sense for there to be a function provided by the Ad Group Web Service that would return the keywords for a particular ad group. A lot of the AdWords API functionality seems counter-intuitive.

We have quite a few working components of the system, so this week we will probably begin tying everything together into a cohesive unit. This is going to be exciting.

If there is anything we can do to help you manage your paid search or natural search campaigns, feel free to contact us at 888-299-4837 or email Info@WorkMedia.net.