Skip to main content
Jignesh_Bhate
Jignesh_Bhate
Level 3
April 3, 2018
Solved

Unused Signals Report

I am trying to bring AA props and eVars in AAM, just trying to understand when would I be able to them in Unused signals report? As of now, it reports the signals for date (T-2)? Is this not realtime or near realtime?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    JerryHe1Accepted solution
    Level 3
    April 3, 2018

    Qualification for traits and segments happen in real time yes but reporting doesn’t show up until the day after. If you log into AAM now, you can only see traits reporting up to yesterday. If you see otherwise, please tell me. That would be awesome.

    The best way I find to test SSF is to create a trait and segment for testing that is based on some query parameter that identifies you only. For example, I setup a rule where it checks if the url (which can be captured in an evar or prop, depending on your implementation) contains Adobe_Test and then map this segment to a cookie destination. The beauty of this is that you can qualify for this trait and segment and then you can see that in your browser response as cookie destinations show up there. Hope this helps.

    Thanks,

    Jerry Helou, Ph.D

    Digital Experience Architect

    <http://www.softcrylic.com/>

    T: +1 302-381-2883

    www.softcrylic.com<http://www.softcrylic.com/>;

    <https://www.linkedin.com/in/jirarhelou/>

    <https://softcrylic.com/e-books/marketers-play-book/>

    View in thread

    4 replies

    JerryHe1
    Level 3
    April 3, 2018

    All reporting in AAM including unused signals are one day behind but the availability of these reports might not happen until noon EST or even later. It depends on the processing jobs.

    Sent from my Phone

    Translate
      Jignesh_Bhate
      Jignesh_BhateAuthor
      Level 3
      April 3, 2018

      Hi Jerry

      I was actually playing around with rule based traits and as per this article https://marketing.adobe.com/resources/help/en_US/aam/c_tb_trait_summary.html , it seems the qualification for rule based traits happen in realtime. There can be multiple problems here,

      • either SSF isn't working correctly at my end due to which data isn't flowing in AAM. I can see the values in the /b/ss/ url, so i am a bit hopeful that SSF might be working

              or

      • my trait builder query is incorrect, due to which I cant see anything in the trait graph

      Thanks

      Jignesh

      Translate
      JerryHe1Accepted solution
      Level 3
      April 3, 2018

      Qualification for traits and segments happen in real time yes but reporting doesn’t show up until the day after. If you log into AAM now, you can only see traits reporting up to yesterday. If you see otherwise, please tell me. That would be awesome.

      The best way I find to test SSF is to create a trait and segment for testing that is based on some query parameter that identifies you only. For example, I setup a rule where it checks if the url (which can be captured in an evar or prop, depending on your implementation) contains Adobe_Test and then map this segment to a cookie destination. The beauty of this is that you can qualify for this trait and segment and then you can see that in your browser response as cookie destinations show up there. Hope this helps.

      Thanks,

      Jerry Helou, Ph.D

      Digital Experience Architect

      <http://www.softcrylic.com/>

      T: +1 302-381-2883

      www.softcrylic.com<http://www.softcrylic.com/>;

      <https://www.linkedin.com/in/jirarhelou/>

      <https://softcrylic.com/e-books/marketers-play-book/>

      Translate
        Jignesh_Bhate
        Jignesh_BhateAuthor
        Level 3
        April 4, 2018

        Yeah, you are correct. Thank you for clarifying the notion between trait qualification and reporting into the UI. Also, thanks for sharing a quick test approach for SSF validation

        Thanks,

        Jignesh

        Translate
          Terms & ConditionsAccessibility statement

          Loading footer...