New vs. Return Visitors to a Specific Page

[skatofiabah]

Hi,

I want to know how to get new vs. return visits/visitors to a specific page and how to show this over time? I don't want to look at when visit =1 and visit >1 because a new visit/visitor to that page could have happened visit 1 or visit 99 of a given visitor to the entire website and domain. Is there an easy way to break this down that I'm not seeing. I feel like I'm having to make a segment for each month and then re-tac on more months and create a segment for each month to repeat. There has to be a better way I'd think.

Thanks!

[Jennifer_Dungan]

Hi @skatofiabah ,

I know what you mean... Visit number isn't sufficient for looking at recent traffic... The default segments are really designed for 'all time'...

That said, I think you would benefit from my non-overlapping new/repeat users within a specific time frame segments.

https://experienceleague.adobe.com/en/docs/events/the-skill-exchange-recordings/analytics/may2023/ro...

[igupta]

Don't know if this is what you are looking for? getNewRepeat plugin from Adobe allows you to look at new vs. repeat visitors within a specified time period. Default cookie expiration is 30 days but you can custom set it per your needs. This would entail a user who has visited a site as new and repeat if he comes back within cookie lifetime period. On each subsequent repeat visit, cookie lifetime period is renewed. If user comes after cookie expiration time, user is New visitor again.

https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/plugins/getnewrepeat

You can also try the segments from @Jennifer_Dungan  and it may solve your use case as well.

[Jennifer_Dungan]

While an option, I found this plugin hasn't worked well in years... not since the war on cookies started... while the cookies were set first-party, they weren't set to secure or same-site... I stopped using that plugin years ago... Also, cookies set by JavaScript are less trusted than cookies set by a server... these are set by JS, cookies like the ECID are set by the server... (I not even talking about server-side cookies... just regular cookies... but there is a definite scale of trust)

It's possible that the plugin has been updated since I dropped it, and it's worth a try... but I used to use this plugin for years.. but dropped it quite some time ago because I just didn't trust the results any longer.

[Jagpreet_Singh_]

@skatofiabah Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!