Identifying Late Arriving Hits | Community
Skip to main content
Level 2
February 20, 2025
Solved

Identifying Late Arriving Hits

  • February 20, 2025
  • 2 replies
  • 976 views

Hi.  Is there a way to identify if a hit in the hit_data.tsv file is a late-arriving hit?  We currently do not receive late-arriving hits and we are assessing how our data loads will need to change if we enable this.  Thanks in advance.

Best answer by Jennifer_Dungan

Ok, so you are talking about offline data, or technically imported data.

 

Looks like you have to work with client care to enable including this data in the feeds. It's possible that maybe the "hit_source" would be the field to indicate "late arriving data"?

 

1: Standard image request without timestamp 
2: Standard image request with timestamp

 

1 might be all the normal data, and 2 would be the late arriving?  We don't have this enabled on our feeds as we aren't collecting offline data or ingesting data sources.

2 replies

NicoleNLAuthor
Level 2
February 20, 2025

Also, one more question, are these typically Mobile App hits or can they include Web hits as well?

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 20, 2025

I suppose it depends on your definition of a "late arriving hit".

 

Technically, your mobile apps can be configured to capture "offline data", this will store a set number of tracking calls while the users are offline, then send that data to the server once the user reconnects to the internet... this means that the hit timestamp can be significantly earlier than when it arrives on the server.

 

On the other hand, you may just be referring to network latency and delays in processing data on the Adobe server (particularly when there is major incidents or maintenance occurring).

 

For the processing delays, the best option is to use the max delay on your Raw Data feeds to ensure as much data is processed as possibly before bundling up the feed and sending it off... I believe you can set up to 2 hours delay. Unless there are major issues, this should solve a lot of issues.

 

If you are talking about Mobile App Offline Data, that's a different story... data could come in months later... You could try creating a validation process where you maybe choose an acceptable time frame to re-pull data, then create a delta comparison between what you have and what is new, adding the new data to your lake... 

NicoleNLAuthor
Level 2
February 20, 2025

Thanks Jennifer!  I am referring to the hits identified in the article at the following link.  Does these hits include all of the cases you specified above?

Late arriving hits | Adobe Analytics

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
February 20, 2025

Ok, so you are talking about offline data, or technically imported data.

 

Looks like you have to work with client care to enable including this data in the feeds. It's possible that maybe the "hit_source" would be the field to indicate "late arriving data"?

 

1: Standard image request without timestamp 
2: Standard image request with timestamp

 

1 might be all the normal data, and 2 would be the late arriving?  We don't have this enabled on our feeds as we aren't collecting offline data or ingesting data sources.