この会話は、活動がないためロックされています。新しい投稿を作成してください。
この会話は、活動がないためロックされています。新しい投稿を作成してください。
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..
解決済! 解決策の投稿を見る。
表示
返信
いいね!の合計
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.
表示
返信
いいね!の合計
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.
表示
返信
いいね!の合計
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.
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
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.
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
@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..
表示
返信
いいね!の合計
表示
返信
いいね!の合計
@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.
表示
返信
いいね!の合計
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 .
表示
返信
いいね!の合計
表示
返信
いいね!の合計