Client-side
This method tracks user interactions by executing JavaScript in the user's browser. This is easier to implement but relies on browser-based tracking (cookies, scripts). You can opt for this when you require a quick deployment or when server-side tracking is not feasible. However, its reliability can be affected by factors such as ad blockers, disabled JavaScript, or cookie restrictions, which may prevent tracking data from being collected accurately.
Prerequisites
- The steps mentioned in this page must be performed by a JavaScript developer or someone with technical programming knowledge.
- Ensure the correct {region} and {hostname} values are used in the script URL.
Activate tracking
- Add the base tracking script to the <head> section of the page where tracking is required:
<script type="text/javascript"
src="//{region}.production.ai.zephr.com/{hostname}/SiteScript.js" async></script>
- Implement event tracking with predefined payloads.
For each onsite action that needs to be tracked, implement the corresponding script/payload as shown in the table. Use the following action values as a reference when you are setting up these scripts, to ensure you are tracking the correct event:
| Type | Action Value |
| Page Load | 21 |
| Paywall impression | 44 |
| Registration wall impression | 43 |
| Paywall click | 28 |
| Registration click | 70 |
| Paywall conversion | 151 |
| Registration conversion | 71 |
| Scroll | 46 |
| Hard/Fixed Paywall impression | 51 |
| Meter impression | 41 |
- Test in your staging environment. Zuora recommends integrating and testing these scripts in your staging environment before deploying them to production. This setup is typically a one-time integration that enables seamless ongoing tracking.