Thank you, @lelloba!
Your solution comes very close to what I was asking for but unfortunately it is not the right one:
Id page
1 /Page_a, /Page_c, /Page_e
2 /Page_b, /Page_c
3 /Page_a, /Page_b, /Page_d, /Page_c
The right solution (the sequence) should be as described above:
ID Sequence
1 /;Page_c; /Page_a; /Page_e
2 /;Page_b; /Page_c;
3 /;Page_b; /Page_a; /Page_d; /Page_c
I am out office and cannot look at my solution (no PC). I had probably used a group by with a sorted list. There should be another option so you can do what you want (set, unique concatenate, list (not sorted).
Hi @bruno29a ,
I deleted my previous post because the solution I proposed - see attached workflow - is not yet perfect (for example, when ID = “005” the result is “, a, b, c, a, d, b” instead of “, a, b, c, a, d, b, e, a”).
I tried your solution using the same data but unfortunately it goes in a loop…
Ciao
Alfredo
Hi @alfroc , forgive me for asking. I find this is interesting. But I’m simply curious as to what real case scenario is this for? Would you be kind enough to share? Thank you!
Hi @badger101,
I’m trying to analyze the path that every visitor of my website does, as you can see from the table obtained with DataStudio on Google Analytics data.
Ciao
Alfredo
Thank you @alfroc . That makes sense. I would love to help you out. Would be kind enough to export at least the portion you screenshorted above to a file? (I’m assuming you’ll be using Excel for that matter, which is fine by me). All I need is to have something to work with as an input (that resembles the pattern and format of the real data).
Note: I have also edited the name of this forum thread to ‘Website visitor pathway analysis’ so that others seeking for solutions in the future for the same kind of case will be able to find this easily.
Hi @badger101
Thanks for your help! I finally managed to find a solution that works for me as it fully supports reverse paths as well.
I renamed the workflow according to the name of this thread.
Ciao
Alfredo
Hi @alfroc , I’m glad you have found your own workaround, and thank you for sharing the workflow.
Forgive me, but I’ll have to say that the workflow you came up with has a nested loop which might not be so efficient when applied to large datasets. Plus, it looks fairly complicated to begin with, given a simple dataset that you have. It might work great for you, but it can be difficult for others to adopt it.
I was thinking of proposing solutions without loops, and in addition to that, I was thinking to add a special column summarizing the dataset for each unique pathway from the results.
But hey, as long as you’re happy with what you’ve got. Cheers!