Giving marketing teams the ability to test and optimize transactional emails opens up a new customer referral and upgrade channel. Love what these guys are doing.
Not only is transactional email a great referral channel (just look at what Dropbox did), it's also ripe for optimization.
Engagement emails are used by almost every kind of app to facilitate user actions, but by being trapped in source code, the people who care about user experience and metrics can't take action to improve them.
> I can't think of a really good legit reason for wanting a cross-app unique ID.
The use case that's affected the most by this change is that of advertisers who want to track the performance of ads they buy from publishers, which I think is a legitimate need. The fact that the IDFA uniquely identifies an iOS device (unless the user resets it) is a side effect of Apple's implementation of it; all app advertisers really want is the same kind of first-party conversion tracking for their apps that's standard everywhere else on the web.
Agreed - app advertisers are playing a performance marketing game with their install ads. This change is going to make user acquisition more tedious in several ways:
- some networks will become straight CPC, which will be a pain in the ass to arbitrage to a CPI - there will be a lot of campaign monitoring required
- other methods of install attribution simply aren't as reliable. This will affect the eCPMs of in-app advertising that consisted of app-install demand.
Allowing the use of the IDFA by publishers and not by advertisers renders it useless, since it can no longer be used for attribution. I don't think conversion tracking - measuring the performance of ads you bought to promote your app - counts as spying.
Yes, it does. And it allows for shady "install this app to continue"-campaigns to artificially boost downloads of apps so they appear in top sellers - even if nobody is actually using them.
Searching StockTwits for '$WAG' results in relevant tweets about Walgreen Co. [1], whereas searching Twitter for '$WAG' results in tweets containing '$wag' in place of 'swag' [2].
Then what is he complaining about? It looks like his "product" has just as much opportunity as it did before, just the $links are now a different color by default, no?
Renaming your company is a paperwork-intensive process - you need to provide proof to Apple that the new name is registered as a company and owned by you.
Thanks for the link. How does company/organization name work when one doesn't have an LLC or anything else "official"? Perhaps one can just use their name.
We were using a landing page on App.net with default settings, so users on iOS devices were dumped straight to the app store. Users on other devices (including PCs) were taken to our landing page for a presell.
We didn't have the infrastructure to support per-ad conversion/download tracking, hopefully we will for our next big spend.
For backing up files that need to be on Google Docs, I use GDocBackup (http://gs.fhtino.it/gdocbackup) and have it download my Google Docs to a Dropbox folder.
Is it possible that the degradation in performance is due to more developers building more apps and driving more traffic to App Engine as time goes on?
The performance degrades too quickly for this. In two or three months we might be on our old performance level, again. Well, I seriously hope that we'll stay fast this time. Only time will tell.
Fall for what? The temptation to express ideas using common memes? Good luck finding any publication where no writer ever gets lazy and uses cliched forms of expression. (Also, if you're looking for really engineer-friendly technical writing, Wired is probably not the place to turn.)
That's unfortunate, because I assumed it was something nano-related, which sounded much more exciting than... uhh, rubber iPhone covers or whatever this is.
