DTM Direct call inheriting variables set by previous rules

Avatar

Avatar

jerome_chevreau

Avatar

jerome_chevreau

jerome_chevreau

14-08-2015

Hi,

 

I have noticed that the Direct call has a "bug" as variables which are set on rules which trigger s.tl() persist and get tied up with my direct call rule (i.e. to fire a s.t()).

 

I have been battling trying to find an effective solution to try keep only the variables which are set on the template.

 

The above can be very challenging especially for end users who dont have any developer background. 

 

It would be great to have DTM be more strict in terms of taking the variables which have been set within the tempalte and the editor (i.e. under the analytics tab). If this cannot be done, another option can be to offer the functionality to 'clear variables' when setting up any kind of rules.

 

Thanks

Jerome

2 Comments (2 New)
2 Comments

Avatar

Avatar

mikethompson

Avatar

mikethompson

mikethompson

26-08-2015

This actually happens if you have multiple s.tl() calls on the page as well and are using the fill-in-the-form option. To get around it, we stopped using the form and have taken to writing custom code for all rules in which we clear out the variables before defining new values.  

 

It would be nice if the form option had a check-box option to clear all variables other than what you are setting.

Avatar

Avatar

jchuck5612

Avatar

jchuck5612

jchuck5612

11-06-2016

This limitation has bitten me a couple times and always on SPA's where I need to have link click tracking as well as page loads when the hash changes.