Persistance issue with SiteCatalyst events set via JQuery onHandler

[rohan_kapoor]

I'm having a couple of issues with the jQuery onHandler when using the SiteCatalyst events (s.events) variable. The onHandler first of all fires two extra events which shouldn't populate when I click on the button in question. The second issue is that other outgoing links immediately clicked on (leveraging automatic exit links) also fire the same events as the first event. This is inflating the overall Page views on the event in question and also other events which are firing in the same visit. PS: I set a 'true' value when firing the main event and map it to SiteCatalyst and I set the other two events to 'false'. This doesn't seem to fix the issue. It would be great if you could add an option to insert attachments so that I could share my use case. Thanks, Rohan

[rohan_kapoor]

Sorry for the type, I meant persistence

[walter_gold]

Hi Rohan, We'll have someone get in touch with you about this. For future reference, "cases" can be filed directly from the User Interface using the blue [Support] button in the top right. This option allows users to upload attachments and sends the case details directly into our Enterprise incident tracking system(a completely separate system). It also provides us with the Account / Profile & your username so that we know all the relevant information and can review the specifics of the situation. Lastly, this allows our Account Management teams to track, analyze, and report on the types of cases and concerns our users have so that we can improve our service in the long term. This learning community is mostly intended for users to share and source ideas about product usage. A "hive mind" for best practices and anecdotal research for our user base. You may see other customers offer their solutions or tips around your post so this may still be a valid option for you. I just wanted you know that we have another environment where "cases" are filed so that they can be properly resolved to mutual satisfaction.

[rohan_kapoor]

Got it Walter, I currently have two different Tealium accounts which caused this. I'll make sure to post the future questions from the right account. I've attached a screenshot for this question now, Thanks!

[rohan_kapoor]

Any update on the this question?

[Clint]

Melissa is going to reach out to you directly on this.

[rohan_kapoor]

Thanks Clint, Son Hoang reached out to me and it looks like the issue will be fixed. We can close this off now. Thanks!

[son_hoang · Accepted solution]

Just as a comment for other people that might be reading this question. Please note that whenever you call utag.view() or utag.link() (e.g. using an onHandler extension to do 'event' tracking), that not only will the applicable tags fire, but all the All Tags extensions, tag specific extensions will too. This can cause any values set in your onHandler extension to be overwritten causing confusing behavior. This can be a bit difficult to keep track of especially if you have a lot of extensions or custom JavaScript Code extensions overwriting values without checking if they already exist.

[rohan_kapoor]

Thanks Son!

[son_hoang]

You're welcome, thanks for your patience on this issue.