Hybrid App offline tracking issue | Community
Skip to main content
C
cathyc18262486
Level 2
February 5, 2024
Question

Hybrid App offline tracking issue

  • February 5, 2024
  • 2 replies
  • 1898 views

We work on hybrid app tracking (only it’s javascript part from webview). We utilize AppMeasurement javascript implementation as the app has page reloads (all the app files are stored on user’s device) and we need to track events offline.
 Online tracking works fine. We have issues with offline tracking.

 Settings:
 only ‘s.trackOffline = true’ and ‘Timestamp Optional’ for the report suite.

 Not set:
 s.offlineThrottleDelay
 s.offlineHitLimit
 s.forceOffline
 s.forceOnline 

The issue:
We’re able to see offline events in real-time report as soon as we restore the connection after offline interactions. We can see them in the report later.
 But if there are more than 10 events in offline queue (for instance, we fire 20 events offline) we restore the connection and only 10 (or less) events fire in real time report (and appear in the report later).
This behavior is either in local environment or in the app on the iPad.
We’ve tried to monitor the process in the browser locally:
requests are multiplying approximately every 500 milliseconds in the queue trying to get to the server. And only the last 10 requests for the last 10 events (or even less) get status 200 after restoring the connection. 

What can cause the issue? Have we missed smth or is it expected behavior? Thank you!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 5, 2024

Hmm that is interesting.. I haven't worked with Offline data so much, since all our content requires the internet at this time.. 

 

However, that doesn't sound right... if you have offline data, then I can't see only the last 10 calls making it through... that seems counter productive to having offline data in the first place...

 

That said, this might be worth a ticket to client care, they should be able to see at a deeper level where the information might be getting lost and offer more suggestions that I can (maybe someone else here has more experience in this area and can chime in).

 

I do ask that whatever you find out, please share back here, so that everyone can benefit from your learnings.

C
cathyc18262486Author
Level 2
February 6, 2024

Thank you, Jennifer. We've already reported this issue to Adobe Customer Care and I hope I'll share the results soon.

leocwlau
Community Advisor and Adobe Champion
leocwlauCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 6, 2024

You may try to set the s.offlineThrottleDelay to control how many hits are sent simultaneously when the device is back online. When unset or 0, all queued hits sent at once could cause network issues and loss of data, and it is bad for performance as well.

    C
    cathyc18262486Author
    Level 2
    February 6, 2024

    I played with this setting as well as with s.offlineHitLimit. I set different values to them and tested. The issue remains.

    leocwlau
    Community Advisor and Adobe Champion
    leocwlauCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    February 7, 2024

    That's getting difficult. I never tried that offline tracking myself so no first-hand experience, perhaps this can be an interesting exercise to test out.

    I am thinking if the issue is with AppMeasurement which is unable to send out buffered hits when the device reconnected; or if AppMeasurement attempted to send offline hits but those hits failed; or hits sent but some timestamp issue causing the data unable to be displayed in AA. Noted that you already monitoring the embedded browser for network activities so you could have the answer already.

    Hope Adobe Customer Care can give you the answer.

      Terms & ConditionsAccessibility statement

      Loading footer...