Activity Map link value getting truncated at 128 characters | Community
Skip to main content
Level 2
September 27, 2024
Question

Activity Map link value getting truncated at 128 characters

  • September 27, 2024
  • 2 replies
  • 4459 views


We have observed that link under activity map is limited to 128 characters while capturing in network call where as the database limit is 255 characters on Adobe
1. what is the max character length for link under Activity Map?
2. Is there a possibility to increase its length under Admin or anywhere else?

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

2 replies

bjoern__koth
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 27, 2024

Hi @manoj_katragadda 
that is a very good question. Since this information is transported as context data, I was trying to find hints on this in the documentation, but could not.

 

https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/page-vars/contextdata

Also another thread where this final question remains unanswered

 

@jennifer_dungan@brianau1  anything you can add to this?

Cheers from Switzerland!
Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 27, 2024

I just checked, I am getting the same limitation... 

 

The old documentation for "allowable character limits" no longer seems to exist (assuming it even contained context variables / Activity Map)...

 

I've reached out to an Adobe contact who handles a lot of the documentation to see if we can get some clarity... 

 

As it stands, I don't know of any settings to adjust length (and since no other dimensions have anything I suspect it's "what you see is what you get")...

 

It would be nice if we could get the full 255 character length....

Gigazelle
Adobe Employee
Adobe Employee
September 27, 2024

What's the exact value that you're seeing getting truncated?

The hard limit is in bytes, not characters, so if you're using multi-byte characters, the total length will be notably smaller.

There's no limit to what context data variables can hold, since they are not stored in any data tables; processing rules place a context data value into a variable, and the variable that it is placed into is what has its limits.

There is no way to increase storage capacity for any variable. They are hard limits based on Adobe's data architecture.

Level 2
September 30, 2024

We have received a response from Adobe support and this is how the reply went. The gist is, yes its capped at 128 characters and cannot increase. If we want more characters to be captured it is recommended to send te data to custom eVar that can handle 255 characters.

 

"Activity Map link in the Activity Map code, there is a limit set to capture the data, which is capped at 128 characters.

You can see this in the code snippet:

["a.activitymap.link"] = 128 < n.length ? n.substring(0, 128) : n;

Now, even if we want to capture the data completely without truncation, you need to capture it in an eVar. The Activity Map data will be captured as context data and will automatically map on the backend.

Therefore, the only option to capture the Activity Map link is by firing the same data that's being captured in the Activity Map link into an eVar. Since eVars have a length of 255 characters, there will be no truncation.

This is a custom implementation that needs to be done on your end, as we will not be able to assist with the custom implementation. However, the only workaround to capture the Activity Map link completely is to capture that in an eVar whenever the Activity Map link is fired in the server call.
"

Gigazelle
Adobe Employee
Adobe Employee
September 30, 2024

When I read your reply, I was actually in a bit of disbelief - my thoughts were, "there's no way that AppMeasurement would do that, that has to be some sort of custom implementation thing". So, I open up a copy of AppMeasurement, and sure enough, it is in fact getting truncated right there!

I reached out to one of our AppMeasurement developers regarding this thread, and their first impression was that it was a bandwidth optimization, implemented back when image request length mattered significantly more.

I'm finding out if there are any repercussions of modifying the activity map code to truncate at 255 instead of 128. If you want to try that on a development report suite, you're more than welcome to!