Filtering referring domain table or panel based on URL (ending)

[Sean54]

Hi There, 

i have a website that has english and Spanish pages. 

So different pages on the site have different URL endings. 

i would like to be able to filter a table for referring domains to be able to see the referring domains going to Enlish pages e.g., /EN, or to Spanish pages e.g., /es NOTE: Referring domain table doesnt allow "advanced filter" to include or exclude by URL so cant do this way..

Know theres somebody our there that can help - any thoughts welcome. 

Thanks a mill. 

[Jennifer_Dungan · Accepted solution]

While the URL is captured into Adobe data, the URL generally isn't available for Workspace unless you have a separate eVar set up for it. Also, if your URLs exceed 255 characters, the language part of the URL could be susceptible to truncation.

There are some other factors to consider.. how many unique URLs you have, especially if you capture them with your campaigns, could push them over the default 500,000 unique value limit in Workspace, which will cause the URLs captured beyond that to be collapsed under "(low traffic)" which also means a segment based on the URL won't capture those pages.

You could however set up Classifications on the eVar holding the URL, since this is processed, it won't have an issue with unique values.

-----

We have a few sites that are multilingual (English / French), and I actually have a prop set to track the language there... then it's basically a prop that holds two values. This makes it easy to use as a breakdown, or to drag into columns to see the variations side by side, or to create segments on.

You could set up something similar...  This can be done in a few ways. You could use Adobe Launch to create custom code Data Element that looks for your language key in your URLs, and assign the value of "english" or "spanish", then set this into a new "language prop" (I would make sure to set this on all pages AND all actions - so that you can also tell clicks / successes / interactions / etc by language as well).

Or you could use Processing Rules to check if the URL contains your language key, and set the prop that way.

-------

Whichever way you choose, you will need either an eVar to hold the URL, or a prop/eVar to hold specific (I choose prop, since I don't need the 255 character limit or custom expiry of the eVar, but there is nothing wrong with using an eVar). 

If you already have a URL eVar, you could start with Classifications, that way you can process up to 6 months of data so you can start using this right away.

----

When you set up you segments, based on any of the above methods, you really just need two Hit Level segments, where the eVar, prop or classification is either "english" or "spanish", then you can pair it with any report (referring domains, or otherwise).