Thanks Gigazelle, that was exactly what I was hoping to avoid. But it
sounds like that is my only alternative. I appreciate the confirmation.
Would be nice if when launch comes around we had a "D=gl" or a "d=g" or
something to give us this functionality without losing the minified
Thanks for responding Jantzen,I was hoping not to have to transmit and
convert the whole url for each time I reference the url. I would like to
have the advantage of using the D=g shorthand, but have the result
turned all lowercase when the D=g is converted into a url on the Adobe
server end. Certainly I could store the URL in a data element and force
it lowercase there using DTM or custom code, but then I have a number of
large URL strings in every beacon call instead of a quick simple "D=g".
Hi, I am sure this isn't a new question but I can't find it anywhere in
the forums.I am using 'D=g' in multiple places in our reporting to get
the url, we are having a problem however with URLs where one customer
enters upper case characters and another customer enters lower case
characters. How can I force the results of 'D=g' to be either upper or
lower case without replacing 'D=g' with a data element that holds the
Greetings. I have an issue that has been plaguing my co-workers and I
for a couple of days. I have a specific page load rule where the page
load is firing, I can see in the debug log that it is firing.
Additionally the custom code for the page rule fires. Using some console
statements I can see that at the point of the custom code execution all
of the props and evars have been correctly set, but the beacon is never
sent.I can add an s.t() call to the custom code and then the beacon