admin support for s.events
| Project: | Omniture Integration |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Clint,
I think we need to discuss this more. This issue is taken from the line item that says:
Adding the ability to define "s.events =" in the admin interface, very similarly to how you have crafted the taxonomy terms. For example, if a user could choose that "Submit Comment = event4" or "Submit Rating = event5".
I guess my concern is how the admin will actually control or effect these events? In order for event4 to actually be used, one would need to implement something like actions or workflow to set up an action when comments are submitted by users that populates s.eVar4 with something... the user name/anon? and then the admin could allow you to turn on this comment tracker feature. Similarly with the Rating.
So is this a number of new feature requests in reality?
1. track user comment submissions
2. track user rating usage
Can you clarify where you were going with this?
#1
Mmm, I guess what I'm trying to get at here is some system for tracking Drupal events. My thinking, in hindsight, was overly simplistic!
We need to figure out someway to set s.events for add comment, comment approved, add story/page, login, register, etc.
Different Omniture customers will likely use various events to track the Drupal events, because of this we need a flexible/dynamic way to specify which event gets set for the corresponding Drupal event.