Hello,

My customer Telefonica Uruguay has raised a feature improvement with me.

The use case is as follows:

He tried to create a new custom tracker based on datalayer fields. One of these fields was very long - a long URL containing several query string parameters-.

He used "equals" and copied the exact url.

He thought everything went smooth, because no errors or warning were given, however the report that was using this custom tracker was stuck at zero.

After reviewing, my customer found out that when copying the long string in the custom tracker definition, our field has a maximum length, and the tool automatically cuts all the characters after the limit.

This can be easily missed (as it was the case here) because no error or warning is displayed to the user.

Of course, it can be bypassed by using regex or contains, but the thing is that if the user selects equal, this can go unnoticed very easily.

I was able to reproduce by simply trying to save this custom tracker in my sandbox:

When saving, the tool cuts after the limit, and the "22222" part of the string is removed from the tracker, therefore it will never be matched --> we will always show 0 in the reports.

Can we increase the limit of the field, or at least display an error or warning message to the user?

Thanks in advance,

Enrique