Google Analytics Goal Not Recording Accurately - google-analytics

I'm not getting the right results returned for a goal I have set up. The goal says the last 7 days have 92 goal conversions, when it should be 400+.
When a user completes a subscription purchase, they land on a confirmation page. We have several subdomains that the user can be coming from as well as the potential for a reference appended to the URL. So, I have the goal set up as a regular expression like this:
.*/insider/confirm.*
If, for example, the user pays and then is directed to the following page, shouldn't the goal be recorded?
test.com/insider/confirm?ref=2343

As I can't see anything wrong with the regular expression, although very greedy, the goals should be captured with the above example URL and goal setup.
Have you recently set this goal up? A thing with goals are that they aren't historically applicable to your data. They start collecting data from the point where you set it up.
Have you tried using the above regexp in the "All pages"-report under "Behavior"? Enter it into the filter pattern and there you can see exactly what pages your regexp would capture.

Related

How can i visualize a customer journey with tag manager and google data studio?

I have a website where the customer can take a quiz to find the right products. I want to track the customer's journey on the quiz, to see what they choose and where people fall off.
The quiz starts at example.com/start/ and for every step they take, the URL "expand" to e.g. example.com/start/first_step/, next step example.com/start/first_step/second_step etc.
I think I can do it with tag manager, by creating events for each step / URL. But my first issue is, that the events get to long. The other issue is, I cant figure out how to visualize the journey in either Google analytics 4 or Google data studio.
enter image description here
Does any of you have a great idea for how I can do it?
what exactly to you mean saying "the events get to long"? Do you mean the requests payload to the google analytics server?
Generally speaking, I'd recommend the following:
Create a generic event for all quiz steps
Add two parameter for the progress, one containing the steps name an one containing the index (e.g. "quiz_step_str" & "quiz_step_index")
Send the events to GA4
Visualize them using a bar chart. (https://analyticsdemystified.com/google-analytics/step-step-guide-creating-funnels-googles-data-studio/)
Additional information regarding step 2:
The parameter containing the step name can be generated using js and getting the value from the url. Just scrape the corrsponding part from it (e.g. "example.com/start/first_step/" -> "first_step").
For the parameter containing the steps' index, I recommend creating a lookup table.

How to properly use sequences for attribution?

My goal is to see which customers originate from organic search, but convert via a different source later on.
To do this, I defined this segment:
Then, I look at the Source/Medium report, but the results seem off. I expected to see zero revenue in the google/organic row (as the segment should show users where the transaction is specifically not coming from google/organic.
Am I using the right tool for what I'm trying to achieve? And if so, what am I doing wrong?
The conversion path in Google Analytics is a better solution here. You can find it under conversions -> multi-channel funnels -> top conversion paths.
What you're going to see here is all the combinations of channels that have been used to generate a conversion, see the screenshot below.
If you have a bigger website you're probably going to have >10.000 different conversion paths depending on the time period that you select. What you want to realize is how much conversion value and conversion was generated in conversion paths that started with organic, but ended with a different channel. Simply apply the filter below in the report to retrieve that data. Please note that in the standard Google Analytics reports all conversions and conversion value are attributed to the last, non-direct click.
The solution is to add a condition that includes only sessions as described in the second step of the sequence. This will reduce the population from all users that present the pattern in the sequence, to only sessions that matter. See detailed explanation here: https://www.napkyn.com/2017/09/07/quick-google-analytics-trick-use-sequence-segments-to-analyse-behavior-over-multiple-sessions/

Suspiciously high frequencies of certain counts with Google Analytics

I am working with Google Analytics data und during the analysis I saw that I have wierd distribution of visits. For instance, the minimum visits for a page is 89, wich also has the highes freq count in my dataset. Then I have 177 visits for a page with the second highest freq count. I find this pattern every month...
Does anyone know anything about that?
It sounds like you might have some combination of repeated trackers, heavy spam or over-impactful bot traffic.
Repeated trackers an be identified using Realtime reporting: if you click onto the Page Views tag, does each page load trigger only one page view?
Spam can often be identified using the Hostname. Run a custom report looking at Hostnames, and you can see if it's coming from freebuttons.xyz or some equally scummy location.
Finally, bot traffic can be filtered out using an option in the view settings: try setting up a duplicate View with this setting on, and see how different the volumes are.

URL-based Goal doesn't get reached in Google Analytics despite the same URL-based PageView being registered correctly.

I've got a multi-stage online questionnaire form, and I use a _gaq.push(['_trackPageview', '/Form_Stage_XX']) code to register form's stages destinations (the "XX"s stand for actual stage numbers).
I also set up the URL-destination Goals based on pages /Form_Stage_XX (same as in _gaq.push).
Now in the Site content -> Pages report I can see the visits of /Form_Stage_XX registered as expected, but the related Goals won't get reached.
Any ideas why is this?
Many thanks.
Please do check your goals configuration in the Profile Settings - > Goals Page to see if the URL is set to the same as /Form_Stage_XX and also if the Match Type is set to Exact Match. I would also recommend using the Match Type: Regular Expression with .*\Form_Stage_XX as the parameter.
You should be able to see if your goals are beign tracked as expected in the Conversions - > Goals Report.
One more thing is that form goals are usually better tracked as a Funnel Conversion, so you can track the flow from each step and thus visualize where visitors are leaving your form.
You can find more information in this great video lesson, made by Google

Google Analytics Goal Funnel Issues

I am attempting to create goal funnels in GA for dynamic asp.net based pages. The funnel currently looks as follows:
/
/market_home.aspx
/Category.aspx
/product.aspx
/Cart.aspx
/Checkout.aspx
/OrderReview.aspx
/Confirmation.aspx
The market_home, Category and product pages are dynamic and will contain various parameters ie:
/market_home.aspx?id=1
/Category.aspx?id=1
/product.aspx?id=1
I am using regular expression as my match setting (have tried head match as well). I still get two of my market home pages not being captured. It is only 2 out of 18.
I can't seem to figure out why it catches some, but not all of the traffic.
I also am not capturing incoming/outgoing traffic that is not at the start of the funnel. In other words, those visitors being captured in the funnel appear to complete the entire thing from start to finish. There are no visitors dropping out in the middle anywhere, which I can't believe.
The beginning of the URL will not change.
Any ideas what could be wrong?
I've got the same problem, i even asked about it couple days ago: Using regexp in Google Analytics Goal Funnel steps
I beleive the thing is that RegExp don't work properly in funnel steps. My solution for this is generating the same virtual pageview in every dynamically generated page and use it in the funnel. Goog practice is to create a separate profile for it and filter out those virtuals in the main to avoid data distortion.

Resources