Intempt
  1. Data Models & Event Schema
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. Data Models & Event Schema

Attribute Schema

Attribute Schemas#

Intempt uses a unified customer data model powered by attributes.
Attributes allow Intempt to store, merge, and update all user- or account-related information collected from multiple sources.
These attributes are what make personalization, segmentation, and engagement possible across all GrowthOS tools.

What Are Attributes?#

Attributes are pieces of information attached to profiles (users) or accounts.
They represent stable or evolving properties of an entity — for example:
User’s email
Phone number
Subscription tier
Country
First seen / Last seen
LTV
Custom business fields
Product usage summaries
Attributes are populated through:
SDKs
REST API
Cloud sources (Shopify, HubSpot, Stripe, etc.)
Real-time events (Flink pipelines)
Profile merging logic

Why Attributes Matter#

Intempt gathers data from multiple sources and merges them into a single customer profile using advanced identity resolution.
Attributes are the output of this unified model.
Once attributes are created and populated, they power all GrowthOS modules:

Discover 🎯#

Analyze, explore, and segment users based on their attributes.
Predictive models, behavior tracking, and cohorts reference these attributes to surface insights.

Engage 💬#

Use attributes to:
Personalize journeys
Trigger automated flows
Send tailored messages
Apply privacy preferences
Build cross-channel experiences

Optimize 🛠️#

Attributes feed:
Experiment audiences
Real-time dashboards
Performance diagnostics
Reporting metrics
Attributes make GrowthOS function as a single consistent data layer.

Intempt Infrastructure Behind Attributes#

Intempt’s attribute engine is powered by the same systems that manage events:

ClickHouse#

Stores attributes in a high-performance columnar format
Designed for trillions of records
Supports real-time lookups and historical queries

Flink Pipelines#

Update attributes in real time
Compute engagement, session, or summary attributes on the fly
Trigger journeys based on attribute changes

Real-Time Personalization#

CDN-powered engine
Applies segmentation + attribute evaluation globally under 500ms
This ensures attributes are always fresh, accurate, and ready to be used at any moment.

Data Ingestion Sources for Attributes#

Attributes are populated and updated from multiple ingestion points.

SDKs (Client-side)#

JavaScript SDK#

The most powerful method for populating and updating profile attributes via websites.

iOS SDK#

Best for capturing attributes in iOS apps.

Android SDK#

Optimized for capturing attributes in Android apps.
Client-based SDKs are ideal for capturing direct user interaction data.

Server-side Sources#

Node.js SDK#

Used when the server needs to update critical profile attributes such as revenue, order details, or subscription info.

REST API#

Used when Intempt does not have a native SDK for your environment.
Server-side collection is safer, more reliable, and bypasses ad-blockers.

Cloud App Sources#

Intempt also supports attribute enrichment from 3rd-party systems:
Shopify — imports customer and order attributes
HubSpot — imports CRM attributes
Stripe — imports subscription and payment attributes
These attributes sync directly into the unified profile model.

Tracking Data and Attribute Updates#

Two main tracking approaches:#

1.
Client-based tracking
Browser and mobile SDKs
Captures direct interaction + contextual attributes
Provides richer behavioral context
2.
Server-based tracking
Node.js SDK and REST API
More secure, reliable
Ensures business-critical attributes (ex: payments) cannot be blocked
Intempt recommends using a mix of both for best accuracy and reliability.

Summary#

Attributes form the foundation of Intempt’s unified profile.
They allow Intempt to:
Merge multiple data sources
Maintain a consistent customer model
Deliver real-time insights
Trigger personalized engagement
Power segmentation and experimentation
Using SDKs, APIs, and cloud sources, Intempt ensures attributes remain updated and consistent across your entire customer lifecycle.
Modified at 2025-12-03 11:38:55
Previous
Required Fields
Next
Product Catalog Schema
Built with