Facing issue to see A4T report | Community
Skip to main content
A
AbinashMi2
June 18, 2025
Solved

Facing issue to see A4T report

  • June 18, 2025
  • 2 replies
  • 482 views

Hi Team,

We've created an AB test activity for the mobile app and we have selected a specfic report suit other than our web one. We've observed following issue when we click the "view in analytic" link in the Adobe target report section to check A4T report. This works fine on those activities which are created for the web. Is that we are missing anything on the app sepecfic report suit. How can I fix this?


Looking for any help.

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

If you are seeing “No Control Experience Found,” it usually means the A4T data from Target isn’t getting stitched into the Analytics hit from the mobile app.

 

Since your app is using the AEP Mobile SDK, it’s worth checking a few things:

  • Make sure both the Target and Analytics extensions are properly set up in your mobile Launch property.

  • Confirm that the SDK is actually sending Target metadata (like activity and experience) with the Analytics hit, this does not happen automatically in all cases.

  • You might need to manually pass those values.

 

Even though the report suite has the classifications, A4T reporting only works if the right data is passed during the hit.

 

If everything looks correct in the setup and it’s still not working, it could help to capture a debug log or network call and check if the Target activity data is actually being sent to Analytics.

And the last thing would be to consult the Adobe Support team for deeper analysis.

Hope that helps!

2 replies

Josh__Stephens
Community Advisor
Josh__StephensCommunity Advisor
Community Advisor
June 18, 2025

It looks like there are some classifications that are expected but missing from the report suite. Do your web & app activities use the same report suite? If not, look to see what classifications the web reports are using and verify those are in your mobile report suite as well.

    Vinay_Chauhan
    Community Advisor
    Vinay_ChauhanCommunity Advisor
    Community Advisor
    June 18, 2025

    That error usually means the report suite you’re using for the app doesn’t have all the required A4T components enabled, especially the classifications like activity name, experience, offer, etc.

    You might want to double-check that the report suite selected for the mobile app is A4T-enabled. Just because it works for your web suite doesn’t mean the same setup exists for mobile, they need to be configured individually.

    Also, it’s worth confirming whether the necessary classifications for A4T (like the "Analytics for Target" ones) have been provisioned for the mobile suite. If not, you’ll probably need to contact Adobe Client Care to get those enabled, that usually resolves the “incompatible report suite” error.

    And if you’re using the AEP Mobile SDK, make sure the A4T configuration is properly set up within the mobile app implementation too.

    Once the report suite has the right components, the A4T reports should work without that error.

    Hope this helps!

      A
      AbinashMi2Author
      June 23, 2025

      Hi @vinay_chauhan , Thank you for you reply. I’ve reviewed the Analytics for Target (A4T) classifications, and they exist in both the mobile and web report suites. On the mobile report suite, these classifications are also working correctly in freeform tables. However, when I checked the A4T report, it showed “No Control Experience Found.”

      For the web implementation, we are using AppMeasurement.js, whereas for mobile, we are using the AEP Mobile SDK. Could you please help us verify whether the A4T setup has been correctly implemented on the AEP Mobile SDK? It looks like that could be the issue.

       

      Vinay_Chauhan
      Community Advisor
      Vinay_ChauhanCommunity AdvisorAccepted solution
      Community Advisor
      June 23, 2025

      If you are seeing “No Control Experience Found,” it usually means the A4T data from Target isn’t getting stitched into the Analytics hit from the mobile app.

       

      Since your app is using the AEP Mobile SDK, it’s worth checking a few things:

      • Make sure both the Target and Analytics extensions are properly set up in your mobile Launch property.

      • Confirm that the SDK is actually sending Target metadata (like activity and experience) with the Analytics hit, this does not happen automatically in all cases.

      • You might need to manually pass those values.

       

      Even though the report suite has the classifications, A4T reporting only works if the right data is passed during the hit.

       

      If everything looks correct in the setup and it’s still not working, it could help to capture a debug log or network call and check if the Target activity data is actually being sent to Analytics.

      And the last thing would be to consult the Adobe Support team for deeper analysis.

      Hope that helps!

        Terms & ConditionsAccessibility statement

        Loading footer...