Firebase console wrong first open

1,688 views
Skip to first unread message

Bobgoo

unread,
Jan 28, 2017, 2:21:30 PM1/28/17
to Firebase Google Group
Hi,

since January 25th we are experiencing (for at least 2 differents apps) that the units reported in Firenase console for the first_open event are wrong. There are shown only about the 15% of all the actual first_open. Anybody else detected the issue?

Our apps are iOS both in the latest Firebase 3.11.1. The same happened with release 3.11.0.

In my opinion it seems as the error is in the server side which is doing some kind of filtering or whatever...

Todd Kerpelman

unread,
Feb 2, 2017, 5:07:10 PM2/2/17
to Firebase Google Group
Hi, Bobgoo. I believe this was due to a bug fix that recently went out. 

We were originally tracking first_open as "Anybody who first opened your app with Firebase Analytics installed". So suppose you were to update to version 1.2 of your app with Firebase Analytics installed. If 200 people installed and opened version 1.2 of your app, and another 500 previous customers upgraded from version 1.1 to 1.2, you would get 700 first_open events.

With the fix that recently went out, we'll only count people who have opened your app for the first time, and not people who have upgraded from an older version without analytics. So in our previous example, you would only see 200 first_open events, which is closer to what that stat is intended to measure.

I'll see if we can get this added to the release notes so other developers are aware.

--T

Petru-Maria Magdeleine

unread,
Feb 3, 2017, 10:32:40 AM2/3/17
to Firebase Google Group
Hi, just check our metrics and we have the same problem too.
It's a match with the iOS Release 10.2.1 date : January 23th.

Todd Kerpelman

unread,
Feb 3, 2017, 1:12:39 PM2/3/17
to Firebase Google Group
Yep -- see my above answer. This was a server-side change, I believe, so you'll probably be seeing it in all of your apps.

Bobgoo

unread,
Feb 6, 2017, 10:55:05 AM2/6/17
to Firebase Google Group
Hi,

unfortunately the filtering you are doing in server-side must be incorrect or something. I have at least two other data sources in order to compare, let me explain:

1) I am collecting another custom event which is send once and only once when the app is first installed (it is also a parameter set in iOS Keychain so it cannot be duplicated) and it is showing a number of aproximately 6.5x the first_open event.
2) The actual downloads in iTunes Connect are similar to my custom event while the first_open events are only accounting the 15% of downloads.

It happened exactly the same in November when iOS 10.1.1 was released. The problem last from 9 November until mid December. I have just check November data and it seems it was recalculated and corrected on your side, because in the present, data for first_open on that month make sense compared to my custom event and to iTunes Connect. So, in my opinion we are facing the same issue we had in November.

Regards,

Todd Kerpelman

unread,
Feb 6, 2017, 6:17:21 PM2/6/17
to Firebase Google Group
Hmmm... well, I certainly won't rule out the possibility that something else is wrong. Bob, can you take a screenshot of your iTunes connect report, your firebase first_open report, and mail them to me, along with your app ID? (The one that looks like 1:1234567890:ios:314c85221c190efe1) I'll pass 'em along to the product team and we can see if something else is going on here...

--T



--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/ZeIENGw52gE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/3098b528-6c3c-438c-a751-1ef8ee48fec7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bobgoo

unread,
Feb 7, 2017, 10:08:19 AM2/7/17
to Firebase Google Group
Yes, sure... At what email address can I reach you?

Todd Kerpelman

unread,
Feb 8, 2017, 12:47:15 PM2/8/17
to Firebase Google Group
Actually on second thought, why don't you send your information through our Troubleshooting page over at  https://firebase.google.com/support/contact/troubleshooting/? We've got people responding to it 24-hours a day, and it'll make sure we get the right info about your app  -- you can select it in the drop-down list. 

Please include the screenshots I mentioned above and also mention in your description that you've been speaking with me about the case. That way, they'll be sure to get me involved.

Thanks!

--T

On Tue, Feb 7, 2017 at 12:36 AM, Bobgoo <d...@bobgoo.com> wrote:
Yes, sure... At what email address can I reach you?
--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/ZeIENGw52gE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

Bobgoo

unread,
Feb 9, 2017, 10:50:43 AM2/9/17
to Firebase Google Group
It seems from yesterday the first_open event numbers in console have gone back to normal. So probably something has been rolled back or changed in the server side.

Todd Kerpelman

unread,
Feb 10, 2017, 2:23:25 PM2/10/17
to Firebase Google Group
Hi, Bobgoo. (Or is that Mr. Goo?)

Yep -- I've confirmed with the team that they've rolled back the fix because it was creating erroneous reports for some iOS apps like the ones you were seeing. Everything should be looking back to normal on your end soon. Thanks for reporting this!

--T


On Thu, Feb 9, 2017 at 2:16 AM, Bobgoo <d...@bobgoo.com> wrote:
It seems from yesterday the first_open event numbers in console have gone back to normal. So probably something has been rolled back or changed in the server side.
--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/ZeIENGw52gE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages