Looking for approach to report on offline vs online hits for a native mobile app | Community
Skip to main content
N
nancyduley
Level 2
November 14, 2024
Question

Looking for approach to report on offline vs online hits for a native mobile app

  • November 14, 2024
  • 1 reply
  • 920 views

Hello, we are using adobe analytics mobile sdk and flutter platform for our iOS/Android native app. We have turned on "Offline Enabled" so we collect hits for offline activity. In the future we will set up a data feed and connect with adobe engineering to send "late hits" in the data feed. Does anyone know about an approach to report on offline vs online hits, within workspace or via data feed data? How can we segment the hits? Thanks.

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

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 14, 2024

That's an interesting concept... I am not sure if there is an out of the box solution or not? (To be fair, our apps can't run offline, so I've not tried this)

 

My understanding of the "offline" tracking was that Adobe would continue to run on the app, collecting and storing the data locally, until the user came back online, then the entire bundle would be sent to the server....

 

I don't know if there is anything attached to the bundled data that would or could be used to identify it as being offline...

 

However, do you have AEP Assurance (i.e. Griffon) installed in your apps?

 

If I were you, I would do some testing... first hit a few specific screen as "online", (you should see these immediately in Assurance), then turn off the internet and hit the same pages, then turn the internet back on (which should send the bundle to Adobe...which should then show in Assurance.

 

Compare the hits really closely to see if there are any differences (aside from the obvious timestamp differences),

 

You might be able to see if there is some indicator of "offline" and if there is, you might be able to leverage that either directly in Adobe, or possibly map it to a dimension or event using Processing Rules...

 

If you can't find anything, you may have to see if your developers can get creative.... like can they detect the online/offline status? If so, can they set a dimension (either a context variable to be mapped with processing, or directly into the schema depending on your implementation) that you can use in your reporting?

    N
    nancyduleyAuthor
    Level 2
    November 14, 2024

    Jennifer, thanks for the timely and very helpful reply!

     

    The main reason we are interested in offline activity is because we have spent effort to provide offline features and are thinking of adding more. We are wondering if people use features we already added.

     

    I like your idea of seeing if there is anything in the bundled data that could be used to identify it as offline hits. I think our developer uses Griffon. Mapping data to a dimension or using a processing rule makes sense. Great suggestions to review with our developer to see what could work.

      Jennifer_Dungan
      Community Advisor and Adobe Champion
      Jennifer_DunganCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      November 14, 2024

      Oh yeah, I can totally understand wanting to understand the usage between online and offline! It's just not something we can do... at least not yet... being a Newspaper having fresh content is important (as well as being able to take down information for legal reasons quickly sometimes happens... like we need to remove names due to publication bans, or needing to get updated information on developing stories, that sort of thing)... so none of our apps have the ability to "read offline" at this time...

       

      I would love to hear if you find something you can use out of the box, or if you come up with a custom solution! I imagine other people might be interested too.

       

      Good luck!

        Terms & ConditionsAccessibility statement

        Loading footer...