Accepted Solutions (0)

Answers (1)

Answers (1)



Would this work?

Screenshot 2020-09-16 at 9.13.25 AM.png

@H_L - If the referring URL includes parameters or hash values beyond the pathname, would you want to include those in your segment (assuming all other criteria is met)?
No. Sorry forgot to mention, we give user's choice, they can choose any of the language/country combination, which means there are almost unlimited /us/en/, /de/en/, etc...
@evolytics_brian - emm, sorry I didn't get the point. what's the mean of "beyond the pathname"?
@H_L - I was referring to things like the query string (?) or hash (#). If you're filtering for a referring URL, and you want to exclude those from your criteria, you can't use "ends with" criteria. You'd have to use an option that specifies "contains" or "matches" instead. Though, you'll probably need to specify various values, for example: "/us/en/" OR "/us/en/?" OR "/us/en/#" OR "/us/en?" OR "/us/en#". Another option would be to update your data collection (implementation) to capture what you're looking for so creating a segment is much easier. For example, pull the {{loction}}/{{language}} value from the referrer and capture it in a prop as part of any necessary calls. Then your segment would just be "propN equal '/us/en'" and you're done.

@evolytics_brian, thank you for the further explanation. What we want, is to identify the traffic referred from respective country/language home page.

That's why we only want to filter out referrer from,  but don't want to include

And, there will "unlimited" combination of country/language, as said before, we give user freedom to access any of the combination, e.g. /us/ja/, /br/ko/, /jp/br/, so it's nearly not possible to input all the values one by one.

The way you mentioned to implement, sorry I am not sure can make it or not.


But we used another way, exported all the referrer, counts the length, and filter. As all the contains same count of charaters and starts with same domain 😉


Thanks again for your inputs.