Target Activity is Not Present in Analytics Workspace | Community
Skip to main content

4 replies

Perrin_Ennen
Community Advisor
Community Advisor
February 24, 2026

Hi ​@PrasanthV,

Most of the time this happens because Analytics hasn’t received any qualifying hits for the activity yet. Even if the activity is set to use Adobe Analytics as the reporting source, it will only appear in Analysis Workspace after the first visitor actually qualifies and the hit is processed (which can take 30–120 minutes or sometimes longer). https://experienceleague.adobe.com/en/docs/analytics/technotes/latency

 

I would first confirm that the activity is active, that the mbox is firing on the page, and that at least one real (or QA) visitor has entered the activity. Also make sure you are looking at the correct report suite in Workspace and that the reporting source was set to Adobe Analytics before activation.

 

Hope that helps.

 

If it still doesn’t appear after a few hours, could you share:

  • whether the activity has received any traffic yet,
  • which implementation you use (at.js or Web SDK), and
  • whether you see the Analytics call following the Target request in the network tab?
PrasanthVAuthor
Level 3
February 24, 2026

​​Hi ​@Perrin_Ennen ,

 

Thank you for your prompt response.

  1. Yes, but it shows unspecified.
  2. at.js
  3. Yes
Perrin_Ennen
Community Advisor
Community Advisor
February 24, 2026

Hi ​@PrasanthV,

thanks for the update. If the activity shows as “Unspecified”, it usually means Analytics is receiving hits but cannot yet attribute them to specific experiences. 

https://experienceleague.adobe.com/en/docs/target/using/integrate/a4t/troubleshoot-a4t/a4t-troubleshooting

 

From my side, I would now double-check that the activity has actually delivered at least one experience (not just qualified), that the correct report suite is selected in Workspace, and that Adobe Analytics was set as the reporting source before activation. I would also verify that visitor stitching looks healthy (same MID/SDID passed between Target and Analytics).

April 21, 2026

Hi ​@PrasanthV 

If your Target activities are correctly stitching (SDID matches), and numeric IDs are appearing in Analysis Workspace, & Activity Name and Experience Name have remained "Unspecified",

then this occurred because the automated "handshake" that sends metadata from Adobe Target to Adobe Analytics failed to sync, resulting in data mapping missing in the backend lookup table. 

  1. Immediate workaround is manual classification mapping, it can enforce manual mapping that bypass automated sync using the classification rule builder in analytics. Setup a basic rule Criteria : contains -> Activity ID, Action: Activity Name/Campaign -> your activity Name. 
  2. Long term fix: reach out to adobe support to force system resync of the A4T classifications. 
PrasanthVAuthor
Level 3
April 22, 2026

Hi All,

 

Thank you for your support.

There was no issue on my end; It is now working after the Adobe support team completed the backend configuration.

Level 2
April 22, 2026

If it is happening only with this one activity, one issue I encountered was that changing an activity name after it has been activated in adobe target is not displaying in Adobe Analytics.