One of the main facilities provided by Gear Supply to their suppliers is cross-platform marketing exposure through advertisements. While on the consumer side, their quality guarantee scheme stands out.
When Matt approached us, he had listed 13 issues from Google Analytics reports that he was pulling his hair around.
Not only did he want these issues to be resolved, but he also wanted a root cause analysis to be done so that the reporting would improve in general and the issues he had not discovered yet would also be resolved.
He was aware that some shortcut approaches he had taken were back firing.
When we examined the list of 13 issues, 2 issues stood out
As we looked at the list of issues, it was clear that many GearSupply would be better off migrating from Universal Google Analytics to GA4.
Our approach to developing solutions was to discover the root causes. For this, we tested intermediate configurations. If a configuration did not solve an issue, we moved one layer deeper to address the problem more holistically.
This made sure the final implemented solutions were fool-proof.
Our first step was to migrate from Universal Analytics to GA4.
This was not only necessary from Google’s support perspective,
but also from a solution implementation perspective.
For example, creating custom dimensions would have been complex and time taking in Universal Analytics but it was a cakewalk in GA4.
Moving to GA4 reduced the testing time also, with the debug view showed us the necessary parameters in order understand if the implementation is correct or requires modifications against configuration changes took effect in real-time.
In the process of migration, we made configuration improvements that solved most of the direct configuration & reporting issues.
To show the “1st page visited URL” by each user in the traffic report, we first tested the impact of increasing session time to 8hrs.
If it worked, it would save changes in the report. Though the landing page showed up in the report in 80% of cases, it wasn’t a fool proof solution.
So, next, we built a custom dimension for “1st page visited URL” in GA4.
We built a JavaScript variable in Google Tag Manager
which recorded the landing page URL.oof solution.
The URL was passed to GA4 as a dimension. The final piece was to resolve the issue of user_id capture.
The site was using a Google Analytics plugin which was misconfigured and giving faulty data.
All 13 issues were resolved. www.gearsupply.com was successfully migrated to GA4 thereby simplifying many reporting aspects. It also helped us reduce the time to deliver the solutions.
The traffic report showed the advertisement “1st page visited URL” against each purchase as a separate dimension. This is a far better reporting structure than what Mendel had expected.
User_id is getting captured and showing up accurately in all the reports.