since ‎09-10-2017
‎16-01-2021
clintg36
Level 1
Re: Lowercase D=g
Avatar

clintg36

clintg36
- Dynamic Tag Management
Thanks for confirming that it is working for you stewarts16448458 and thanks for the helpful suggestions to everyone.

Views

624

Like

1

Replies

0
Re: Lowercase D=g
Avatar

clintg36

clintg36
- Dynamic Tag Management
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 representation.

Views

500

Likes

0

Replies

0
Re: Lowercase D=g
Avatar

clintg36

clintg36
- Dynamic Tag Management
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". N...

Views

497

Like

1

Replies

0
Lowercase D=g
Avatar

clintg36

clintg36
- Dynamic Tag Management
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 url?Thanks!

Views

1.6K

Likes

2

Replies

10
Page Load Fires, No Beacon
Avatar

clintg36

clintg36
- Dynamic Tag Management
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 fires exactly...

Views

515

Likes

0

Replies

1
Likes given to