At that point we instituted a big program to move to Amplitude (which we’ve been fairly happy with, but probably won’t be perfect until we get our own data overlays through eventually getting a data lake etc etc) - now the move BACK to GA … II would never touch GA again or consider it for a new project
No, this is the same migration. This is my point: you weren't actually forced to migrate until now. The migration has been optional up until this announcement, and many people haven't. What your team did 2-3 years ago, the majority of organizations have been putting off. But now they can't anymore.
So they've basically said 'GA is closing unless you want to pay 120k/pa so move to firebase - GA is now Firebase Analytics' to now 'Firebase Analytics is Google Analytics again, but that thing we said you had to do you now have to definitively do?' ?
...and there's been very little movement. We can still create "universal analytics" properties, we still can't do the same stuff in Firebase, and the GA4 "Measurement Protocol" is still in beta.
I think our eventual move is going to be to a non-Google product.
There’s heaps of good ones around now - our shift to amplitude was a good one but I know there are a lot of other really simple and free ones about too
On the website side of things, which is GA's core user-base, Universal Analytics has remained supported up til this announcement.
We're actually not currently using a data lake. We were initially on the startup plan which was fantastic (the ability to do templated reports etc is a big one for us) but currently we couldn't justify the cost of a full subscription at that point (and now we are just making do until we can complete our next round at which point we will re-look at the whole situation)
We love that you have an API and used fivetran to ETL to (for want of something cheap + low BI tool costs) BigQuery where we were hoping to be able to attach Data Studio to it to achieve our objectives.
This may not have been the right approach.
We couldn't spare anyone from our dev team to take the time to work out the transforms/queries required to make it useful in Data Studio so we spent some time contracting the work out, but that fell over because they were on lend from a mate's startup and I think just never moved out of the blocks. Also maybe we were using the incorrect tools.
Essentially we were looking to get a fair proportion of our data out, in order to create data views for our clients on their usage (... platform in bio, but hospital analytics stuff - no patient info, all operational efficiency). This was fulfilled really nicely by Templates but in the reports we now generate (... a bit laborious but using a offshore contractor who takes all the pain out of it) we are also able to put benchmarking averages against their peer hospitals etc in which wasn't something it was immediately obvious we could achieve with Templates. Ultimately we want those individual dashboards available for the Hospitals to view, as well as be able to return things like views per period for their content on our dashboard, which we know we can also achieve through the API
Which is an abstraction that tries to handle old GA use-cases and the Segment/Amplitude style use-cases but does neither well.
This is precisely why they're doing it with urgency though. These rulings are based on Universal Analytics. GA4, along with their Consent Mode (still in beta) is supposed to be designed to work entirely without cookies and IP addresses.
GA's second-biggest moat (behind being free) is its existing install base. It's already in place on approximately every website on the Internet. And no one wants to change analytics vendors, because that breaks history, which is a no-no. You want to know if your visits are up/down vs last month or last year, you literally cannot answer that unless you are using the same tool this years as you were last year.
By forcing a migration to a non-compatible version, Google loses that big advantage. If you're going to lose that anyways, then there's less of a reason to stick with GA. Now you're forcing people to gut-and-replace their existing data collection process, what incentive is there for people to stick with Google? One of the biggest reasons to stay with GA was just killed.
The timing is also exceptionally atrocious. Google is, again, forcing people to expend the effort to rebuild their analytics implementations from scratch. Meanwhile court rulings are coming down on a monthly basis enumerating different ways in which Google Analytics violates GDPR. A lot of companies might just brush off these rulings by simply doing nothing, but now they're being forced to actively invest time and effort into Google Analytics. A lot of them are going to be doing an evaluation against privacy-conscious competitors that simply would not have happened if Google wasn't kicking people of their existing platform.
The GA4 data model is also completely different from the GA Universal data model, which is an impediment to their fourth-biggest moat, the fact that every piece of BI software in the universe has a GA plug-in. Many of those plug-ins work despite not being actively maintained since 2015; the GA4 ecosystem is smaller and will take some time to recover.
(The third-biggest moat is Google Ads integration. I suspect that Google imagines this to be bigger than it really is in practice.)