There are probably some value-adds you can do here, besides convenience for developers. For example, you could save your users money by doing some creative aggregation of data points (assuming these services charge by volume) before sending them off. Or you can try to detect low-value data points and let your users filter them out (like hits from bots). Or you can do sampling so that only 1 out of every x data points goes through. Yeah, in-house developers could code this up too, and it might completely kill the value of the analytics service by not sending all data, but who has the time to investigate these types of things?<p>Also, since switching analytics providers becomes very easy for your users, you can try to leverage this fact and get a kickback from analytics providers that you help convert your users to. You could, theoretically, reduce the friction of moving to another provider to near zero (no development / integration cost, no data-lock in if your users let you store historic logs that you could replay to another provider, etc). That would result in much more competitive pricing from the analytics providers.<p>edit: yeah, these random thoughts mostly apply to the server side stuff. just throwing them out there.