I have just released Keyword Transformer version 1.2.0! In this release, you will find support for the Google AdWords Editor. Both the Professional Edition and the Personal Edition have been upgraded.
If you are an owner of the Personal Edition and have not purchased the Professional Edition, I have sent you an email that contains a link to the download location. If you have not received it, please check your spam folders just in case it may have gone there.
If you are an owner of the Professional Edition, please login to your account at http://products.djt-engineer.co.uk/ to download the updated version. If you do not yet have a password or you have forgotten your password, click on Retrieve Password and enter the email address with which you registered your purchase. You will then be emailed a new random password. If you did not purchase the product under JV Manager and you still have not migrated your account, please contact me for access to your upgrade.
If you are unaware of Google AdWords Editor, it’s a tool that supports offline, rapid editing of your advertising campaigns. It’s in public beta at the moment. You can find it at the following URL:
http://services.google.com/adwordseditor/
Please refer all questions regarding its usage to Google.
If you can think of any further enhancements that you would like to see in a future version of Keyword Transformer, please add comments to this blog post in the usual way.
The following bug has been reported:
When keyword permutations and removed spaces are both selected, any two-word phrase “WordA WordB” will be missing the expected output “WordAWordB”. The facility works for phrases with more than two words. As a workaround, include the two-word phrase “WordB WordA” in the input.
I hope to fix this bug in time for the next release.
The following bug has also been reported:
When using many options together with a long list of input keywords, Keyword Transformer crashes. In actual fact, it does not crash, but as the output list grows, the time required for duplicate detection increases linearly with the number of keywords. Once you get past maybe 2,000 keywords or so, this has a significant effect on the speed of the program.
As a workaround, please either use a smaller number of input keywords when you need to do many types of transform on each keyword, or use the “Write Files” feature to write a single keyword output file for each input file.
I do have a solution for this bug in mind, but it will take a bit of work to implement. I will of course try to fix this bug by the next release, but it’s possible that the fix will have to come later.