Coincidentally, I wanted to launch this yesterday but HackerNews was down--<p>I built KillSwitch (http://Killswit.ch) with the busy agency in mind. Many digital agencies don't host the sites they advertise for and this can cause a problem when there is downtime. It's not uncommon for a client website to go down for hours in the middle of the night while traffic is being sent to the site. KillSwitch monitors the site every minute for connectivity and in the event of downtime notifies stakeholders. If the site is not returned to service after a user-adjustable threshold, the AdWords campaign is paused automatically. Upon restoration of connectivity, it's started again.<p>This is the most M of MVP's but I've really enjoyed building it. If you have any feedback, I'd be happy to hear it. Josh@Killswit.ch<p>Stack:
PHP with Laravel 4 (http://laravel.com/)
Bootstrap 3 Dashboard (Gumby on the homepage)
Amazon Web Services
Ubuntu 12.04
Local dev with Vagrant & Virtual box
Deployment with Capistrano
One question for other Adwords users - have you noticed a penalty for putting the campaign in pause mode?<p>Years ago (3+) we used to pause our campaigns during known holiday times - we sell to mostly business-minded users and found that, on Christmas Eve and Christmas Day, we were getting clicks that would never, ever convert (3+ years of data). So we started pausing campaigns during those times. We found that when we re-enabled those campaigns we would get much worse results for as much as two weeks after we re-enabled them.<p>Being that this is HN, I realize that 100 people can't want to argue/disprove/etc (or be "captiuous") but I'm telling you now that we knew that it was due to pausing rather than "external factors". I'd just like to hear from anyone else to see if they had the same experiences.
I'd also be happy to entertain any questions you might have about the solo-founder undertaking and how I arrived at this particular niche of monitoring.