Hi all,
I have a weird situation in that when I am setting variables in a Launch rule, only one of them actually works properly (eVar70 in this case). The other ones (eVar7, event16, event60) do not. This is all being triggered as an s.tl() to avoid additional page views.
Is there anything I'm missing here, or is there some sort of bug in Launch that is causing this issue?
On the surface, this looks fine.
Do you have any custom code in your extension that could be overwriting the values to null? Or are you setting s.linkTrackVars manually anywhere that would override these props and eVars from being set into this parameter for tracking?
In the old school days, for an s.tl() call, you would set your s.linkTrackVars with a list of all the parameters you wanted to be included in the tracking call (since you would still have all the page level params still set on the page, and you would want to curate specifically what was being sent).
In Launch, this value is supposed to be set dynamically based on the props and eVars you have configured in your set variables. However, technically, you can still set your s.linkTrackVars manually, and if done incorrectly it could be causing the issue you are experiencing...
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.