Events showing in event log not turning up

I have a bunch of checkpoint events in our app

cp1
cp2
cp3 etc

and a funnel associated with these events.
I was worried because not many people were going through the funnel.
Further investigation shows that while all the events are being triggered- I can see them in Events log - they are not always attributed back to the user. So, that user doesn't look like they went through the funnel, whereas in reality they did.
It isn't always the same events that are missing either.
Events in the log which are attributed to the user look exactly the same as those that aren't.

Help!

0

Comments

16 comments
  • Hello,
    can you post a screenshot of event in the event logs (opened row with request details) and then screenshot of the user profile, where it should be, but its not?

    0
    Comment actions Permalink
  • Also which SDK and server version are you using?

    0
    Comment actions Permalink
  • And next question: do you set your custom user ids in SDK or rely on AdvertisingID / OpenUDID?

    0
    Comment actions Permalink
  • Screen shot from our player profile -
    The events we're interested in are:
    select_career_win1
    select_career_win4
    select_career_win5

    Clearly events 2 & 3 are missing from this sequence.

    0
    Comment actions Permalink
  • Screenshot from the log showing missing event.
    All missing events are in the log.

    0
    Comment actions Permalink
  • We're using the Android SDK
    Countly Enterprise Edition V17.05.1 (hard to tell because of your reliance on gray on black - How do we change this?)

    We are setting custom user ids - so that they match our player ids on our back-end

    thanks for your help in getting to the bottom of this.
    AA

    0
    Comment actions Permalink
  • You say it's Android SDK but screenshots say iOS. I think all those events select_career_winX happen in several sessions (several app opens), correct?

    Also do you change user id once when he logs in or when you first got your player id or you do this on each app launch? And could you please tell me how you call [Countly.sharedInstance setNewDeviceID:@"new_device_id" onServer:YES] - with onServer: YES?

    0
    Comment actions Permalink
  • Sorry, we are using both android and iOS sdk - this is happening with devices on both platforms.

    I've asked an engineer to answer your other questions,
    Do you have anyone more local to my time zone who could help?

    Thanks. AA

    0
    Comment actions Permalink
  • Oh, and no the events are all part of the same session.
    If I repeat the process on other devices/ accounts sometimes all the events are attributed to the user but sometimes not.
    It is not always the same events that are missing either.

    0
    Comment actions Permalink
  • One thing that we do is to ignore requests with same timestamp, in case a duplicate was sent. But checking from your screenshot it seems they have different timestamps.

    With user merging it is possible that event is received while user was merging data or something like that, so knowing scenario when and how merging happens could help us.

    0
    Comment actions Permalink
  • About timezone, unfortunately I think we all are on GMT +2 to +4

    0
    Comment actions Permalink
  • From my engineer...

    For setting the device id. One of the first thing we do in our game is to authenticate with our api servers then once it has it will set the device id with countly. This happens well before we send the select_career_win events. This happens everytime we launch the game.

    For our setting the device id our code is

    iOS:

    void countly_setDeviceId(const char* deviceId)
    {
    [Countly.sharedInstance setNewDeviceID: [NSString stringWithUTF8String: deviceId] onServer: true];
    }

    Android:

    changeDeviceId(deviceId)

    0
    Comment actions Permalink
  • ar2rsawseen:

    With user merging it is possible that event is received while user was merging data or something like that, so knowing scenario when and how merging happens could help us.

    Not sure what you mean by this? Pls elaborate.

    0
    Comment actions Permalink
  • Guys - could I get some help with this pls?

    0
    Comment actions Permalink
  • Hello,
    so user merging probably is not the reason, because you do it on start, and you don't see all events from same request. Currently there are no know bugs, and only states when such situation might happen, if you specifically block some event keys (which you did not, because they still appear in other cases).

    So this may be a bug we are not aware of and would need further examining. Let's move it to an email conversation which will be faster and would allow providing information more freely

    0
    Comment actions Permalink
  • received email and replied.. thanks.

    0
    Comment actions Permalink

Please sign in to leave a comment.