I'm trying to use manual session control with the Google Analyitics measurement API, and I cannot get it to work. After a bunch of fiddling, as a basic test case I set up a simple test site in analytics, and manually made the following requests to it:
?v=1&t=event&tid= (myid) &cid= (uid1) &ec=SessionTest&ea=TestStart&sc=start
?v=1&t=event&tid= (myid) &cid= (uid1) &ec=SessionTest&ea=TestEnd&sc=end
?v=1&t=event&tid= (myid) &cid= (uid2) &ec=SessionTest&ea=TestStart&sc=start
?v=1&t=event&tid= (myid) &cid= (uid2) &ec=SessionTest&ea=TestEnd&sc=end
Then looking at the analytics and waiting, the sessions in question still just time out after the normal 30 mins, instead of ending with the "sc=end" request. For example, under the "real-time -> events" page about 5 minutes after making the requests I still both of the "users" under the "Active Users" tab, and the page still claims there are "Right now: 2 active users on the site".
Related
how to set an alert for server up/Down in AppDynamics?
I tried to set an alert for whether the server is working or not but I didn't see any policy in AppDynamics. can you help me with that?
Create a Health Rule using the Machine Agent "Availability" metric for a Critical and / or Warning condition (for example check if zero every minute for 5 minutes).
If you want to add "alerting" have a look at setting up a Policy which does Actions (such as emailing alerts), configure this to be triggered by events created by your Health Rule
I have a trouble with Server Side Tagging Consolidation Stream. I am trying to use GA4 Stream to dispatch Universal Analytics data to Google Analytics. So far I managed to send data via 2 different streams - one for GA4 and one for UA and they are working fine. I have to mention also that in both situation I am using GTM4WP plugin by Thomas Geiger. But when I am trying to use GA4 stream to send data also to Universal Analytics it doesn't work as I expected. In Universal Analytics I can see purchase event in "Behaviour > Event" or "Real-time > Events" Tabs but I don't see even once transaction in "Conversion > E-commerce - Overview". I checked outgoing request and it looks like bellow (I skip some parameters) (:
tr=89
t=event
ea=purchase
ec=ecommerce
I have and idea that it doesn't work because t parameter is equal do event, not to transaction but I checked working request (without consolidation) and it also has t=event:
tr=0
ec=Enhanced%20Ecommerce
ea=gtm4wp.orderCompletedEEC
el=%2Fcheckout%2Forder-received%2F213251%2F
pa=purchase
t=event
Wham am I doing wrong here?
my main problem is, that since the 23rd of July the Google Analytics Page Tracking is not working anymore, even though I did not change anything.
I have multiple Websites, which have an integrated questionnaire. If people answer a question, the URL does not change, but somehow (I did not write the questionnaire by myself, therefore I do not know how it is exactly working) Analytics tracked their behaviour as Page-View(with specific URLs e.g. www.url.com/question-5).
I think this is the line of code, which tells Google Analytics, that it shall track the Page-View.
window._mfq.push(["newPageView", "/".concat(M || t)]),
"function" == typeof window.ga && (window.ga("gtm1.set", "dimension1", e),
window.ga("gtm1.set", "page", "/".concat(M || t)),
window.ga("gtm1.send", "pageview")),
Google Analytics is integrated with Google Tag Manager and the Google Analytics Tag is triggered by the build in "Page-view" Trigger.
How is it possible, that it was working with no problems till last week and suddenly it is not anymore (on roughly 10 different Websites). It seems to me, that Google Analytics (or Tag Manager) did an update, but I cannot find any information regarding this.
Do you know, if something has changed in the last week?
Addition:
The Google Analytics Debugger tells me the following:
Executing Google Analytics commands.
>Running command: ga("gtm1.set", "dimension1", 200624)
Executing Google Analytics commands.
>Running command: ga("gtm1.set", "page", "/steps-route-1-1-question")
Executing Google Analytics commands.
>Running command: ga("gtm1.send", "pageview")
Ok, found the problem.
The variable gtm1 is not initialized. The page view is therefore no longer sent to GTM. I don't know exactly why that worked before. Possibly. had the gtm variable, which records the actual page view, the name gtm1 and due to some change on the part of Google this is no longer the case.
Yup this was a Google change. Events are now send using gtag function, see https://developers.google.com/analytics/devguides/collection/gtagjs/events
I configured Firebase Remote Config A/B testing for Android, and we did rollout on at least 10K devices.
For some reason, I see "0 users" in my A/B test after more than 24 hours.
Firebase GMS version is: 11.8.0
Should it show A/B participants in real-time or it's ok to see 0 users after 24 hours?
P.S: We are able to get AB test variants on test devices through Firebase Instance Id, it works well.
The simplest experiment which is running has only app package as a target, with no additional filters. And it shows 0 users as well.
Finally, we found an answer!
Maybe somebody will find it helpful:
For now, it happens (no data in Firebase remote config A/B test experiment) if you have an activation event configured for A/B test experiment.
If you have 2 different experiments, both will fail to get results even if you have "activation event" configured only in 1 of them.
Additionally, remote config will not work as well, you'll be able to get only default values.
We already reported to Google about, so they'll fix it at some point I hope.
Another useful info which is really hard to get:
How long is it ok to see "0 Total Users" in experiment I've just
started?
It takes many hours before you can see any data in your experiment. We were able to see results only after 21 hours after experiment start, so if you configured everything well, don't worry and wait for at least 24 hours. It will show 0 "Total Users" for many hours after the start.
Should I use app versionName or versionCode in "Version" field of
experiment setup?
You should use versionName.
Some useful info from support:
Firebase SDK
Make sure your users have the version of your app with the latest SDK.
Since your experiment is with Remote Config
When activateFetched() is called, all events from that point on will be tagged with the experiment. If you have a goal or activation event that happens before activateFetched(), such as automatic events like first_open, session_start, etc., the experiment setup might be wrong.
Are you using an Activation Event?
Make sure to call fetch() and activateFetched() before the activation event occurs.
Experiment ID of the experiments (if support asks you about)
It's the number at the end of the URL while viewing experiment results.
This debugging log could be useful to get what is going on
Also:
The good way to check if your experiment is working now is to set it to a specific version you didn't publish yet and check logs from remote config with the fresh app install(or erase all app data & restart).
It should show different variant every time you reinstall the app, since your Firebase Instance ID changes after app reinstall/app data erase.
If you see variants change - then A/B test is running well.
In your "build.graddle": don't forget to set the same versionName which you set in experiment setup.
In my case, I was receiving results of A/B testing but suddenly, it stopped to appear. It had continued for 7 days and then results appeared. Firebase Support manager said:
what I suspected here is just a delay in showing the result in the
experiments
Additionally, she said that
With that, I would suggest always using the latest SDK version and
enabling Google Analytics data sharing.
In my case, I used I wasn't using the latest SDK version, but Google Analytics was enabled for "Benchmarking", "Technical Support", "Account Specialists" except for "Google products & services". I believe these settings were enabled by default (the screenshot from Google Analytics):
I am issuing GET requests as defined in the Google Measurement Protocol from our server to record offline conversions.
The following test request (tracking id obfuscated)
https://www.google-analytics.com/debug/collect?v=1&tid=xx&cid=111300&t=transaction&ti=1500000&tr=100
validates against the /debug Endpoint (using Postman)
{
"hitParsingResult": [ {
"valid": true,
"parserMessage": [ ],
"hit": "/debug/collect?v=1\u0026tid=xxu0026cid=111300\u0026t=transaction\u0026ti=1500000\u0026tr=100"
} ],
"parserMessage": [ {
"messageType": "INFO",
"description": "Found 1 hit in the request."
} ]
}
And shows up in the Sales Performance report in Google Analytics when submitted to the production endpoint using PostMan (i.e. without /debug/)
However I can't see any of the actual production data, submitted from the server in the Sales Performance report.
Any ideas?
This is kind of tricky, yes the transaction is valid,but the debuger only check the syntaxis, but your Google Analytics configuration has not enabled that type of hit (t=transaction, That is only for Standart E-commerce). In my test account, I run that hit and this work. In your case, if your account is enhanced e-commerce is being filtered on the processing.
So here is a screeshot of you hit on my test view running on classic ecommerce.
So you have 2 options to fix this, downgrade you e-commerce (not recommendable in all the cases)
Downgrade
If you do want to use that syntaxis, you have to uncheck the enhance e-commerce and that should work in your case. With your hit and with my configuration this works (a new account w/no filter and standard e-commerce enabled)
Attach information
The enhanced ecommerce was designed to be send attached with other hits (on event or pageview mainly).
For example, this hit is a no interaction event and it's valid for receive transaction and the purchase. Use no interaction events avoid fake sessions and allows to you import the data of the transaction without alter metrics as bounce rate.
https://www.google-analytics.com/collect?v=1&t=event&ni=1&ec=Ecommerce&ea=Transaction&cid=2.2&tid=UA-xxxxx-1&ti=T12345&tr=35.43&pa=purchase
There is a data latency with Google analytics. Officially its 24 - 72 hours before data shows up in the standard reports.
From my own experience I can say depending upon how much data there is in your account you can see it as early as 12 - 24 hours.
If the debug end point says its a valid it you can assume its working fine.