Character Limitation | Community
Skip to main content
simon_barnard
simon_barnard
October 16, 2015
Solved

Character Limitation

  • October 16, 2015
  • 2 replies
  • 14615 views

I wonder if anyone can help - 

We are currently using omniture data to feed several dashboard reports, however the link details showing in our omniture reports are being limited to 100 characters, rendering the report unusable. Is anyone aware if there is a simple non technical way of extending this character allowance?

    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 BrianAu1

    Hi Simon,

    There is not a way to extend the limits of a given variable type, but since you are passing data into a custom traffic (prop) variable and hitting the 100 bytes limit; if you use a custom conversion (eVar) you have up to 255 bytes. Please be aware the two noted variable types carry different utilization and allocation properties however. See below for allowable character limits:

    >>>
    https://marketing.adobe.com/resources/help/kb/en_US/analytics/using/allowable-characters-limits.html

    Many variables contain limitations to the number of bytes they can hold. A byte is generally a single character, however can take up to 6 bytes depending on the complexity of the character. Any variables that exceed these limitations are truncated:

    • PageName and all custom traffic variables (props): 100 bytes
    • Tracking Codes and all custom conversion variables (eVars): 255 bytes
    • URL and Referrer: 255 bytes
    • Hierarchy variables: 255 bytes total across all levels
    • Purchase ID: 20 bytes
    • Products:
      • 100 bytes for each product category
      • 100 bytes for each product name
      • No overall limit within the entire variable
    • Events variable: No overall limit, however each serialized value may only contain 20 bytes

    Best,

    Brian

    2 replies

    B
    Adobe Employee
    BrianAu1Adobe EmployeeAccepted solution
    Adobe Employee
    October 16, 2015

    Hi Simon,

    There is not a way to extend the limits of a given variable type, but since you are passing data into a custom traffic (prop) variable and hitting the 100 bytes limit; if you use a custom conversion (eVar) you have up to 255 bytes. Please be aware the two noted variable types carry different utilization and allocation properties however. See below for allowable character limits:

    >>>
    https://marketing.adobe.com/resources/help/kb/en_US/analytics/using/allowable-characters-limits.html

    Many variables contain limitations to the number of bytes they can hold. A byte is generally a single character, however can take up to 6 bytes depending on the complexity of the character. Any variables that exceed these limitations are truncated:

    • PageName and all custom traffic variables (props): 100 bytes
    • Tracking Codes and all custom conversion variables (eVars): 255 bytes
    • URL and Referrer: 255 bytes
    • Hierarchy variables: 255 bytes total across all levels
    • Purchase ID: 20 bytes
    • Products:
      • 100 bytes for each product category
      • 100 bytes for each product name
      • No overall limit within the entire variable
    • Events variable: No overall limit, however each serialized value may only contain 20 bytes

    Best,

    Brian

      E
      etaracila
      March 22, 2022

      hi Brian,

      I wonder what is the character limitation for context data variables? RE: https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/contextdata.html?lang=en

       

      Thank you

      cathyw49544988
      cathyw49544988
      June 27, 2018

      I have a about the length for URL. In the previous e-mail, it mentioned that:

      • URL and Referrer: 255 bytes

      But URL seems it is not available to user, correct? This is the reason I have to use a prop or evar to hold the URL. Is there a way to access the adobe default URL?

      Thanks

      Terms & ConditionsAccessibility statement

      Loading footer...