This code sample show one method of checking that events are firing as expected and that your third-party analytics solution is picking up the events that have fired. It does this by creating a global variable for each event that serves as a counter that increases incrementally each time the event occurs. You can then check the value of this variable in your browser console.
ATGSvcs.rules.analytics.launch({'poll-delay': -1,
'eeTransactionCompleted': function(e, data) {
window.eeTransactionCompleted = (window.eeTransactionCompleted ?
window.eeTransactionCompleted : 0) + 1;
},
'eeOffered': function(e, data) {
window.eeOffered= (window.eeOffered ? window.eeOffered : 0) + 1;
}
});If you find that the analytics code is loading and events are firing as expected but you are still experiencing problems, it may be that the analytics code is loading after certain events have already occurred. You can instruct the analytics code to search the logs for events that occurred prior to the analytics code loading. Further details of how to do this are in the code sample in the Act on Event without Polling Server section of this document.
