example implementation of hook_omniture
| Project: | Omniture Integration |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
I suggest we include a sample omniture.inc with the following componants:
The following settings should be controllable from the admin:
Track Download Links
Track External Links
Track Inline Stats
Link Leave Query String
Check off extensions of Download File Types
Enter Internal Filters
Enter linkTrackVars
Enter LinkTrackEvents
Enter your campaign variable to tag SEO query links with:
Enter your visitorNameSpace variable.
Enter any plugins you will be using.
We shuld also include some documentation in the README about the s_code_remote_h.js which users who are new to Site Catalyst might not think to put on their check off list.
Also, is it convention to store .js files that are module specific with the module? How do we bring the s_code.js in when we want and not have Drupal do it automatically?
#1
let's go one step at a time ;)
First step is deciding if we like the omniture.inc system or want to use a hook http://drupal.org/node/182201
We can discuss all these other things in another issue (i.e. conversation flows best with one problem per issue).
#2
Given the proposed hook idea in #182201: replace omniture.inc system with hook_omniture_variabless changing the title.
#3
given the frequent updates to the s_code.js file, it would be better to simply use a form control to update or write over a file once the developer customizes and configures the new s_code version