Why can A4T Activity Impressions not be used in Segment Builder

[mjgood44]

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/is-the-metric-quot-activi...

Reviving this closed topic. I want to be able to measure the conversion rate for visits that saw a given Target Activity, say "Target Test > Experience A". I can include the Target Activity > Experience dimension in my segment, but that value persists for a user for 90 days from the last activity they had where a target activity existed, meaning target activities can persist indefinitely if the user is frequent on the site.

What I want to be able to do is to segment to visits that contain a hit where "Target Test > Experience A" AND Activity Impression exists. This gives me just visits on which the user was presented with the given activity. Why is this not possible, and is there a workaround?

[yuhuisg]

Does the solution that I provided in that thread work for you? I.e. use the Visits metric as a workaround.

I assume that the Activity Impressions metric is an aggregate data that is imported from Target into Analytics at the Target > Experience level, so Analytics can't segment the data per ECID.

[Sukrity_Wadhwa]

Hi @mjgood44,

Was the given solution helpful to resolve your query or do you still need more help here? Do let us know. In case the given solution was helpful, then kindly choose it as the 'Correct Reply'.

Thanks!

[mjgood44]

This is not a helpful reply. As I stated in my original post, Visits would not work because the values for A4T data persist indefinitely as long as a user has activity in the past 90 days.

[Vinay_Chauhan · Accepted solution]

You can try building a visit-level segment that looks for hits where both "Target Activity > Experience A" and "Activity Impression" happen in the same visit. Instead of just using the Target dimension (which sticks around for 90 days), this method focuses only on visits where the user actually saw that experience.

In the segment builder, set both conditions to hit-level, then wrap them in a visit-level container. That should give you more accurate data for visits where the experience was truly shown.