AT Source Reporting Latency | Community
Skip to main content
acookie4rachel
acookie4rachel
Level 2
June 7, 2022
Solved

AT Source Reporting Latency

Hi, I just activated an activity with AT as reporting source. I have QA to verify the expected experience. The primary goal is a lightbox clickthrough.

My team has performed some lightbox clickthroughs on the live site. However, after an hour, I still do not see the conversions in reporting. May I know what is the latency for conversion data to appear in reporting?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    dsingh16Accepted solution
    Employee
    June 10, 2022

    Hi, @acookie4rachel Here is the document which mentioned the features that depend on the latency of data. 

    https://experienceleague.adobe.com/docs/analytics/technotes/latency.html?lang=en#:~:text=Analytics%20for%20Target%20(A4T)%20requires,stored%20in%20the%20same%20hit.

     

     

    View reply

    3 replies

    acookie4rachel
    acookie4rachelAuthor
    Level 2
    July 21, 2022

    Not explicitly mentioned in AT documentation, but it seems like the standard 2-hour latency, similar to AA, applies in AT too. 

    Translate
    dsingh16Accepted solution
    Employee
    June 10, 2022

    Hi, @acookie4rachel Here is the document which mentioned the features that depend on the latency of data. 

    https://experienceleague.adobe.com/docs/analytics/technotes/latency.html?lang=en#:~:text=Analytics%20for%20Target%20(A4T)%20requires,stored%20in%20the%20same%20hit.

     

     

    Translate
      acookie4rachel
      acookie4rachelAuthor
      Level 2
      July 21, 2022

      Thanks! But this is AA documentation. I'm not using AA source for reporting (A4T). But seems like the 2-hour latency applies in AT source reporting too.

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...