Intempt
  1. Installation
Intempt
  • Installation
    • Basic Intempt Installation
    • Create source
    • Web Snippet
    • Google Tag Manager
    • Autocapture setup
    • SPA tracking
    • Environment Setup
    • Validating Installation
  • SDK
    • JS SDK
    • Android SDK
    • iOS SDK
    • Node.js SDK
  • API Reference
    • Track data
      POST
    • Consent
      POST
    • Choose API
      POST
    • Recommendations Feed API
      POST
  • Data Ingestion & Tracking
    • identify()
    • track()
    • record()
    • alias()
    • group()
    • consent()
    • intempt:html / intempt:page / intempt:session
    • Product Catalog Ingestion via API
  • Data Models & Event Schema
    • Event Schema Overview
    • Required Fields
    • Attribute Schema
    • Product Catalog Schema
  • Webhooks
    • Webhook Configuration
  • Server Side Experiments
    • Overview
    • Choose API endpoint
    • Handling Experiment Response
  1. Installation

Validating Installation

Validating Installation#

After installing Intempt on your website, app, or server, you should verify that events are being sent correctly to Intempt’s ingestion layer. Intempt processes events in real time, so validation can be done within seconds of triggering actions in your product.

Real-Time Event Availability#

Intempt is built to ingest, store, and analyze events immediately.
When an event is triggered from your implementation:
It reaches Intempt’s ingestion servers within seconds
It becomes queryable for analysis almost instantly
It appears in the Live Data Feed inside the project
This real-time behavior is powered by Clickhouse, which stores recent events in a fast row-oriented format and historical events in a time-partitioned columnar format.

What to Look For in the Live Data Feed#

To validate that your installation works:
1.
Trigger an action on your site or app (page load, click, form submission, etc.)
2.
Open your Intempt project
3.
Navigate to the Live Data Feed
4.
Confirm that new events are appearing in real time
Each event includes:
Event name
Timestamp
A unique identifier
masterID (entity performing the event)
Event properties (JSON)
If events appear here, your installation is working correctly.

How Intempt Receives Your Data#

Intempt’s data ingestion layer supports multiple tracking methods:
JavaScript SDK for websites
iOS SDK and Android SDK for mobile apps
Node.js SDK or REST API for server-side events
All sources send data into the same ingestion pipeline.
If any of these sources are configured correctly, their events will be visible in the Live Data Feed.

Client vs. Server Events During Validation#

Both types of implementations can be used for validation:

Client-based (JavaScript, iOS, Android)#

Best for verifying direct user interactions
Ideal for checking autocapture or UI-driven events

Server-based (Node.js, REST API)#

Best for validating secure or backend-triggered events
Ensures events are not blocked by browsers or ad blockers
We recommend validating both client and server events if your integration uses a mix of tracking methods.
Modified at 2025-12-03 10:38:25
Previous
Environment Setup
Next
JS SDK
Built with