I used Google Calendar Push Notifications.
https://developers.google.com/google-apps/calendar/v3/push
Suddenly, the notification was delayed.
It usually arrives in 0.5 to 2 seconds. But In Delay, arrives in 5 minitues to 1 hour.
It seems to be doing a something check in Google Calendar API.
I want some hints... (Because Any Errors? Any Penalties? Any ...)
Related
I am launching some push notifications campaigns through Firebase. Until last week, those campaigns were populating correctly as App Channel. However, this weekend they started to populate as Desktop.
However, they are only populating 1 or 2 sessions per campaign in total.
There have not being major changes on the Utm tracking. An example of tracking for the last campaigns:
?utm_source=firebase_messaging&utm_medium=ema-push-notifications&utm_campaign=dto20-112022_210820854259&utm_id=dto20-112022
Those campaigns were both set up for iOS and Android.
Do you have any idea of why this could be happening? Or where should continue investigating?
It's the first time I see this.
Thanks!
I’ve been experiencing a discrepancy in terms of page views between GA4 and GA3, both installed through GTM page view event.
I notice that GA4 is much slower to send the collect request compared to GA3, literally takes 3-4 seconds more from my office connection and pc.
I think that this is the main cause of discrepancy between the two.
Is it possible to somehow speed up GA4 tracker?
I remembered Google design this feature.
Here is the reference from a blog post
One thing you might have noticed is the delay it takes for the hit to
be sent. When you load the page, you can see how the browser waits a
few seconds before dispatching the hit to GA. This is because GAv2
batches requests automatically, which, again, is a great feature
upgrade.
Link
GA4 now will send multiple event as one request. But you don't need to worry about this will lost some event if user close the browser suddenly.
Here is the article from Google
Note: When a user's device goes offline (for example, a user loses their internet connection while browsing your mobile app), Google Analytics stores event data on their device and then sends the data once their device is back online. Analytics ignores events that arrive more than 72 hours after the events are triggered.
Link
I am testing a push notification that is related to an event that only has 24 hs of duration. So, I wanted to send a notification with a variant to see the impact and diference. But i dont want to that same notification be sended more than once because if it is sended 24 hs later the event is off and we will be sending a wrong notification.
The message will be send everyday in the usual configuration or only the first day (That it is when it is schedule).
I have this doubt specially because when i see the result console y can see this:
We have a positive number for notification opened on days before the starting date. I DONT want users to see notif after 24 hs. I cant find any documentation regarding this.
How would you send offline events and antidate them of more than 4 hours (which is the limit of the qt param)?
You can use measurement protocol (https://developers.google.com/analytics/devguides/collection/protocol/v1) to send offline events to Google Analytics, but you cannot place them in the past (the moment when the hit arrives in Google Analytics is authentic).
We are trying to send some push notifications using the GCM API to Chrome users. Until 3-4
days back, the delivery rate of the notifications to the end users were
about 60-70%. We have a timeout of 1 day, so people who did not come online
for about a day after the notifications went out, should not get it.
We are seeing that this delivery rate has drastically dropped down to about
10%, with no change on our side. We push messages to GCM and the API
returns successfully, but the messages do not get delivered. Also, a few of
our users in the test pool have mentioned that despite being online(on
Chrome), they did not receive any notifications when they were sent.
Strangely, they did get those notifications after a couple of days(even
after there was a timeout set, of 24 hours).
Does the old GCM API have some problems like the delay and drop in delivery
rates? For example, for a test token, the notification was sent on Dec 1, 09:55 GMT, and delivered on Dec 3, 13:14 GMT.
We are using this endpoint : https://android.googleapis.com/gcm/send
So just to keep it short, it would seem that you are using an old endpoint:
https://android.googleapis.com/gcm/send
And as far as GCM implementation goes, there wasn't any behavior reported like this as of the moment (I've been monitoring the GCM tags so.. yeah..), but you can't really guarantee the success of the request unless you are using the suggested endpoint (seen in the docs):
https://gcm-http.googleapis.com/gcm/send
I suggest to use this moving forward. And since we're also on the subject of using the suggested implementation, you should also have a look into using Firebase Cloud Messaging too. Cheers!