Look, again, I don't want to impede your sales effort, but I basically ask "how is your Porsche different from my Ferrari" and you answered "well, it takes 2 minutes to intuitively start the engine, and also, it has wheels, seats, a gear stick and air conditioning".
I don't think you can set up tracking in two actual minutes with any of the competitors, nor that there is a significant difference with any of them - you still need to write the tracking pixel into your codebase, get it through QA, and so on. How is your implementation different? The tracking pixel is still code provided by Google/you/Webtrekk/Piwik/Heap/KissMetrics/etc. and it will still require putting into the codebase. An old team member recently admitted to using GA on his personal page because "it's so easy to roll out".
All competitors except IBM and Google Free let you tie requests, visitors, visits and transactions via their respective IDs which easily gives you all of the above if you know how to write basic SQL. All track the (single-r [1]) referer (ok, just nitpicking here), just as your server logs do, all track ads via the equivalent to UTM parameters or GCID, all track metadata such as the browser and device fingerprint which you can use for further identification, all track logins, add to mailing list requests, and whatever else you can dream of because at the end of the day it's just a request to a server and you can put whatever you want in it.
Attribution wise, it's a matter of having the code at hand. Having done this many times now, I can just rewrite the queries from memory once I put the data in the right format. Admittedly, it will take me half an hour rather than 2 minutes. But most clients are happy with that; it means you can run 40 parallel attribution models if you like, and include backend information such as discounts.
I don't think you can set up tracking in two actual minutes with any of the competitors, nor that there is a significant difference with any of them - you still need to write the tracking pixel into your codebase, get it through QA, and so on. How is your implementation different? The tracking pixel is still code provided by Google/you/Webtrekk/Piwik/Heap/KissMetrics/etc. and it will still require putting into the codebase. An old team member recently admitted to using GA on his personal page because "it's so easy to roll out".
All competitors except IBM and Google Free let you tie requests, visitors, visits and transactions via their respective IDs which easily gives you all of the above if you know how to write basic SQL. All track the (single-r [1]) referer (ok, just nitpicking here), just as your server logs do, all track ads via the equivalent to UTM parameters or GCID, all track metadata such as the browser and device fingerprint which you can use for further identification, all track logins, add to mailing list requests, and whatever else you can dream of because at the end of the day it's just a request to a server and you can put whatever you want in it.
Attribution wise, it's a matter of having the code at hand. Having done this many times now, I can just rewrite the queries from memory once I put the data in the right format. Admittedly, it will take me half an hour rather than 2 minutes. But most clients are happy with that; it means you can run 40 parallel attribution models if you like, and include backend information such as discounts.
So once again: what is your USP?
[1] http://en.wikipedia.org/wiki/HTTP_referer#Etymology