# Create source

# Sources

With Intempt, you can create a **Source** for each website, app, or backend service you want to track. While it’s technically possible to send all your data through a single source, we strongly recommend creating a **separate source for each independent data origin**.

This improves:
- Data quality  
- Audience segmentation  
- Debugging  
- Attribute mapping  
- Multi-environment setups  

---

## Why use multiple sources?

Each source keeps its own:
- Tracking configuration  
- Event stream  
- Identity resolution context  
- Attribute mappings  
- Rate limits and ingestion logs  

This provides cleaner, more reliable datasets—especially when managing multiple products or environments such as **production, staging, and development**.

---

# Use Cases

### 1. **Ingest event data from selected sources**
Track user actions from your website, mobile apps, or backend services through Intempt’s SDKs and APIs.

### 2. **Configure attribute mapping**
Control how external fields map to Intempt attributes:
- One-way sync (external → Intempt)
- Two-way sync (external ↔ Intempt)

### 3. **Configure sync schedules (Cloud Apps)**
Set synchronization frequency for platforms such as HubSpot, Shopify, or Stripe.

---

# Where to Start

## Event Stream Sources
Event stream sources collect **real-time behavioral data** from your website, mobile app, or servers.

### **JavaScript SDK**
Track all browser-side data flowing through your website.  
Captures: page views, clicks, forms, user identification, and custom events.

### **iOS SDK**
Track user interactions on your iOS mobile application.  
Supports auto-tracked events (touch, view, session events) + advanced personalization & experiments.

### **Android SDK**
Track all events and interactions from your Android application.  
Supports autotrack, custom events, personalization, and experiments.

### **Node.js SDK**
Send data directly from your backend servers.  
Recommended when:
- Client-side tracking is tampered with
- You must track secure or authoritative events
- Data originates from backend processes

### **REST API**
Send your data to Intempt’s **HTTP Tracking API** from any platform.  
Use this when:
- No native SDK exists for your environment  
- Server-to-server tracking is required

### **Google Tag Manager**
Install the JavaScript SDK without modifying your codebase.  
Use GTM to:
- Deploy Intempt in minutes  
- Manage tags centrally  
- Control event tracking via GTM rules

---

# Cloud Apps (Integrations)

## **HubSpot**
Sync:
- Contacts  
- Companies  
- Deals  

Ideal for combining CRM insights with behavioral analytics.

---

## **Shopify**
Sync:
- Orders  
- Customers  
- Product data  

Perfect for running ecommerce analytics, product recommendations, and personalized experiences.

---

## **Stripe**
Sync:
- Customers  
- Subscriptions  
- Invoices  
- Charges  
- Trials  

Useful for churn analysis, billing behavior, and LTV segmentation.