Data not arriving for identical Report Suites

[digitalNick]

Hello Everyone

We're currently facing a major issue with one of our Adobe Analytics instances: We initially created a Report Suite for development purposes which is receiving data via Adobe Launch as expected. However, any other Report Suite that we were generating after that point, does not seem to receive any data at all (neither in real-time and/or Analysis Workspace).

All settings are identical as we used the initially created, working Report Suites as a template to make sure we inherite the expected setup. We also validated already that it's not associated with our implementation setup by triggering manual hits via the legacy static pixels. The result is the same, the working Report Suite receives data, all others are do not get any data at all.

Here is what we already tried to exclude as potential issues:

• Timestamp configuration (is off for all Report Suites working and non-working)
• Implementation (as explained above)
• Go-live date has passed already a few days ago
• Identical setup/configuration of all Report Suites

As we've never experienced such a complete outage of newely created Report Suites, I wanted to verify if there might be any other underlying issue. Adobe Support has been contacted as well but did not came back with an assessment/solution yet.

Thank you in advance.

[Saurav_Raj]

Hi @digitalNick 

I will recommend pulling a data feed report for a day when you conducted this test. Using the MID from your server call, you can search for the hit and validate if they are present in the backend or not. If they are getting rejected, you should see it in exclude_hit column. The lookup table will give you the reason for it.

Lookup table for exclude_hit : https://experienceleague.adobe.com/docs/analytics/export/analytics-data-feed/data-feed-contents/data...

[kaush1889]

What is the daily traffic estimates provided at the time of creating new report suite? If it is more than a million, Adobe Infrastructure team takes time to allocate resources and activate the report suite.

[kaush1889]

The approach @Saurav_Raj suggested should be used after eliminating all the possible issues. Also, while fetching raw data, opt for hourly files instead of daily. 

[digitalNick]

@kaush1889 / @Saurav_Raj, thanks so much for all the answers and potential investigations. In collaboration with Adobe support, we tried the direct data feed extract without any issues. There are literally no entries…neither skipped nor successfully processed. Furthermore, the overall expected traffic is comparatively low in the thousands, not millions.

However, as one of the support engineers found out, it might be related to the Axle Date Range within the backend of the Report Suite. The only working Report Suite has proper dates set like this:

2000-01-01 00:00:00 through 2022-03-02

All others, which are not working, are showing the following configuration:

2000-01-01 00:00:00 through 2000-01-01

Nevertheless, it has not been confirmed yet as they needed to escalate it to engineering for further analysis.

[kaush1889]

Right ... this is most probably due to the above mentioned comment:

"What is the daily traffic estimates provided at the time of creating new report suite? If it is more than a million, Adobe Infrastructure team takes time to allocate resources and activate the report suite."

[digitalNick]

@kaush1889, I don't think so as none of the Report Suites are reaching that limit. The estimated daily page views are between 1,000 - 5,000 - far away from the millions:

We even created one with only 100 for testing purposes - still the same result.

[kaush1889]

Got it. Then as you confirmed, it's an internal issue which Engineering team will handle.

[digitalNick · Accepted solution]

FYI @kaush1889 / @Saurav_Raj it has been confirmed as a global defect by Adobe:

https://status.adobe.com/products/1173/20220303017