Analytics Connection

Hi @Colin W Happy Little Friday! Hope you had a great week so far. 

The current Typeform integration only supports Universal Analytics (UA), but not the new GA4 format or analytics. You can find information about how to create a Universal Analytics (UA) ID for new properties in this Google Analytics help article.

Hopefully this helps, but let us know if you have any other questions. 

Hi @Colin W I’m afraid this isn’t currently on the roadmap, so I would suggest using the workaround provided for the meantime. 

Hi Team,

I’m also having the same issue. If we create a new GA4 account it means we start over again  and need to change our entire tech stack with the new ga4 tracking code which is a huge disadvantage.

Looks like I’m going to have to remove typeform from my my stack in order to correctly track the customer journey online.

Collin, you could find another alternative that will allow you to correctly track and measure 

Hi John.

What’s the turn around time for the other products in your tech stack, when something like this comes out?

Good question, so GA4 released October 2020- other platforms such as webflow and Calendly have native integrations already set up and running and working great. 

Just curious as Typeform has released a lot of technological capability within their tools (including VideoAsk) in the last year, to get the core product improved. 

VideoAsk is a great product as well, but also it needs to integrate with GA4 because in another years time more customers will be moving across and as marketers need to track and measure the customer journey. Integrations is a huge decision when buying and implementing software and often it is used on the sales side to sell. 

Also, if we see your platforms help convert customers it makes the product sticky and makes it more valuable to use and harder to leave. But as customers upgrade to GA4 they now can’t track the effectiveness of Typeform and VideoAsk. 

And given all that they HAVE done and what is still on the roadmap, how big a percentage of your stack is currently represented by Typeform? 

It’s not a question of how big a percentage, but, how big a role does typeform play in customers that use GA to track the customer journey.

I understand the requirements to track the customer journey but am curious about what people have in their stack and ‘the rate of change’/updates/maintenance that is caused by trying to ‘keep up with the joneses’ 

It isn’t “keeping up the joneses” it simply keeping up with what people are using today because when I go to implement a software I first see the features and then how it integrates. If both boxes are ticked then it’s a go ahead, if not I have to keep going until I find the right solution. This is one of those cases and it sucks to be me because I love the TypeForm/VideoAsk product as they are truly amazing tech. 

Also, “I’m afraid this isn’t currently on the roadmap”, which means that it’s not something that the team are considering, so from a marketers perspective it moves them further away from their goal therefore makes it harder to make that buying decision, help their customers and so fourth.

And given all that they HAVE done and what is still on the roadmap. 

Typeform and VideoAsk are two huge products that have shifted the way we can drive more leads and conversions and i’m happy they exist, the team should be very proud of what they have built.  

If you do have resources to put towards building this integration it would great, if not all good, just makes it harder for us the customer

I hope this gives you one persons perspective and I hope this is received as positive feedback. 
 

Thank for your time

Nigel

Always nice to chat tech!

Hi @Jan Schnakenberg I’m afraid our integration doesn’t support GA4. You can read more about this and workarounds for it here. 

Thanks, @Jan Schnakenberg ! This isn’t a feature we support, so I would still suggest using the workaround here to be sure all of your data appears in Google Analytics. 

Hi @sarahnestanalytics This isn’t something we have planned to support, but I would suggest following the workarounds above for the time being. If anything changes, we’ll post an update here.