Adobe Analytics

ChadSi · 11/19/25

While debugging updates to a mobile app, we can see the context data being sent properly and, in Assurance, the data being bucketed properly in the post-processed data section. However, the data is not being passed into Adobe Analytics. I have checked processing rules and everything looks ok. I've also tried adding in test evar and event and in Assurance they are populated, but not in Analytics. Another twist is I could see someone completed the same flow and the data from their session was passed into analytics. I can't seem to find any rhyme or reason to this.

Sumit-Kumar · 11/19/25

If your mobile SDK sends timestamped hits and the report suite is not timestamp optional, those hits will be discarded silently.
Check in Admin - Report Suite - General - Timestamp Optional. If it’s not enabled, turn on Timestamp Optional for that RSID.
Enable the Timestamp Optional setting | Adobe Analytics

If this doesnt solve, confirm that your setup matches the successful session by your teammate. This includes using the same device type (iOS or Android), the same app build and RSID. Are you using the AEP Mobile SDK with Edge Network or the traditional service specific endpoint. OR are you on a VPN or within an IP range that might be excluded by internal filters? If so, try testing on mobile data or from an external network to rule out IP based exclusions.

SamuelPaulPeter · 11/19/25

As @Sumit-Kumar said,

If Assurance shows your context data but nothing appears in Analytics, it usually means the hit is getting dropped server-side.

The two things to check first:

Timestamp Optional
If your mobile SDK is sending timestamped hits and the report suite isn’t set to Timestamp Optional, Adobe will silently discard them.
Admin → Report Suite → General → enable “Timestamp Optional.”

RSID / Endpoint mismatch
Make sure your failing session is sending to the same RSID and same endpoint as the session that worked (AEP Edge vs Legacy AA). Even a small mismatch will send data to the wrong place.

If both of these are correct, test outside your company network (VPN/IP filters) and compare the raw hit from a working vs failing device — that usually reveals the gap quickly.

ChadSi · 11/21/25

Thank you both for your help. I have confirmed that the RS setting is timestamp options. I have also confirmed that the RSID and Endpoint are the same. I have also broken down the successful post by device and build and replicated that. Did not work. Additionally, I used a VPN to replicate being in India. This too did not work. Still perplexed.

Jennifer_Dungan · 11/20/25

In Assurance, did you get a Post Processing Response? Or just the context variables...

It's possible that there is a configuration issue in your app for the DataStream ID, so that once the information is sent to Adobe, Adobe doesn't know what to do with it, or where to send it...

ChadSi · 11/21/25

In Assurance, I do get the Post Processing Response and it looks correct.

While I understand that there could be a config issue, all other track.state and track.actions are working properly. It is only this screen that is an issue and it shares configuration with the rest of the app.

I also see more successful sessions coming in, so it works sometimes.

I really appreciate your help.

Sumit-Kumar · 11/21/25

hi @ChadSi

Difficult to answer without access to your logs screenshot and your setup. But, based on your response, it appears you’re not using edge Network or data stream, but only the adobe analytics service endpoint with SDK i.e. trackState/trackAction . From your previous reply to Jen, it’s also clear that most of your tested trackState/trackAction calls are appearing in reporting except for one screen.

I recommend starting by validating in Assurance whether the analytics events for that trackState show as PROCESSED (as per screenshot below). If they don’t, that means an issue specific to that screen. If they do show as processed, then set up a real time report in AA for that RSID with dimensions like GEO, Page or any applicable prop, and check if your test data appears instantly.

If you have access, modify the data value in androidStudio or Xcode to make it unique for your testing env. This will help confirm whether the data is being recorded in analysis Workspace. These steps should help narrow down the issue and help in finding the root cause.

Also, just to share status, pls visit :--
Adobe Analytics View in Assurance | Adobe Experience Platform

Post-processed status

After the SDK makes a network request with Adobe Analytics, the status will tell you if Assurance was able to retrieve the post-processing information for the Adobe Analytics request. The Analytics Events view must remain active while the post-processing status is in operation after the request has been triggered.

Please note that in order to retrieve post-processing information, the logged-in user must have access to the corresponding report suite.

Status Description

Queued	The network request is fetching the post-processing information.
Processed	The network request was successful, and the post-processing information is received.
Delayed	The maximum number of requests retries to fetch the post-processing information has been exceeded.
Error	An error caused the network request to fail. More details about the error are displayed in the event details view.
Unauthorized	The user does not have access to the Adobe Analytics report suite.
Unavailable	The Adobe Analytics request does not have a corresponding AnalyticsResponse event.
No Debug Flag	The current Adobe Analytics or Assurance SDK version might not support the Analytics Debugging feature. For more information, please read the Troubleshooting guide.
Expired	The AnalyticsTrack or LifecycleStart event is older than 24 hours.

Jennifer_Dungan · 11/21/25

Good Advice @Sumit-Kumar

Another thing... IF there is something significantly malformed in the data, it's possible that Adobe is throwing it out... but it should still be in the Raw Data... maybe you can export 1 day's worth of Raw Data, and check to see if the page is there, and see if they are identified as "exclude_hit"

If you can find it, you may have to go through all the fields to try and find what is the problem so that you can fix it.