Truncated URLs in a report (Entry Pages)

[gautier_lemesle]

Hi all,

First of all, thanks for allowing people to share comments/questions in regards to Adobe Analytics; it's really appreciated.

We have a client for which we're running into an issue as per reporting (display and gathering of data).

When we're using one of the default report (Entry Pages), our client website have URLs longer than 100 characters. Therefore, information being displayed are truncated in the middle of the URL with a format like : http://www.clientsample.com/en/this/is/grea...example.php

The problem is that when we're exporting this report, obviously, all URLs are truncated. I've noticed also that the hyperlink of all those URLs are not truncated. We've obviously tried to get a custom script to do a find and replace of all <a> values with their <href> values but there's something blocking us from modifying the page. Although this wouldn't have solved the reporting export problem, we would still have copy/paste information from the screen.

Also, to this point, we've noticed that not only this truncated issue is affecting the report display and data export; but also the advanced segmentation we might be doing. So, if an advanced segment is matching URLs with truncated parts, even if there's a match, those URLs will never be included in the report (display and data export).

So my questions are:

- I don't think I'm the only one facing this (the max 100 character limit for display); is there a plan to correct this?

- instead of generating a report on the values <a>, could you make the report generate itself from <href> values?

- as it's affecting the ability to create advanced segments, is there a plan to correct this?

If possible, I'm hoping for an answer that would be more broad than "ask your Omniture representative" or "ask your client to reduce URLs length". I think this is a serious problem and I would love to get this to be resolved.

Thank you all for your help and I'm more than happy to follow-up on this with Omniture folks through PM.

--

Gautier

[alison_smith · Accepted solution]

A workaround that might help for the time being might be to copy the URL into an eVar, which has 255 char limit rather than 100.  If you have Processing Rules certification you can do this easily without amending the site code.  Set the eVar expiry to 'page' to simulate a traffic prop, if desired.

I presume this URL report is needed for some specific reason, rather than the usual Pages report.  Typical practice would be:

- pass the Domain (www.clientsample.com) into the Servers report (s.server)

- pass the 'meaningful' part of the page name into the Pages report (s.pageName) e.g. en:this:is:great long string up to 100chars example

- pass any additional info, such as query string parameters, into other reports (s.props)