How can I create a sequential segment that captures events that happen on the same page view? | Community
Skip to main content
D
dks0526367
New Member
November 28, 2022
Solved

How can I create a sequential segment that captures events that happen on the same page view?

  • November 28, 2022
  • 1 reply
  • 1321 views

For example, I would like to create a segment that captures users that use the same Refinement Attribute multiple times on the same page. Essentially I want a segment that looks like the one in this image, but I would want it to be "Within 0 page views" so that it only captures instances of this happening on the same page. However, Adobe requires a minimum of 1 to be set with the "within" operator. Is there any way to only include things from the same page view?

 

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 Jennifer_Dungan

Yeah, this seems tricky.. basically I think you are basically trying to get how many subsequent times people are using this feature on the page?

 

I am not sure if there is a good, non-convoluted way to segment this... if this is an important metric, maybe you should consider setting up a Counter eVar? I haven't used these much, I only started looking into this... but I wonder if on the page view you could set the eVar to 0, then on each use you can increment the eVar with "+1" (just double check that the eVar will take 0... we all know how that works in classifications...  as in not well)

 

So that if the user leaves the page, then comes back, the eVar will be reset to 0 and each use can be counted again?

 

Not sure if that covers your needs.....

 

 

Here is a little documentation on Counter eVars (basically a little bit in the table regarding eVat Type, and paragraph at the bottom of the page - I scanned quickly through the video, but I think it really only addresses persistence) https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/conversion-variables/conversion-var-admin.html?lang=en

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 29, 2022

Can you re-post your image? It seems to have failed....

 

But my first instinct it to try to use "within 1 Hit" rather than within one page view... we may need to try adding some fancy exclude logic, but without seeing your desired outcome it's a bit hard to help at this time.

D
dks0526367Author
New Member
November 29, 2022

Hi Jennifer,

 

Sorry about that, I edited the original post to include a proper image. 

 

Unfortunately I don't think "within x Hits" would work either, as there could be any number of hits on that page before the hit containing the repeat behavior for which I'm looking.

D
dks0526367Author
New Member
December 1, 2022

Yeah, this seems tricky.. basically I think you are basically trying to get how many subsequent times people are using this feature on the page?

 

I am not sure if there is a good, non-convoluted way to segment this... if this is an important metric, maybe you should consider setting up a Counter eVar? I haven't used these much, I only started looking into this... but I wonder if on the page view you could set the eVar to 0, then on each use you can increment the eVar with "+1" (just double check that the eVar will take 0... we all know how that works in classifications...  as in not well)

 

So that if the user leaves the page, then comes back, the eVar will be reset to 0 and each use can be counted again?

 

Not sure if that covers your needs.....

 

 

Here is a little documentation on Counter eVars (basically a little bit in the table regarding eVat Type, and paragraph at the bottom of the page - I scanned quickly through the video, but I think it really only addresses persistence) https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/conversion-variables/conversion-var-admin.html?lang=en


Yea, I think that sounds like the best option here. Thankfully I don't think this is important enough to require that extra work, but it's good to know that there's an option if something like this comes up again in the future.

Thank you!

Terms & ConditionsAccessibility statement

Loading footer...