Data tracking deployment

AI Paywall tracks user interactions, including page views, scroll, paywall, and other component impressions, clicks, and conversions. This tracking helps Zephr manage content access, enable AI model learning and decision-making, and deliver user analytics and insights effectively. The AI Paywall tracks the following events:

• Page Load Events - When a user visits a tracked page, the system records the article URL, referral source, and any agreed-upon additional data.
• Paywall and other Component Events - This is triggered when content access is restricted (or other experiences are shown) due to user behavior or subscription rules.
  • Hard Paywall: The user is completely blocked from accessing content due to a business rule, typically requiring a paid subscription.
  • Registration/Paywall: The user reaches their free content limit and is prompted to either register (by providing an email) or purchase access.
  • Metered Offers & Promotions: During the user journey, special offers related to content access or other products may be presented.
• Click Events - This is triggered when users interact with specific elements.
  • E-commerce Click: When a user clicks from an impression to the checkout page. This may be from a paywall or another offer.
  • Registration Click: When a user submits their email to sign up.
• Conversion Events - This is triggered when a user completes a key action that signifies a successful outcome, such as a purchase, registration, account upgrade, or subscription. Conversion events are critical for tracking the effectiveness of paywall strategies and promotional campaigns.
• Other Events - The same event tracking system can be used for additional actions like login, logout, and custom events. AI Paywall offers an extensive library of event IDs with a fully configurable payload. You can contact your onboarding or account manager for more details.

The event tracking can be done in two ways:

• Client-side tracking - Relies on JavaScript execution in the user's browser to capture interactions and send data via cookies and scripts.
• Server-side tracking - Tracks user interactions by directly sending data from the server to an endpoint.

The difference between client-side tracking and server-side tracking is listed in the following table: