Page URLs with double slashes under Workspace

[jantzen_belliston-Adobe]

Hi,

We are able to see different version of URLs. In workspace,

Example: www.example.com/home.html > proper one

we also able to see www.example.com//home.html (with double slash because of Typed/Bookmarked dimension majorly. Some traffic from referring domains too. It not only displaying for home page. It is coming for category and sub category pages too. 

NOTE: Adobe image request/call is happening even with double, triple, infinity slash for all the page in the website. So that we able to receive data to ADOBE workspace with different version of URLs for same page.

I hope, this can be avoided by configuring under DOMAIN level going forward. Example kind of 301 permanent redirection or any other URL structure setup. Please let us know whether I'm on the same page or is there anything can be done under tool end too. I hope CMS- domain level change is pretty straight forward to avoid this type of issue even with other tools.

Thanks!

@yuhuisg can't paste the screenshot as this for customer. I can say

Page URL (Prop 2)

https://www.example.com/home.html 

https://www.example.com//home.html

https://www.example.com//category.html

https://www.example.com/category.html

its coming irrespective to the variables. If you drag this under Page Name Evar, that time also you get these URL's

I investigate where this comes from, it mainly referring to typed/bookmark. I hope it can be rectified using permanent fix under the domain level. By doing redirection etc..

[jantzen_belliston-Adobe]

Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?

[jkm-disco · Accepted solution]

Hi @prathap08 ,

This is a hack, but if the bad data is already collected you could clean it up using a classification.

That is, for each domain, create a Path variable and define it using classification rule builder similar to the following:

\/*([^\?]*)\??.*$

 Mapping $1 to the new variable.

[jkm-disco · Accepted solution]

Hi @prathap08 , this is also a work around, but give you better data going in. Try manually reformatting the text in custom code.

E.g. 

s.registerPreTrackCall(function(){
s.prop2 = s.prop2.replace("\/\/","\/");
});

Or, if you are using context data/pagename it would look similar with the corresponding variable.

This doesn't address the issue, but would probably be a fast solution.

[prathap08 · Accepted solution]

@jkm-disco Thanks mate. I'm little conscious to touch under existing implementation. Also, I want to give permanent solution even they under any other page traffic provider analytics platform. So providing the suggestions to implement under the domain level rather in adobe analytics alone. Is this make sense?

[jkm-disco · Accepted solution]

Makes sense, it's probably worth finding a permanent solution. However, if you are going the re-direction route, you'll need to do a check on each page to not fire a beacon unless the double "/" are absent. Best of luck.

[prathap08 · Accepted solution]

@jkm-disco Yes mate, I got your point I guess. You mean, that we need to do for all the pages in the website to redirect if double/triple etc comes, it should redirect the respective correct page. I hope there is a solution to rewrite for all the pages in the domain level.

[#8]

Hi @prathap08 ,

If you are setting it into prop2 with document.location.href you can use the following javascript to set the variable:

s.prop2 = document.location.href.replace(/([^:])\/\/+/g,"$1/");

 This will replace every instance of repeated "/" unless directly following a ":".

Note: If you are use to using the normal "Set Variable" action, and if this is being used for click tracking, and if you go with this custom code option, be sure to update s.linkTrackVars .

[prathap08]

What URL dimension in your reports?

In my case, I track the page URL to a prop. When I broke down the Referrer dimension by that prop, I got the correctly formatted URLs. When I report on the prop itself, I also get the correctly formatted URLs.

[prathap08]

Yes mate, same way configured in the prop. Not specifically to referrer that I'm facing. It's coming irrespectively to the any dimension. I guess, the way the URL structure built is allowing extra SLASH by the way image request is happening. Specifically I can say, it all coming from TYPED referrer. We are seeing the data under the PAGE URL dimension. Please correct me if m wrong.

[yuhuisg]

@prathap08 it sounds strange that you encounter this problem of double slashes "//" in your prop's values only with the Typed/Bookmark referrer. If that is really the case, then it sounds to me like a bug that Adobe should fix. I suggest opening a ticket with Client Care for them to investigate and resolve.

[prathap08]

@yuhuisg: yes, its a prop. Its not only with typed/bookmark. Even you drag and drop. Page URL( Prop 2). It will give one URL with proper URL slash and another one with double slash. I'm seeing call is happening when we tried sending the image request with double slash. Is it something we need to correct rather than connecting adobe client care? as I said earlier, kind of any re-direction to be done across the website pages? Thanks

[yuhuisg]

@prathap08 could you edit your original post to show screenshots of some example reports where you see the double-slash discrepancy?

[prathap08]

@yuhuisg can't paste the screenshot as this for customer. I can say

Page URL (Prop 2)

https://www.example.com/home.html 

https://www.example.com//home.html

https://www.example.com//category.html

https://www.example.com/category.html

its coming irrespective to the variables. If you drag this under Page Name Evar, that time also you get these URL's I investigate where this comes from, it mainly referring to typed/bookmark. I hope it can be rectified using permanent fix under the domain level. By doing redirection etc..

[yuhuisg]

@prathap08 can you show how your Prop2 is being set in AA? e.g. is it s.prop2 = document.location ?

[prathap08]

@yuhuisgsorry for the late response. Yes mate, through data layer. Prop 2 set up with > "destination UR"L: document.location.href under the pages and Rule set up with DOM ready and the variable set it to PROP 2 calling out with respective data element.