There are multiple types of metrics and approaches for creating them
|Metric Type||Description||Scope||Typical Use||Notes|
|Standard||Triggers on proxy based traffic flowing through SiteSpect. Generally considered the most accurate compared to client side script based metrics.||Managed by SiteSpect||Page, API traffic, Form Submit, Click Through, Referrer||Works in the same way a Search and Replace Variation works with Triggers. (a)|
|EventTrack||Client side scriptable way to trigger a metric. Requires two parts; the script call SS.EventTrack.rp('mymetric'); and the receiving metric in SiteSpect.||Managed by SiteSpect or added by Customer code base||SPA page, browser events such as hover, click, and scroll.||SS.EventTrack.rp() can be declared using SiteSpect of by the Customer's managed code. Note: requires the dependency of the SiteSpect library core.js. (b)|
|Engine API||Client side scriptable way to trigger a metric. Requires two parts; the script POST and the receiving metric in SiteSpect.||Managed by SiteSpect or added by Customer code base||SPA page, browser events such as hover, click, and scroll.||Since this uses Engine API, triggers are ignored - it only references the metric by ID. Has no library dependencies, does not require Engine API to be enabled. (b)|
a. Requires traffic to route through SiteSpect.
b. Can optionally be used on pages that do not route through SiteSpect.
The reality is that we often use a combination of these approaches for metrics based on use case and site architecture. Any of these options can be implemented by either the SiteSpect Professional Services Team or on your own. But please consider using a few of your bundles services hours to sync with us to best help plan out optimal approach based on your site and goals.
If you are interested in pushing campaign data from SiteSpect to another application during user sessions, please see information on WATTS.