One of the issues we are having is getting page names to show correctly. The current implementation is actually been set to attempt to create page name by parsing the URL. What is the consensus or best practices for collecting page names? Can the implementation be set up to collect page name from meta title within the web page HTML?
Hi @JohnRog ,
The standard way of implementing pagenames is getting the values from the html title tag or from data layer (if available).
Using the title tag to get the pagename value is the most common way.
To use title in Adobe launch implementation, all you need to do is:
> Create a data element
> Select Data element type as "Page Info"
> Select Attribute as "Title"
This will get title value in a data element which you can then use in any eVar or prop.
Before implementing the above solution, be sure to check if the page code contains <title> tag with respective page name info.
Hope that helps !
The page name field in Adobe Analytics is a free-form field. That means it can accept any string that you pass to it. I believe this was decided waaaaaay back in the early Omniture days to give clients the flexibility of what they defined as a "page name". It will only use the page URL if you omit the "pageName" field in your Pageview s.t() beacon. (On the other hand, Google Analytics has standardised on the page URL as the preferred page name.)
The recommendation from Adobe has always been to define your own standard. Of course, the easiest is to parse the URL since the URL is supposed to be permanent. Some organisations have chosen to always define their own page names regardless of the URL or page title or other parts of the page. And then there are some, like you, who use the page title, assuming that it is permanent too.
Whatever method you use, I think the main consideration is "permanence". This will ensure that you're able to compare historical page reports reliably without needing manual manipulation, e.g. if a page name has been changed over time.