We LOVE Mint because it’s one of the few solutions we’ve found that shows the specific traffic sources we buy advertising on. Very effective for showing conversions from sites, and for validating ad spending.

(Though Shaun: man, would we love dated tracking that shows us a trend line, like Google Analytics provides, so we could show them a nice, long graph over time, rather than the short bar graphs… but regardless, Mint is the %$#@ for tracking detail. And putting it on a client’s iPhone so they can see real-time results. A big Thanks).

The challenge for us is getting IT departments to install Mint. They often call it a “serious security risk” because of server credentials being shared with the Mint server.

Any response we could use to these folks? I want a killer FAQ’s or retort so we can accelerate the adoption process.

I’m not sure what they mean by this (or if they know what they mean by this). The only information a Mint installation shares with haveamint.com is the installation location, Mint version and activation key. The transmission of this data only occurs during installation and once a week thereafter to check for licensed updates.

All other data (including your database connection info) are stored locally on your servers and never transmitted to a third-party.