Thanks for the response. I am just checking to see if there are any best practices. We are using SharePoint as a shell for our Intranet and I am questioning the most effective way to capture page levels, click events etc... as well as the best way to capture the data in general as far as the data object.
Hi James and Joseph,
We are currently switching from SharePoint to Adobe CQ5 but here are some general tips that I would suggest:
- Be sure to have SharePoint, your CMS system, be configured so that you can tag as many variable attributes on a page level consistently as possible including things like: page name, channel, section, type of page, keywords, etc. This is will allow you to assign variables to your data object on the page easier and is extremely valuable in Site Catalyst implementation because you can break down behavior like no other. In the future, this will allow you to integrate future products such as displaying custom content by utilizing the keyword fields. Setting the foundation and capturing as much information is important. I find that if you just capture the variables you want now, it will be a struggle getting IT to re-implement additional page level tags and you would likely have to rely on using extensions.
- Through talks when we met at Tealium Conference in SD Joseph, you mentioned that connecting online data behavior with the specific customer is important. I would be sure to include a GUID field (either generated from Tealium or internally) and a customer ID field so that when the customer logs in, you can identify their activity prior to login and moving forward. Keep in mind this is assuming that the customer ID does not include any customer information of course. Doing this and a few other tweaks in cookie persisting, you can have a full view of activity of each customer.
- For click events, I am assuming you want to capture things like form submission data along with the action that they clicked on the "submit" button. There are a few ways you can do this but ultimately, you would need to utilize a "utag.link". In the utag.link, you can have form field data be passed and set your click event function. Here is a quick example:
form: "financial advising inquiry", [form indication]
typeofservice: serviceType.toLowerCase(), [capture field]
investmentrange: investmentRange.toLowerCase(), [capture field]
date: date, [capture field]
event: "event10", [indicator to fire an event to site catalyst. Must be mapped in tag]
link_text: "financial advising inquiry" [naming your site catalyst link name. You can also set this up as an extension or tag mapping]
Depending on how you want to use Site Catalyst to answer your business questions, the example above can change.
Are these suggestions in the realm of what you were looking for? There are other implementation methods and suggestions but I want to make sure I am heading in the right direction in answering your question.
Thanks for the response. We are actually using SharePoint for our Intranet. There won't be much need for capturing form-related data initially but there may be at some point in the future. For now we are looking at the basics: capturing page structure and forming a friendly page name. In that regard we are considering capturing the url behind the breadcrumb and building a page name off of that. We would use the _spPageContextInfo.webServerRelativeUrl (output some like this) = /humanresources/mycareer. Any ideas there?
We will want to be using the utag.link call for all clicks that occur on a page that are related to events other than another page view such as a download. Also, we need to look in to whether or not we can capture the user name (this may be acceptable considering this is an internal site). If not we may need to generate a unique identifier.
Any other recommendations along these lines?