I know that this is not a Tessitura analytics quesiton, but I am hoping someone out there may be grappling with a similar issue with Google Analytics (GA4).
I see a majority of our $ conversions on traffic that has a Session default channel group of "Unassigned" and a Session source/medium of "not set" (but if I change to First Session source/medium it is identified as "direct/none"
Both our main website and TNEW site are housed in one GA4 ID, so while I am seeing some small amount of conversions that I can tie to a TNEW page, I am wondering if there is something going on to cause the majority of conversions to come through without the proper tracking. It may not be related to TNEW at all, but it is really suspicious given the monetary tie.
Obviously I am trying to identify the traffic that is resulting in the majority of transactions on TNEW. I have already submitted a support ticket to make sure that the Measurement ID settings are correct in GA4 per these instructions.
And it appears that other tracking of email, paid ads, social, etc. are working. So I am stumped as to where all of the revenue is coming from.
I have read as much as possible online and basically all I can find is that Unassigned and Not Set appear when google is not being sent the UTM parameters is needs.
If anyone has any thoughts or is experiencing similar issues, please let me know. Thanks in advance!
I will cross post in the Reporting and Analytics forum too.
Tessitura looked into my support ticket and they believe that there is a defect that is impacting how data is transfered. Essentially, they think that the traffic gets tracked coming onto TNEW (which we do see) but then the ID gets switched when a user checks out by either logging in as a member or using Guest checkout. Therefore, I can see traffic coming in, and I can see sales conversions, but they are not connected to the same user. So I cannot determine where my conversion traffic is coming from. I have been told they are continuing to research and troubleshoot and that hopefully, there will be a fix in an upcoming version update.