track over 255 characters | Community
Skip to main content
-
-Stef-
January 13, 2023
Solved

track over 255 characters

  • January 13, 2023
  • 2 replies
  • 2304 views

Hi,

our URLs are longer than 255 characters because of various utm descriptions included. Do you have any ideas on how to track the complete URL?

I think a list evar is not useful because its purpose is to split up the content into several parts...

Regards

Stefanie

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by nilotpal

Hi @-stef- PageURL or eVars in Adobe Analytics have a size limit of 255 bytes, hence for any pageURL longer than that, we can consider using two eVars (assuming 255 bytes should be sufficient for pageURL+path; and another 255 bytes for the query string parameter) 

  1. capture page URL and path in eVarX= window.location.hostname+window.location.pathname (reference)
  2. the query string parameters in say eVarY=window.location.search 

You can then use the combination of eVarX and eVarY through data feeds/warehouse to meet your use case. Otherwise, there is not out of the box solution to capture more than 255 bytes under any dimension.

 

2 replies

P
Pankaj_Sabharwal
Level 5
January 13, 2023

Hi @-stef- 

 

The pageURL variable (g) in Analytics has a limit of 255 characters/bytes.

 

The first 255 characters of the URL are passed along in g. If the URL goes beyond 255, it is captured in -g. This has a limit of 2k bytes.



This might helps:  Page URL 

 

Thanks



    nilotpal
    Adobe Employee
    nilotpalAdobe EmployeeAccepted solution
    Adobe Employee
    January 15, 2023

    Hi @-stef- PageURL or eVars in Adobe Analytics have a size limit of 255 bytes, hence for any pageURL longer than that, we can consider using two eVars (assuming 255 bytes should be sufficient for pageURL+path; and another 255 bytes for the query string parameter) 

    1. capture page URL and path in eVarX= window.location.hostname+window.location.pathname (reference)
    2. the query string parameters in say eVarY=window.location.search 

    You can then use the combination of eVarX and eVarY through data feeds/warehouse to meet your use case. Otherwise, there is not out of the box solution to capture more than 255 bytes under any dimension.

     

    Terms & ConditionsAccessibility statement

    Loading footer...