@KRAZ @Stewart_Schilling Between the help of you both my rule efficiency just went up tremendously. Thanks! Multiple direct calls in events > setting evar as %event.identifier% in UI; gets me exactly what I needed! What normally would have been 4 separate rules is now 1, and that's just for one re...
@keithb81089125 I could use help on setting the custom code to assign the descriptor to my eVar. We are adding a particular descriptor in the class for a button so I'm thinking I could put in the custom code var eVar26 = this.getAttribute('class') Then in AA Set Variables would I put my eVar26 Set a...
I'd like to use this method on a rule. What would be the best way to set this event element attribute as an eVar? Would I need to use a custom code? @Stewart_Schilling
Were you able to get the event identifier to populate as a eVar? I'm wanting to do what you mention in the initial question, but I'm not quite following to your end result.
We launched our gtag implementation and it has worked without issue. What's different in our scenario is we are just sending to one Google Tag account for one domain.I would recommend that instead of trying to do the conditional send after running the rule, to instead use two different Adobe tag rul...
One thought: Regarding the double page views - Are you launching gtag on a global page view and pushing tags through individual rules? When configuring, it seemed that the global tag as a separate rule is unnecessary and when running a rule it will initiate both the global site tag and the rule pixe...
Thank you, this is helpful. I look forward to reading: "I will post article about auto-tagging that we have implemented on our side using #3, which I think is the best solution in terms future proofing your implementation."
We have been implementing several rules using a direct call of satellites. Would it be better in launch to use the Core-click with a css identifier? Is there a key difference in performance of the two?