# Advertising Analyst
Source: https://docs.customeros.ai/agents/advertising-analyst
Optimize advertising campaigns with AI-powered performance analysis and insights
The Advertising Analyst agent provides comprehensive analysis of your advertising campaigns across all platforms, delivering actionable insights to optimize ad spend, improve targeting, and maximize advertising ROI.
## What it does
The Advertising Analyst agent:
* Monitors advertising performance across all platforms (Google, Facebook, LinkedIn, etc.)
* Analyzes campaign metrics, audience performance, and creative effectiveness
* Identifies optimization opportunities for better ROI
* Provides recommendations for budget allocation and bid strategies
* Tracks competitive advertising activities and market trends
## Key Features
* **Cross-Platform Analysis**: Unified view of advertising performance across all channels
* **ROI Optimization**: Detailed analysis of advertising return on investment
* **Audience Insights**: Understanding which audiences drive the best results
* **Creative Performance**: Analysis of which ad creatives perform best
* **Competitive Intelligence**: Monitoring competitor advertising strategies
## Use Cases
* **Campaign Optimization**: Improve performance of existing advertising campaigns
* **Budget Allocation**: Optimize ad spend across platforms and campaigns
* **Audience Targeting**: Refine targeting for better campaign performance
* **Creative Testing**: Identify which ad creatives drive the best results
* **Competitive Analysis**: Stay informed about competitor advertising strategies
## Getting Started
To enable the Advertising Analyst agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Advertising Analyst agent
4. Connect your advertising platforms (Google Ads, Facebook Ads, LinkedIn Ads, etc.)
5. The agent will begin analyzing your advertising performance
## Configuration Options
* **Ad Platforms**: Connect Google Ads, Facebook Ads, LinkedIn Ads, and other platforms
* **Performance Metrics**: Choose which advertising metrics to prioritize
* **Analysis Frequency**: Set how often to analyze and report on performance
* **Optimization Focus**: Define primary goals (conversions, traffic, brand awareness)
* **Competitive Monitoring**: Set up tracking for competitor advertising activities
# AI Search Analyst
Source: https://docs.customeros.ai/agents/ai-search-analyst
Analyze search behavior and optimize content for better discovery and engagement
The AI Search Analyst agent monitors and analyzes search behavior patterns, providing insights to optimize your content strategy, improve search rankings, and enhance content discoverability.
## What it does
The AI Search Analyst agent:
* Analyzes search queries and user search behavior patterns
* Identifies content gaps and optimization opportunities
* Monitors search rankings and competitive positioning
* Provides recommendations for content optimization and creation
* Tracks search trends and emerging topics in your industry
## Key Features
* **Search Behavior Analysis**: Understanding how users search for your products/services
* **Content Gap Identification**: Finding opportunities for new content creation
* **SEO Optimization**: Recommendations for improving search engine rankings
* **Competitive Search Analysis**: Monitoring competitor search performance
* **Trend Monitoring**: Identifying emerging search trends and opportunities
## Use Cases
* **Content Strategy**: Develop content that aligns with search behavior
* **SEO Optimization**: Improve search rankings and organic visibility
* **Keyword Research**: Identify high-value keywords and search opportunities
* **Competitive Analysis**: Understand competitor search strategies
* **Content Planning**: Plan content based on search demand and trends
## Getting Started
To enable the AI Search Analyst agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the AI Search Analyst agent
4. Connect your search analytics and SEO tools
5. The agent will begin analyzing search data and providing insights
## Configuration Options
* **Search Platforms**: Connect Google Analytics, Search Console, and SEO tools
* **Analysis Scope**: Define which websites and content to analyze
* **Competitive Tracking**: Set up monitoring for competitor websites
* **Keyword Focus**: Specify target keywords and topic areas
* **Reporting Frequency**: Choose how often to receive search insights and recommendations
# Campaign Analyst
Source: https://docs.customeros.ai/agents/campaign-analyst
Monitor and analyze marketing campaign performance with AI-powered insights
The Campaign Analyst agent continuously monitors your marketing campaigns, providing detailed performance analysis, insights, and recommendations to optimize your marketing ROI and campaign effectiveness.
## What it does
The Campaign Analyst agent:
* Tracks campaign performance across all marketing channels
* Analyzes conversion rates, engagement metrics, and ROI
* Identifies top-performing campaigns, audiences, and creative assets
* Provides actionable insights for campaign optimization
* Monitors competitor campaign activities and market trends
## Key Features
* **Performance Tracking**: Real-time monitoring of campaign metrics across channels
* **ROI Analysis**: Detailed analysis of campaign return on investment
* **Attribution Modeling**: Understanding the customer journey and touchpoint effectiveness
* **Competitive Intelligence**: Monitoring competitor campaign strategies and performance
* **Predictive Analytics**: Forecasting campaign performance and outcomes
## Use Cases
* **Performance Optimization**: Identify what's working and what needs improvement
* **Budget Allocation**: Optimize spend across campaigns and channels
* **Creative Testing**: Analyze which creative assets drive the best results
* **Audience Insights**: Understand which audiences respond best to your campaigns
* **Competitive Analysis**: Stay informed about competitor marketing activities
## Getting Started
To enable the Campaign Analyst agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Campaign Analyst agent
4. Connect your marketing platforms and analytics tools
5. The agent will begin analyzing your campaign performance
## Configuration Options
* **Data Sources**: Connect marketing platforms (Google Ads, Facebook, LinkedIn, etc.)
* **Metrics Focus**: Choose which performance metrics to prioritize
* **Reporting Frequency**: Set how often to generate performance reports
* **Alert Thresholds**: Define when to receive notifications about performance changes
* **Analysis Depth**: Configure the level of detail for campaign analysis
# Campaign Strategizer
Source: https://docs.customeros.ai/agents/campaign-strategizer
Design and optimize marketing campaigns with AI-powered strategic insights
The Campaign Strategizer agent helps you design, plan, and optimize marketing campaigns by analyzing your audience, market conditions, and historical performance to recommend winning strategies.
## What it does
The Campaign Strategizer agent:
* Analyzes your target audience and ideal customer profiles
* Recommends optimal campaign strategies and tactics
* Suggests messaging, channels, and timing for maximum impact
* Identifies the best audiences for campaign targeting
* Provides budget allocation recommendations across channels
## Key Features
* **Strategic Planning**: Develops comprehensive campaign strategies based on your goals
* **Audience Analysis**: Identifies and segments target audiences for optimal targeting
* **Channel Optimization**: Recommends the best marketing channels for your campaigns
* **Message Crafting**: Suggests compelling messaging and creative directions
* **Budget Planning**: Optimizes budget allocation across channels and tactics
## Use Cases
* **Campaign Planning**: Develop comprehensive strategies for new product launches
* **Audience Targeting**: Identify and segment audiences for personalized campaigns
* **Channel Selection**: Choose the most effective marketing channels for your goals
* **Message Development**: Create compelling messaging that resonates with your audience
* **Performance Optimization**: Improve campaign performance through strategic insights
## Getting Started
To enable the Campaign Strategizer agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Campaign Strategizer agent
4. Define your campaign goals and target audience
5. The agent will begin analyzing and providing strategic recommendations
## Configuration Options
* **Campaign Objectives**: Define your primary goals (awareness, lead generation, conversion)
* **Target Audience**: Specify your ideal customer profiles and segments
* **Channel Preferences**: Set preferences for marketing channels and platforms
* **Budget Parameters**: Define budget constraints and allocation preferences
* **Performance Metrics**: Choose key performance indicators to optimize for
# Company Enricher
Source: https://docs.customeros.ai/agents/company-enricher
Automatically enrich company data with comprehensive business information
The Company Enricher agent automatically enhances your company records with comprehensive business information, providing valuable insights for better decision-making and relationship management.
## What it does
The Company Enricher agent:
* Gathers detailed company information from multiple data sources
* Enriches existing company records with missing data
* Provides industry classifications and business insights
* Updates company size, revenue, and location information
* Identifies key business metrics and growth indicators
## Key Features
* **Comprehensive Data Collection**: Pulls information from multiple reliable business databases
* **Real-time Updates**: Keeps company information current and accurate
* **Industry Intelligence**: Provides detailed industry classifications and market insights
* **Financial Metrics**: Enriches records with revenue, employee count, and growth data
* **Geographic Data**: Adds detailed location and market presence information
## Use Cases
* **Lead Qualification**: Better assess potential customers with complete company profiles
* **Account Planning**: Develop targeted strategies based on comprehensive company data
* **Market Analysis**: Understand your total addressable market with enriched company insights
* **Sales Preparation**: Equip your team with detailed company background before meetings
## Getting Started
To enable the Company Enricher agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Company Enricher agent
4. Configure your data enrichment preferences
5. The agent will automatically begin enriching your company records
## Configuration Options
* **Data Sources**: Select which external data sources to use for enrichment
* **Update Frequency**: Set how often the agent refreshes company information
* **Field Preferences**: Choose which company fields to prioritize for enrichment
* **Quality Thresholds**: Define minimum data quality standards for updates
# Company Researcher
Source: https://docs.customeros.ai/agents/company-researcher
Conduct deep research on companies to uncover strategic insights and opportunities
The Company Researcher agent performs comprehensive research on target companies, providing detailed insights that help you understand prospects, competitors, and market opportunities.
## What it does
The Company Researcher agent:
* Conducts thorough research on target companies
* Analyzes company news, press releases, and public announcements
* Identifies recent funding, partnerships, and strategic initiatives
* Tracks executive changes and organizational updates
* Monitors competitive landscape and market positioning
## Key Features
* **Deep Research**: Goes beyond basic company data to uncover strategic insights
* **News Monitoring**: Tracks recent company developments and industry news
* **Competitive Analysis**: Provides context about company positioning in the market
* **Executive Intelligence**: Monitors leadership changes and key personnel updates
* **Market Context**: Delivers insights about industry trends affecting the company
## Use Cases
* **Sales Intelligence**: Understand prospect companies before outreach
* **Competitive Analysis**: Monitor competitor activities and strategic moves
* **Investment Research**: Evaluate potential partners or acquisition targets
* **Market Research**: Understand industry dynamics and market trends
* **Account Management**: Stay informed about existing customer developments
## Getting Started
To enable the Company Researcher agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Company Researcher agent
4. Set up your research parameters and focus areas
5. The agent will begin conducting research on your target companies
## Configuration Options
* **Research Depth**: Set the level of detail for company research
* **Update Frequency**: Choose how often to refresh research data
* **Focus Areas**: Define specific aspects to prioritize (funding, partnerships, etc.)
* **Alert Triggers**: Set up notifications for significant company developments
* **Research Sources**: Select which data sources and news outlets to monitor
# Contact Enricher
Source: https://docs.customeros.ai/agents/contact-enricher
Automatically enrich contact records with comprehensive personal and professional information
The Contact Enricher agent automatically enhances your contact records with detailed personal and professional information, providing valuable context for better relationship building and targeted outreach.
## What it does
The Contact Enricher agent:
* Enriches contact records with professional information and social profiles
* Gathers employment history, role details, and company information
* Identifies contact preferences and communication channels
* Updates contact information to ensure data accuracy
* Provides insights into contact interests and professional background
## Key Features
* **Professional Profiling**: Detailed employment history, role, and company information
* **Social Intelligence**: Links to professional and social media profiles
* **Contact Verification**: Ensures email addresses and phone numbers are current
* **Interest Mapping**: Identifies professional interests and expertise areas
* **Communication Preferences**: Understanding preferred communication channels and timing
## Use Cases
* **Sales Outreach**: Personalize outreach with detailed contact background
* **Relationship Building**: Better understand contacts for stronger relationships
* **Account Management**: Stay informed about contact role changes and movements
* **Marketing Personalization**: Tailor marketing messages based on contact profiles
* **Networking**: Leverage contact insights for more effective networking
## Getting Started
To enable the Contact Enricher agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Contact Enricher agent
4. Configure your data enrichment preferences
5. The agent will automatically begin enriching your contact records
## Configuration Options
* **Data Sources**: Select which external data sources to use for enrichment
* **Update Frequency**: Set how often the agent refreshes contact information
* **Privacy Settings**: Configure data collection and storage preferences
* **Field Priorities**: Choose which contact fields to prioritize for enrichment
* **Quality Thresholds**: Define minimum data quality standards for updates
# Content Analyst
Source: https://docs.customeros.ai/agents/content-analyst
Analyze content performance and optimize your content strategy with AI insights
The Content Analyst agent evaluates your content performance across all channels, providing detailed insights on engagement, effectiveness, and optimization opportunities to maximize your content ROI.
## What it does
The Content Analyst agent:
* Analyzes content performance across all marketing channels
* Tracks engagement metrics, shares, and conversion rates
* Identifies top-performing content themes and formats
* Provides recommendations for content optimization and creation
* Monitors content trends and competitive content strategies
## Key Features
* **Performance Analytics**: Comprehensive analysis of content engagement and effectiveness
* **Content Attribution**: Understanding how content drives conversions and business outcomes
* **Format Optimization**: Identifying which content formats perform best for your audience
* **Topic Analysis**: Discovering which topics resonate most with your audience
* **Competitive Content Intelligence**: Monitoring competitor content strategies and performance
## Use Cases
* **Content Strategy**: Optimize your content strategy based on performance data
* **Content Planning**: Plan future content based on what works best
* **Format Selection**: Choose the most effective content formats for your goals
* **Topic Research**: Identify trending topics and audience interests
* **ROI Optimization**: Focus resources on high-performing content types
## Getting Started
To enable the Content Analyst agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Content Analyst agent
4. Connect your content platforms and analytics tools
5. The agent will begin analyzing your content performance
## Configuration Options
* **Content Sources**: Connect blogs, social media, email, and other content platforms
* **Performance Metrics**: Choose which metrics to prioritize (engagement, conversion, etc.)
* **Analysis Period**: Set time ranges for content performance analysis
* **Competitive Tracking**: Monitor competitor content strategies
* **Content Categories**: Organize content analysis by topic, format, or campaign
# Ideal Customer Profiler
Source: https://docs.customeros.ai/agents/ideal-customer-profiler
Analyze your best customers to create detailed ideal customer profiles
The Ideal Customer Profiler agent analyzes your most successful customers to create detailed ideal customer profiles (ICPs), helping you identify and target prospects with the highest likelihood of conversion.
## What it does
The Ideal Customer Profiler agent:
* Analyzes your best customers to identify common characteristics
* Creates detailed ideal customer profiles based on successful patterns
* Identifies key demographic, firmographic, and behavioral traits
* Provides assessment models for prospect evaluation
* Continuously refines profiles based on new customer data
## Key Features
* **Pattern Recognition**: Identifies common traits among your best customers
* **Multi-dimensional Analysis**: Considers company size, industry, technology stack, and behavior
* **Dynamic Profiling**: Updates profiles as your customer base evolves
* **Assessment Models**: Evaluates leads based on ICP alignment
* **Segmentation**: Develops multiple ICPs for different product lines or markets
## Use Cases
* **Lead Qualification**: Assess and prioritize prospects based on ICP fit
* **Marketing Targeting**: Focus campaigns on ideal customer segments
* **Sales Strategy**: Align sales efforts with highest-value prospects
* **Product Development**: Understand customer needs for feature prioritization
* **Market Expansion**: Identify new markets that match your ICP characteristics
## Getting Started
To enable the Ideal Customer Profiler agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Ideal Customer Profiler agent
4. Connect your customer data sources
5. The agent will analyze your customers and create initial ICPs
## Configuration Options
* **Customer Segments**: Define which customers to include in ICP analysis
* **Profile Factors**: Choose which characteristics to prioritize (industry, size, etc.)
* **Success Metrics**: Define what constitutes a "successful" customer
* **Update Frequency**: Set how often to refresh ICP analysis
* **Assessment Weights**: Adjust the importance of different ICP factors
# Agents
Source: https://docs.customeros.ai/agents/index
# Lead Qualifier
Source: https://docs.customeros.ai/agents/lead-qualifier
Automatically qualify leads using intelligent stage classification and engagement analysis
The Lead Qualifier agent automatically evaluates and qualifies incoming leads, helping your sales team focus on the most promising opportunities by providing intelligent classification and prioritization.
## What it does
The Lead Qualifier agent:
* Automatically qualifies leads based on stage and engagement signals
* Evaluates lead quality using multiple data points
* Prioritizes leads for sales team follow-up
* Identifies high-engagement evaluation prospects needing sales attention
* Routes qualified leads to appropriate sales representatives
## Key Features
* **Intelligent Classification**: Uses AI to evaluate lead stage and buying intent
* **Multi-factor Analysis**: Considers company fit, engagement level, and behavioral signals
* **Real-time Qualification**: Processes leads immediately as they enter your system
* **Automated Routing**: Directs qualified leads to the right sales team members
* **Continuous Learning**: Improves qualification accuracy based on conversion outcomes
## Use Cases
* **Sales Efficiency**: Help sales teams focus on the most promising leads
* **Lead Prioritization**: Rank leads by likelihood to convert
* **Resource Allocation**: Distribute leads based on quality and sales capacity
* **Conversion Optimization**: Improve overall lead-to-customer conversion rates
* **Marketing Feedback**: Provide insights on lead quality by campaign or source
## Getting Started
To enable the Lead Qualifier agent:
1. Navigate to your CustomerOS workspace
2. Go to Agents in the left sidebar
3. Find and enable the Lead Qualifier agent
4. Configure your lead qualification criteria
5. The agent will begin qualifying incoming leads automatically
## Configuration Options
* **Stage Criteria**: Define factors that indicate lead quality and buying intent
* **Sales Attention Rules**: Set criteria for flagging high-engagement evaluation leads
* **Routing Rules**: Configure how qualified leads are assigned to sales team members
* **Data Sources**: Connect lead sources and enrichment data for comprehensive analysis
* **Feedback Loop**: Enable learning from conversion outcomes to improve qualification accuracy
# Briefs
Source: https://docs.customeros.ai/briefs
Understand how CustomerOS generates dynamic sales briefs and research for every lead.
## What Are Briefs?
Every lead in CustomerOS comes with a **Sales Brief**: a living research document that gives your team the context they need to personalize outreach and progress deals.
Unlike static research decks, briefs are automatically **enriched from the global company graph** and **reframed to your ICP** so that the insights are always:
* **Current** – continuously refreshed with live market and firmographic data
* **Relevant** – prioritized based on what matters to your ICP definition
* **Actionable** – designed to inform real conversations and next steps
***
## What a Brief Includes
Each brief is designed to answer the question: *“What should I know before engaging this lead?”*
Components typically include:
* **Company Overview** → industry, size, HQ, core offering
* **ICP Fit Rationale** → why this company is in your lead list (assessed against your ICP)
* **Recent Activity** → notable web engagements, ad interactions, content downloads
* **Strategic Signals** → hiring patterns, tech stack changes, partnerships, press mentions
* **Buying Stage Context** → current stage in the [Buyer’s Journey](/buyers-journey) and triggers for progression
* **Suggested Talking Points** → AI-generated prompts for outreach, tied to recent activity and ICP priorities
***
## Why Briefs Matter
* **Save Research Time** → No more manual LinkedIn, Google, or Crunchbase digging
* **Enable Personalization at Scale** → Every rep can open a lead and instantly sound relevant
* **Improve Consistency** → Sales, marketing, and success teams all work from the same insights
* **Accelerate Pipeline** → Reps know what’s important to say at the right moment in the journey
***
## How Briefs Are Generated
1. CustomerOS matches the lead to its **global company object**.
2. Live research signals are pulled in from multiple sources.
3. Insights are **assessed against your ICP definition**.
4. AI organizes and summarizes the findings into a concise, ready-to-use brief.
5. The brief is updated dynamically as new touchpoints and research signals come in.
***
## Example
For a mid-market SaaS lead that recently:
* Downloaded an ROI calculator (Education → Solution stage progression)
* Posted 3 engineering job openings (tech adoption signal)
* Shows strong ICP fit
Their brief might include:
* “Company is expanding engineering capacity — likely evaluating tooling vendors.”
* “High engagement with ROI content suggests budget conversation readiness.”
* “Next best action: connect via LinkedIn + send case study with quantified ROI.”
***
## Next Steps
* See how [Leads](/leads) expose briefs directly in the company profile.
* Explore [Touchpoints](/touchpoints) to understand the engagement data driving your briefs.
* Learn how [Contacts](/contacts) tie the right people to each brief.
# Buyer's Journey
Source: https://docs.customeros.ai/buyers-journey
Understand how CustomerOS classifies leads by stage and what content moves them forward.
## Overview
CustomerOS maps every company in your workspace to one of four stages:
1. **Target** → Matches ICP but no engagement yet
2. **Education** → Engaging with problem/industry content (in nurture)
3. **Solution** → Evaluating solutions and approaches (in nurture)
4. **Evaluation** → Comparing vendors and gathering stakeholders (in nurture or needs sales attention with high engagement)
Leads move through stages based on depth of content engagement, attention ratios, form interactions, velocity/decay mechanics, and cross-stakeholder signals. High-engagement evaluation leads flag for sales attention.
***
## Stage Definitions
| Stage | Status | Typical Behaviors | Content Influence |
| -------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| **Target** | Not engaged | ICP match, little or no engagement | Sees ads, social mentions, ungated blog posts |
| **Education** | In nurture | Reads problem/industry blogs, subscribes, downloads explainers | Blogs, thought leadership, explainers, glossaries, trend reports, newsletters, gated diagnostics |
| **Solution** | In nurture | Longer sessions, "how-to"/frameworks, ROI calculators, customer outcomes | Playbooks, frameworks, webinars, ROI tools, verticalized success stories |
| **Evaluation** | In nurture or sales | Visits pricing/comparison pages, downloads case studies, multi-stakeholder visits, demo requests | Transparent competitor pages, case studies by vertical, detailed docs, integration guides |
**High-engagement evaluation** leads (demo requests, pricing revisits, legal/security checks, multiple stakeholders) automatically flag for sales attention.
***
## What Moves a Lead Forward
### Target → Education
**System triggers:**
* 3+ blog views within 2 weeks
* Industry report/diagnostic download (attention ratio >1.2)
* Webinar attendance >75%
**Content that helps:**
* Problem-first blogs and explainers
* Thought leadership POVs that frame pain clearly
* Lightly branded glossaries, checklists, or trend reports
* Awareness ads and ungated tools that give language to the problem
***
### Education → Solution
**System triggers:**
* “How-to” guide or framework download (>60% completion)
* ROI calculator use
* Product/solution webinar engagement
* 2–3 pricing/features visits in one session
**Content that helps:**
* Vertical-specific playbooks and ROI models
* Benchmarks and calculators that arm champions
* Success stories with clear “before/after” outcomes
* Nurture sequences pointing to frameworks and solution assets
***
### Solution → Evaluation
**System triggers:**
* Demo/trial request
* Case study or comparison downloads
* Multiple stakeholders active on site
* Repeat pricing or product page visits
**Content that helps:**
* Transparent comparison pages (vs. competitors / status quo)
* Case studies by vertical, role, or use case
* Technical docs and integration playbooks
* Buyer checklists and differentiated positioning
***
### Evaluation → Sales Attention
**System triggers (high-engagement evaluation):**
* Proposal/contract engagement
* Sales meeting attendance
* Onboarding or implementation doc views
* Requests for references/security info
* Multiple pricing revisits with long session times
**Content that helps:**
* ROI calculators, references, and onboarding previews
* Procurement-friendly docs (SOC2, security, integrations)
* Success plans and implementation timelines
* Sales briefs that pre-empt objections
***
## Decay & Regression
* Leads regress to earlier stages without continued engagement
* Negative signals (unsubscribe, competitor visits) accelerate regression
* Use evergreen hubs and re-engagement campaigns to recover stalled accounts
***
## Velocity Signals
* Multiple sessions in 7 days accelerates stage progression
* Increasing session duration indicates growing intent
* Fast consumption of problem → solution content shows active buying journey
***
## Cheatsheet
| From → To | Triggers | Content that helps |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Target → Education** | • 3+ blog views
• Industry report download
• Webinar >75% | • Problem blogs, explainers, glossaries
• Thought leadership POVs
• Trend reports & diagnostics |
| **Education → Solution** | • Framework/guide download
• ROI calculator use
• Solution webinar
• Pricing/features visits | • Playbooks & ROI models
• Success stories
• Benchmarks & calculators
• Framework nurtures |
| **Solution → Evaluation** | • Demo/trial request
• Case study/comparison downloads
• Multi-stakeholder visits | • Comparison pages
• Case studies by vertical
• Technical/integration docs
• Buyer guides |
| **Evaluation → Sales Ready** | • Proposal/contract engagement
• Sales meeting attendance
• Onboarding doc views | • ROI calculators, references
• Procurement/security docs
• Implementation timelines & previews |
***
## Next Steps
* Learn how [Leads](/leads) are classified and displayed
* Configure [Notifications](/notifications) to alert you on stage movement
* Review [Use Cases](/use-cases) to see stage progression in action
# Contacts
Source: https://docs.customeros.ai/contacts
Understand how CustomerOS identifies and manages key people associated with each lead.
Automated contact creation is an additional addon - reach out to our team if
you want to know more.
## What Are Contacts?
While **leads are companies**, progress always depends on the **people inside those companies**.\
Contacts in CustomerOS represent the decision-makers, influencers, and champions tied to a lead.
Each contact is linked to the **lead’s company object** and enriched with role, seniority, and relevance to your ICP. This gives your team the **human context** needed to run targeted, personalized outreach.
***
## How Contacts Are Discovered
CustomerOS automatically surfaces and enriches contacts based on:
* **Public and partner data sources** (e.g., LinkedIn, press releases, company websites)
* **Your ICP criteria** (e.g., job titles, departments, levels of seniority)
* **Behavioral signals** (multiple people from same company engaging with your content)
* **Manual additions** by your team (always possible for custom scenarios)
***
## Key Attributes of a Contact
Each contact typically includes:
* **Full name and role** → e.g. VP of Marketing, CTO
* **Seniority level** → Executive, Manager, IC
* **ICP relevance** → How closely this person aligns with your ideal personas
* **Contact details** → Email, LinkedIn, phone (where available)
* **Engagement activity** → Touchpoints tied directly to this contact where known
***
## Why Contacts Matter
* **Personalize Outreach** → Talk to the right people with the right message
* **Expand Buying Committees** → See when multiple stakeholders are engaging from the same company
* **Shorten Sales Cycles** → Prioritize contacts who drive budget and decision-making
* **Strengthen Briefs** → Contacts enrich [Sales Briefs](/briefs) with real human context
***
## Example
For a software company lead:
* CustomerOS surfaces a **VP of Engineering** (primary decision maker),
* A **Director of IT** (technical evaluator),
* And a **Head of Finance** (budget influencer).
As engagement grows, you can see which stakeholders are leaning in — and coordinate outreach accordingly.
***
## Best Practices
* **Focus on ICP personas first** → prioritize outreach to contacts who map directly to your ICP.
* **Track multi-contact engagement** → multiple stakeholders engaging = strong buying signal.
* **Keep data fresh** → CustomerOS updates contacts automatically, but you can add/remove as needed.
* **Leverage in briefs** → always review contacts inside [Briefs](/briefs) before outreach.
***
## Next Steps
* Learn how [Leads](/leads) organize companies as the central object.
* Explore how [Touchpoints](/touchpoints) reveal which contacts are active.
* Review how [Briefs](/briefs) combine contacts with research to prep your team.
# Data Structure
Source: https://docs.customeros.ai/data-structure
Learn how CustomerOS organizes data with global company records, workspace-specific leads, and their connected insights.
## Overview
CustomerOS separates the idea of a **Company** from a **Lead**.
* **Companies** are global, canonical records — enriched, maintained, and shared across all CustomerOS workspaces.
* **Leads** are workspace-specific views of those companies, personalized by your ICP and enriched with relevant touchpoints, briefs, and contacts.
This design means every customer benefits from CustomerOS’s live company research, while still getting a perspective that is unique to their pipeline.
***
## Core Objects
### Companies (Global)
* One **canonical record** for each company in the CustomerOS graph.
* Continuously updated with firmographics, technographics, and market signals.
* Shared across all CustomerOS customers.
### Leads (Workspace-Specific)
* A **lead** is how your workspace sees a company.
* Inherits all the research and enrichment from the global company record.
* Reframed and prioritized based on your **ICP definition** and your team’s pipeline.
* Includes buying stage classification and live activity context.
### Touchpoints
* Logged against leads to show every meaningful interaction (website visits, ad clicks, emails, calls, meetings).
* Keep a timeline of engagement and velocity for each lead.
### Lead Research & Briefs
* Generated from the global company data but **contextualized to your ICP and stage**.
* Provide firmographic and technographic insights, recent activity, and tailored next-best-actions.
* Designed to save sales teams hours of manual research.
### Contacts
* The people associated with each lead (decision-makers, influencers, champions).
* Pulled from CRM integrations, enrichment sources, or CustomerOS discovery.
* Anchored to the lead so outreach is always account-contextual.
***
## How It All Connects
1. **Global Company Data** is continuously updated in the CustomerOS graph.
2. Your workspace sees those companies as **Leads**, filtered and assessed by your ICP.
3. Each lead accumulates **Touchpoints** from your data sources.
4. CustomerOS generates contextual **Briefs** using global research + your ICP fit.
5. **Contacts** are attached to leads, giving sales a clear path to action.
***
## Benefits
* **Shared intelligence**: Tap into CustomerOS’s global research without starting from scratch.
* **ICP relevance**: Data and briefs are reshaped for your exact go-to-market motion.
* **Unified view**: Companies, leads, touchpoints, briefs, and contacts all connect seamlessly.
# CustomerOS
Source: https://docs.customeros.ai/index
Turn anonymous traffic into qualified pipeline. CustomerOS identifies ICP-fit, in-market accounts and delivers the insights sales needs to win.
## Welcome to CustomerOS
CustomerOS is the revenue intelligence platform that helps B2B companies uncover the pipeline that actually matters.\
We identify which companies are on your website, assess them against your Ideal Customer Profile (ICP), detect their buying stage, and deliver real-time insights so sales teams can focus on conversations that convert.
Instead of drowning in noise from non-buyers or generic intent data, CustomerOS gives you a live, unified customer graph that connects all of your first- and third-party data. This lets you see **who is in-market right now, what stage they’re in, and how best to engage them.**
The platform is multiplayer, real-time, and built from the ground up to make ICP-fit opportunities visible, actionable, and attributable across your go-to-market motion. Whether your team is in Slack, reviewing dashboards, or running campaigns, CustomerOS makes sure the highest-impact opportunities surface to the right people at the right time.
If your biggest challenge is figuring out *which leads matter* and *how to
engage them before competitors do*, CustomerOS is for you. We go beyond
identification: by mapping each account’s journey, detecting velocity, and
equipping sales with actionable briefs, we ensure your team never misses a
revenue moment.
***
## Example Use Cases
### 1. Identify
Find the accounts that matter.
* Detect anonymous website visitors in real time
* Assess them against ICP and aspirational profiles
* Classify buying stage (target, education, solution, evaluation) and flag high-engagement leads for sales
* Continuously refresh profiles with live data
### 2. Engage
Act on opportunities with precision.
* Route high-intent accounts to the right rep instantly
* Deliver sales briefs with firmographic, technographic, and contact insights
* Automate timely, personalized outreach across email, ads, and Slack
* Trigger multi-channel campaigns based on buyer stage and velocity
### 3. Measure
Prove what’s working and double down.
* Attribute pipeline to content and campaigns
* Track velocity and conversion across the funnel
* Monitor pipeline health in real time
* Replace scattered spreadsheets with unified, automated reporting
# Insights
Source: https://docs.customeros.ai/insights
Get real pipeline-level insights and reporting: content, campaigns, contracts, and more
Basic reporting is free for every CustomerOS user. Need more tailored or
advanced reports? Contact your sales representative.
CustomerOS reporting delivers insights that fuel smarter, data-driven decisions—whether you're tracking content efficiency, ad ROI, or revenue performance.
***
## Insights
### Content Performance Dashboard
* **What’s new**: Identify which content—such as guides, case studies, or articles—actually moves leads through the pipeline versus what doesn’t.
* **Why it matters**: Now you can quantify content performance by stage—tracking touchpoints, conversions, and influence across the buyer’s journey.
### Ad Campaigns Performance Dashboard
* **What’s new**: Get clarity on which ad campaigns are delivering real ICP-qualified pipeline—and which are just burning budget.
* **Why it matters**: View cost per ICP lead, opportunity creation, and ROI by channel—all in a single interface. Perfect for marketing teams that demand accountability.
***
## Reporting Use Cases
| Scenario | Description |
| ------------------------ | -------------------------------------------------------------------------------------------------- |
| **Evaluate content ROI** | Use the Content Performance dashboard to see which assets truly drive pipeline momentum. |
| **Optimize ad spend** | Leverage Ad Campaigns Performance metrics to focus budget on ads that convert ICP-qualified leads. |
***
## Getting Started with Reporting
1. **Integrate your ad platforms and CRM**\
CustomerOS will ingest your Customers from inbound pipeline metrics.
2. **Leverage advanced dashboards**
* Navigate to **Content Performance** to assess content effectiveness.
* Use **Ad Campaigns Performance** to measure and compare campaign ROI and pipeline contribution.
3. **Act on insights**
* Scale investment in high-performing content and channels.
* Reallocate spend from campaigns that aren’t driving ICP pipeline.
* Share dashboards with stakeholders for continuous alignment on performance.
# Google Ads
Source: https://docs.customeros.ai/integrations/ads/google-ads
Import campaign data and costs for attribution
## What It Does
Imports Google Ads campaign data and costs into CustomerOS for attribution and ROI analysis. Attribution connects ad spend to lead generation and revenue.
**Note:** This is an **inbound-only integration** (Google Ads → CustomerOS). CustomerOS does not push conversion data back to Google Ads. Attribution happens by matching utm parameters from ad clicks to CustomerOS sessions.
**Setup:** OAuth connection → Automatic account discovery → Campaigns and costs sync every 2 hours
## Data Flow
### Inbound Only (Google Ads → CustomerOS)
* **Campaigns** sync: name, status, budget, channel type, sub-type
* **Daily costs** import at campaign and ad level (in micros, converted to currency)
* **Campaign hierarchy**: Stores campaign IDs, ad group IDs, and ad IDs for granular tracking
* **Historical data**: 90-day cost lookback on first sync
### Attribution (Within CustomerOS)
When visitors arrive from Google Ads with utm parameters:
1. CustomerOS captures campaign, ad group, and keyword data from utm parameters
2. Tracks visitor journey and engagement across your website
3. Attributes lead creation to originating campaign when they convert
4. Calculates ROI automatically using imported cost data as leads progress to opportunity/customer
## What You Can Do
**Calculate true ROI**: See which campaigns generate customers, not just clicks—track from ad spend to closed revenue
**Optimize budget**: Shift spend to campaigns driving high-engagement evaluation leads vs. low-quality traffic
**Compare lead quality**: View ICP fit rates and lead stages by campaign to improve targeting
**Track full funnel**: Measure conversion rates from click → lead → opportunity → customer by campaign
**Cost per qualified lead**: Calculate actual cost per qualified lead, not just cost per click
## Reporting Capabilities (Within CustomerOS)
* Campaign-level lead quality and ICP fit analysis
* Cost per lead by stage (using imported cost data)
* Conversion rates from click → lead → opportunity → customer
* ROI by campaign with closed revenue attribution (based on CustomerOS pipeline data)
* Time-to-conversion metrics by campaign source
## Smart Features
* **Multi-account support**: Syncs campaigns from all client accounts you manage (MCC/Manager account support)
* **Granular cost tracking**: Daily cost data at campaign and ad level in micros (converted to currency)
* **Attribution via utm**: Matches utm parameters to campaigns for lead attribution
* **Historical sync**: 90 days of cost data on first connection
* **Incremental updates**: Efficient delta syncs every 2 hours
* **Currency handling**: Properly handles cost micros and currency conversion
## Technical Details
* OAuth 2.0 with Google Ads API v20 (configurable)
* Supports Google Ads Manager (MCC) and individual accounts
* Automatic token refresh for uninterrupted sync
* Batch processing with SOQL queries for campaign, ad group, and ad data
* Telemetry and error tracking for reliability
* Configurable sync schedules (default every 2 hours)
# LinkedIn Ads
Source: https://docs.customeros.ai/integrations/ads/linkedin-ads
Import campaign data and costs for B2B attribution
## What It Does
Imports LinkedIn Ads campaign data and costs into CustomerOS for attribution and ROI analysis. Attribution connects B2B advertising spend to lead generation with insights designed for professional audiences.
**Note:** This is an **inbound-only integration** (LinkedIn Ads → CustomerOS). CustomerOS does not push conversion data back to LinkedIn Ads. Attribution happens by matching utm parameters from ad clicks to CustomerOS sessions.
**Setup:** OAuth connection → Account discovery → Campaigns and costs sync every 2 hours
## Data Flow
### Inbound Only (LinkedIn Ads → CustomerOS)
* **Campaign groups** sync: name, status, budget, run schedule
* **Campaigns** import: name, type, objective, format, cost type, budgets
* **Creatives** (ads) fetch data linked to campaigns
* **Daily analytics**: Cost metrics via adAnalytics API with proper currency handling
* **Historical data**: 90-day cost lookback
### Attribution (Within CustomerOS)
When professionals click LinkedIn ads with utm parameters:
1. CustomerOS captures campaign data from utm parameters with the click
2. Tracks engagement through their evaluation journey
3. Attributes lead creation, opportunity, and revenue back to campaigns
4. Provides insight into which LinkedIn audiences drive best-fit customers
## What You Can Do
**Measure B2B ROI**: Track LinkedIn performance by qualified leads and pipeline, not vanity metrics like impressions
**Optimize targeting**: Identify which LinkedIn campaigns drive high-ICP leads based on utm-tracked sessions
**Compare creative**: See which ad messaging generates engaged prospects (based on journey progression)
**Allocate budget**: Shift spend to campaigns generating high-engagement leads and ICP matches
**Report to executives**: Show true LinkedIn advertising ROI with revenue attribution based on imported cost data
## B2B-Specific Value
LinkedIn integration handles longer B2B sales cycles:
* **Professional context**: Track job titles, companies, and seniority of visitors (when available)
* **Buying committee tracking**: See multiple stakeholders from same company engaging
* **Journey progression**: Monitor how LinkedIn-sourced leads move through evaluation stages
* **Multi-touch value**: Understand LinkedIn's role in complex B2B buying journeys
## Smart Features
* **B2B-optimized attribution**: Properly attributes longer buying cycles via utm tracking
* **Campaign hierarchy**: Syncs campaign groups → campaigns → creatives
* **Ad account sync**: Automatically discovers and syncs all accessible ad accounts
* **Campaign-level insights**: Compare effectiveness by lead quality
* **Historical data**: 90-day cost lookback on initial connection
* **Scheduled sync**: Automatic updates every 2 hours
* **Date range support**: Query analytics for specific date ranges
## Technical Details
* OAuth 2.0 with LinkedIn Marketing API
* Supports multiple ad accounts per tenant
* Automatic token refresh with retry logic
* Daily cost granularity via adAnalytics API for precise ROI calculations
* Campaign hierarchy: Campaign Groups → Campaigns → Creatives
* Batch processing for efficiency
* Scheduled every 2 hours via cron system
* Telemetry-monitored reliability
# HubSpot
Source: https://docs.customeros.ai/integrations/crms/hubspot
Import HubSpot company and deal data into CustomerOS
## What It Does
Imports HubSpot companies and deals into CustomerOS to enrich your lead intelligence with existing CRM data.
**Note:** This is currently an **inbound-only integration** (HubSpot → CustomerOS). CustomerOS does not push data back to HubSpot.
**Setup:** OAuth connection → Configure object sync → Enable sync → Automatic updates every 2 hours
## Data Flow
### Inbound Only (HubSpot → CustomerOS)
* **Companies** sync to match with CustomerOS leads by domain
* **Deals** import to understand pipeline and opportunity status
* **Lifecycle stages** imported from HubSpot
* **Company domains** enable intelligent matching
* **Incremental sync** with cursor-based updates every 2 hours
## What You Can Do
**CRM Enrichment**: Bring your existing HubSpot company data into CustomerOS for unified lead intelligence
**Pipeline Visibility**: Import HubSpot deals to see sales pipeline status alongside CustomerOS engagement data
**Data Consolidation**: Centralize HubSpot CRM data with CustomerOS web intelligence and AI qualification
**Migration Support**: Import HubSpot data when transitioning to CustomerOS for lead management
## Smart Features
* **Intelligent matching**: Automatically matches HubSpot companies to CustomerOS leads by domain
* **Incremental sync**: Only processes new or changed records since last sync
* **Multi-portal support**: Connect multiple HubSpot portals to one CustomerOS account
* **Configurable toggles**: Control company and deal sync independently per portal
* **Batch processing**: Efficient large-scale sync with cursor-based pagination
* **Webhook support**: Real-time updates when HubSpot data changes
## Technical Details
* Secure OAuth 2.0 authentication
* Incremental sync with cursor-based pagination
* Supports multiple HubSpot portals per tenant
* ID mapping table tracks relationships between systems
* Remote version tracking for data consistency
* Batch processing (default 25 records per batch)
* Scheduled every 2 hours via cron system
* Webhook endpoint for real-time updates
# Salesforce
Source: https://docs.customeros.ai/integrations/crms/salesforce
Bi-directional sync between CustomerOS and Salesforce
## What It Does
Bi-directional sync that keeps Salesforce updated with qualified leads while using Salesforce as the source of truth for customer status.
**Setup:** One-click OAuth connection → Configure sync toggles → Automatic sync every 5 minutes
## Data Flow
### From Salesforce → CustomerOS
* **Accounts** sync to match with CustomerOS leads by domain/company name
* **Opportunities** update lead states (opportunity created, closed won, closed lost)
* **Converted Leads** automatically mark CustomerOS leads as customers
* **Account Type = "Customer"** triggers customer status update in CustomerOS
### From CustomerOS → Salesforce
* **Qualified leads** push to Salesforce as new Leads (only ICP fit moderate/strong, skips if Account mapping exists)
* **Opportunities** create/update when CustomerOS identifies sales-ready prospects
* **Lead stages** (Target, Education, Solution, Evaluation) sync to custom Salesforce fields (optional)
* **Buying stage** maps to appropriate Salesforce stages
## What You Can Do
**Auto-qualify leads**: Push ICP-fit leads automatically to Salesforce (moderate/strong ICP fit only)
**Sync opportunities**: Marketing sees deal progression in CustomerOS, sales sees engagement history in Salesforce
**Update lead lifecycle**: Leads automatically move to customer status when Salesforce Accounts show purchase
**Track closed-lost**: CustomerOS marks leads as closed-lost when Salesforce Opportunities don't convert, enabling targeted nurture campaigns
## Smart Features
* **Domain matching**: Sophisticated domain analysis prevents duplicate Lead creation if Account exists
* **Self-healing sync**: Automatically recovers from errors and retries failed syncs
* **Incremental updates**: Only processes changes since last sync using SystemModstamp cursors
* **Per-tenant toggles**: Full control over which sync flows are active (5 independent toggles)
* **External ID support**: Deterministic upserts for data consistency
## Technical Details
* OAuth 2.0 secure authentication with token encryption
* Supports custom Salesforce fields for stages and buying states (auto-provisioned)
* Configurable sync frequency (default: every 5 minutes for delta changes)
* Per-tenant toggle controls for granular sync management (5 independent toggles)
* Full audit trail with telemetry and dead-letter queue for errors
* Works with Salesforce Starter, Professional, Enterprise, and Unlimited editions as a Connected App
* External ID support for deterministic upserts
# Integrations
Source: https://docs.customeros.ai/integrations/index
Connect CustomerOS to your existing tools
CustomerOS syncs data with your CRM, outreach tools, and ad platforms. All integrations use secure OAuth authentication and sync automatically.
## What Gets Synced
**CRMs** - Connect your CRM to sync customer and pipeline data
* [Salesforce](/integrations/crms/salesforce) - Bi-directional: Push qualified leads, sync opportunities, auto-update lead status
* [HubSpot](/integrations/crms/hubspot) - Inbound only: Import companies and deals into CustomerOS
**Outreach Tools** - Send qualified leads to prospecting platforms
* [Apollo](/integrations/outreach/apollo) - Outbound: Push CustomerOS qualified leads to Apollo for targeted outreach
**Meeting Schedulers** - Track buyer journeys leading up to meeting bookings
* [Calendly](/integrations/meetings/calendly) - Connect Calendly to track meeting bookings with buyer-journey analytics
* [HubSpot Meetings](/integrations/meetings/hubspot) - Connect HubSpot meeting links to track meetings and enrich with CustomerOS insights
* [Cal.com](/integrations/meetings/calcom) - Connect Cal.com to track bookings with full attribution (works with self-hosted instances)
**Meeting Intelligence** - Extract marketing insights from customer conversations automatically
* [Fathom](/integrations/meeting-transcripts/fathom) - Extract content ideas, messaging insights, and positioning opportunities from Fathom recordings
* [Grain](/integrations/meeting-transcripts/grain) - Extract buying committee language and persona-specific insights from Grain recordings
**Advertising Platforms** - Import campaign costs for attribution and ROI analysis
* [Google Ads](/integrations/ads/google-ads) - Inbound only: Import campaign costs, attribute leads via utm parameters
* [LinkedIn Ads](/integrations/ads/linkedin-ads) - Inbound only: Import B2B campaign costs, attribute leads via utm parameters
## Key Capabilities
**Centralized Intelligence** - All inbound data (HubSpot, Salesforce Accounts, ad campaigns) enriches CustomerOS leads with unified view
**Multi-Touch Attribution** - Track complete customer journey across Google Ads, LinkedIn Ads, website visits, and conversions using utm parameters and imported cost data
**Bi-Directional CRM Sync** - Salesforce opportunities and account status sync both ways; HubSpot data imports into CustomerOS
**Smart Domain Matching** - Automatically matches companies by domain across all platforms to prevent duplicates
**Automated Outbound** - Push qualified leads to sales tools (Apollo) and CRMs (Salesforce) based on ICP fit and stage
All integrations sync automatically after initial setup (every 2 hours to 15 minutes depending on platform).
# Fathom
Source: https://docs.customeros.ai/integrations/meeting-transcripts/fathom
Automatically extract marketing insights from Fathom recordings—discover content gaps, messaging that works, and positioning opportunities from every customer conversation
## What It Does
Connect your Fathom account to CustomerOS to automatically extract marketing intelligence from every recorded call. Discover what content to create based on real prospect questions, which messaging resonates with buyers who close, and how to position against competitors based on actual objections.
Fathom's native AI summaries are enhanced with marketing-focused analysis, giving you actionable insights for content strategy, positioning, and campaign optimization.
## Why It Matters for Marketing
**Content Gap Identification**: Discover the most frequently asked questions and pain points that you don't have content for. Build a data-driven content roadmap based on real buyer needs.
**Messaging That Converts**: Surface which value propositions and benefit statements prospects respond to positively in calls that close. Update website copy and campaign messaging to match what actually works.
**Competitive Intelligence**: Extract every competitor mention and objection to create battlecards that address real concerns. See which competitive positioning angles win deals.
**Buyer Language Extraction**: Understand the exact words and phrases prospects use to describe their problems. Rewrite marketing materials in the language buyers actually speak.
**Campaign Quality Scoring**: See which campaigns drive meetings with buying-intent conversations versus exploratory chats. Optimize budget toward campaigns that generate qualified discussions.
## Use Cases
**Content Creation Roadmap**: Discover that 65% of prospects ask about "data migration process" in discovery calls, but you have no content addressing it. Create a dedicated migration guide and FAQ to reduce sales friction.
**Messaging Optimization**: Identify that prospects respond positively when you say "eliminate manual work" but glaze over when you mention "process automation." Update all website copy to use language that resonates.
**Competitive Battlecards**: Track that prospects mention Competitor X's "complicated onboarding" in 40% of competitive deals. Create content and messaging around your simple setup process to counter this.
**Buyer Language Adoption**: See that prospects say "scattered data across tools" not "lack of integration." Rewrite homepage and landing page copy to match how buyers actually describe their problems.
**Campaign Quality Analysis**: Discover that LinkedIn thought leadership drives meetings where prospects ask about implementation, while paid search drives basic "what is this?" conversations. Shift budget accordingly.
**Positioning Opportunities**: Uncover that 30% of enterprise prospects mention "audit trail requirements" but competitors don't address it. Identify a positioning gap and create dedicated content around compliance features.
## How It Works
1. **Connect via OAuth** - Click Connect and authorize CustomerOS to access your Fathom transcripts (read-only, secure)
2. **Automatic intelligence extraction** - All transcripts sync every 2 hours with AI analysis identifying marketing insights
3. **Pattern identification** - System identifies common questions, pain points, competitor mentions, and messaging themes across all calls
4. **Marketing insight generation** - Get content recommendations, positioning opportunities, and messaging analysis automatically
5. **Campaign attribution** - See which campaigns drive meetings with qualified, buying-intent conversations
6. **Take action** - Use insights to build content addressing real needs, update messaging that resonates, and refine positioning
**What Gets Analyzed:**
* Common questions and pain points mentioned across all calls
* Value propositions and messaging that prospects respond to positively
* Competitor mentions, objections, and positioning opportunities
* Buyer language and terminology for messaging optimization
* Campaign quality signals (buying intent vs. exploratory conversations)
* Content gaps where prospects ask questions you can't answer
* Fathom's AI summaries enhanced with marketing-focused insights
**Intelligence frequency:** Every 2 hours automatically. No manual analysis or transcript review required.
**Campaign attribution:** See which marketing campaigns drive the calls where prospects discuss budget, timeline, and implementation—the conversations that actually matter.
## How to Connect
1. Go to **Settings → Integrations → Meeting Transcripts → Fathom**
2. Click **Connect Fathom** and authorize CustomerOS (read-only access to transcripts)
3. Transcripts begin syncing automatically within 2 hours
4. Past meetings sync first, then new recordings sync every 2 hours
5. View transcripts in Briefs and analyze conversation insights in CustomerOS
## Smart Features
* **Content gap identification** - Automatically surface the most asked questions that need content to address them
* **Messaging analysis** - Identify which value props and language prospects respond to in calls that close
* **Competitive intelligence extraction** - Track all competitor mentions and objections for battlecard creation
* **Buyer language insights** - Extract exact terminology prospects use to rewrite marketing materials
* **Campaign quality scoring** - See which campaigns drive buying-intent conversations vs. basic education
* **Positioning opportunities** - Uncover pain points competitors aren't addressing for differentiation
* **Automatic sync every 2 hours** - Intelligence extraction happens without manual transcript review
* **Fathom AI enhancement** - Native Fathom summaries enriched with marketing-focused analysis
* **Pattern recognition** - Identify themes and trends across hundreds of conversations automatically
* **Attribution to campaigns** - Connect conversation quality back to specific marketing efforts
* **Multi-language support** - Extract insights from transcripts in multiple languages
## Prerequisites
* Active Fathom account with meeting recordings
* Fathom connected to your calendar (Zoom, Google Meet, or Microsoft Teams)
* Admin or owner access to authorize the CustomerOS integration
## Important Notes
* **Intelligence extraction**: Marketing insights are generated every 2 hours automatically. No manual transcript review required.
* **Historical analysis**: Past calls are analyzed when you first connect to build your intelligence baseline. More data = better pattern recognition.
* **Marketing focus**: Analysis prioritizes insights useful for content creation, messaging optimization, and positioning—not just sales coaching.
* **Campaign attribution**: See which campaigns drive qualified conversations by connecting call content to marketing touchpoints.
* **Content recommendations**: System identifies specific questions and pain points that need content to address them.
* **Messaging extraction**: Discover which language and value props work by analyzing calls that close vs. calls that don't.
* **Privacy & security**: Transcripts are securely stored and encrypted. Intelligence is extracted automatically without human review.
***
## Next Steps
* Learn about [Meeting Intelligence](/meeting-transcripts) to understand the full marketing insight capabilities
* Connect [Grain](/integrations/meeting-transcripts/grain) if your team uses multiple recording tools
* Review [Buyer Journeys](/buyers-journey) to see how conversation insights connect to campaigns
* Explore [Briefs](/briefs) to view conversation history and topics before meetings
* Track [Meeting Bookings](/meetings) to understand which campaigns drive qualified conversations
* See [Touchpoints](/touchpoints) for website activity that leads to buying-intent calls
# Grain
Source: https://docs.customeros.ai/integrations/meeting-transcripts/grain
Automatically extract marketing insights from Grain recordings—discover buying committee language, positioning gaps, and content opportunities from multi-participant conversations
## What It Does
Connect your Grain account to CustomerOS to automatically extract marketing intelligence from every recorded call. Discover what content to create based on buying committee discussions, which messaging resonates across stakeholder groups, and how to position based on multi-participant conversations.
Grain's participant tracking and recording metadata are analyzed to surface marketing insights you can't get from Grain alone—actionable intelligence for content strategy, positioning, and campaign optimization.
## Why It Matters for Marketing
**Buying Committee Language**: Understand how different stakeholder roles (technical, business, executive) describe problems and priorities. Create persona-specific content that resonates with each group.
**Content Gap Analysis**: Identify questions that come up when multiple stakeholders are present. Discover that technical buyers ask about "API rate limits" while business buyers ask about "team collaboration"—then create content for both.
**Positioning Intelligence**: Surface concerns and objections raised when full buying committees are present. These multi-stakeholder conversations reveal real positioning opportunities competitors miss.
**Campaign Quality Measurement**: See which campaigns drive meetings with engaged buying committees versus single exploratory calls. Optimize toward campaigns that bring multiple decision-makers.
**Stakeholder Messaging**: Discover which value propositions resonate with different roles. See that executives care about "time savings" while technical folks care about "customization"—then tailor messaging.
## Use Cases
**Persona-Specific Content**: Discover that technical stakeholders ask about "webhook reliability" while business stakeholders ask about "ROI timelines." Create separate content tracks addressing each persona's concerns.
**Buying Committee Messaging**: See that when multiple stakeholders are present, "team efficiency" messaging resonates more than "individual productivity." Update homepage to focus on team benefits.
**Technical vs. Business Content**: Identify that engineering participants ask implementation questions while business participants ask change management questions. Build content libraries for both audiences.
**Campaign Quality Analysis**: Find that LinkedIn thought leadership drives meetings with 3+ participants (buying committees) while paid search drives solo exploratory calls. Shift budget to committee-generating campaigns.
**Positioning from Objections**: Track that when CFOs are present, they raise "budget approval process" concerns. Create dedicated content and sales enablement around procurement workflows.
**Content Sequencing**: Discover that technical prospects who engage with API documentation before calls bring their business counterparts to second meetings 40% more often. Optimize content journey to involve full committees.
## How It Works
1. **Connect via OAuth** - Click Connect and authorize CustomerOS to access your Grain recordings (read-only, secure)
2. **Automatic intelligence extraction** - All transcripts sync every 2 hours with AI analysis identifying marketing insights
3. **Participant-level analysis** - System analyzes which stakeholder roles ask which questions and raise which concerns
4. **Pattern identification** - Identifies common themes across buying committees, technical vs. business conversations, and multi-stakeholder discussions
5. **Marketing insight generation** - Get persona-specific content recommendations, positioning opportunities, and messaging analysis
6. **Campaign attribution** - See which campaigns drive meetings with engaged buying committees versus solo explorers
7. **Take action** - Use insights to create persona-targeted content, tailor messaging by stakeholder role, and optimize campaigns
**What Gets Analyzed:**
* Participant-level questions and concerns by stakeholder role
* Buying committee language and terminology across different personas
* Technical vs. business stakeholder priorities and pain points
* Multi-stakeholder conversation themes and patterns
* Campaign quality signals (buying committee engagement vs. solo explorers)
* Content gaps for different buyer personas and roles
* Positioning opportunities from multi-participant objections
**Intelligence frequency:** Every 2 hours automatically. No manual analysis or transcript review required.
**Participant intelligence:** System identifies which types of stakeholders (technical, business, executive) ask which questions, enabling persona-specific content and messaging.
**Campaign attribution:** See which campaigns drive meetings with engaged buying committees versus individual exploratory conversations.
## How to Connect
1. Go to **Settings → Integrations → Meeting Transcripts → Grain**
2. Click **Connect Grain** and authorize CustomerOS (read-only access to recordings)
3. Transcripts begin syncing automatically within 2 hours
4. Past recordings sync first, then new meetings sync every 2 hours
5. View transcripts in Briefs and analyze participant insights in CustomerOS
## Smart Features
* **Persona-specific insights** - Identify which questions and concerns come from technical vs. business vs. executive stakeholders
* **Buying committee analysis** - Surface patterns from multi-participant conversations to create content that addresses group dynamics
* **Content gap identification** - Discover persona-specific questions that need dedicated content to address them
* **Stakeholder messaging** - Identify which value props resonate with different buyer roles
* **Campaign quality scoring** - See which campaigns drive buying committee meetings vs. solo exploratory calls
* **Positioning opportunities** - Uncover objections raised when full committees are present
* **Automatic sync every 2 hours** - Intelligence extraction happens without manual transcript review
* **Smart deduplication** - Prevents duplicate analysis based on unique recording IDs
* **Multi-hour handling** - Efficiently analyzes long, complex buying committee discussions
* **Attribution to campaigns** - Connect conversation quality back to specific marketing efforts
* **Pattern recognition** - Identify themes across hundreds of multi-stakeholder conversations
## Prerequisites
* Active Grain account with recorded meetings
* Grain connected to your calendar and meeting platforms (Zoom, Google Meet, Microsoft Teams)
* Admin or owner access to authorize the CustomerOS integration
## Important Notes
* **Intelligence extraction**: Marketing insights are generated every 2 hours automatically. No manual transcript review required.
* **Participant analysis**: System identifies stakeholder roles and personas from email domains and conversation context for targeted insights.
* **Multi-stakeholder focus**: Analysis prioritizes insights from buying committee conversations where multiple decision-makers are present.
* **Marketing focus**: Intelligence extraction emphasizes content gaps, messaging optimization, and positioning opportunities—not just sales coaching.
* **Persona-specific content**: Get recommendations for technical vs. business vs. executive content based on actual stakeholder questions.
* **Campaign attribution**: See which campaigns drive buying committee meetings versus solo exploratory conversations.
* **Historical analysis**: Past calls are analyzed when you first connect to build your intelligence baseline across all personas.
* **Privacy & security**: Transcripts are securely stored and encrypted. Intelligence is extracted automatically without human review.
***
## Next Steps
* Learn about [Meeting Intelligence](/meeting-transcripts) to understand the full marketing insight capabilities
* Connect [Fathom](/integrations/meeting-transcripts/fathom) if your team uses multiple recording tools
* Review [Buyer Journeys](/buyers-journey) to see how conversation insights connect to campaigns
* Explore [Briefs](/briefs) to view conversation history and stakeholder involvement before meetings
* Track [Meeting Bookings](/meetings) to understand which campaigns drive buying committee conversations
* See [Touchpoints](/touchpoints) for website activity that leads to multi-stakeholder engagement
# Cal.com
Source: https://docs.customeros.ai/integrations/meetings/calcom
Track buyer journeys and marketing attribution for Cal.com bookings—works with both Cal.com cloud and self-hosted instances
## What It Does
Connect your Cal.com account to CustomerOS to see the complete buyer journey leading up to every meeting booking. Understand which marketing campaigns, content, and website pages drive your most valuable meetings—all while keeping your existing Cal.com workflow intact.
**Works with Cal.com cloud and self-hosted instances** - Perfect for teams who value data sovereignty and open-source flexibility.
## Why It Matters for Marketing
**Meeting Attribution**: See exactly which marketing channels, campaigns, and content pieces drive Cal.com bookings. Connect ad spend directly to booked meetings and closed deals.
**Buyer Journey Visibility**: Track the complete path from first website visit to booked meeting. Understand how prospects engage with your content before scheduling a call.
**Campaign Optimization**: Identify high-performing campaigns that drive qualified meetings, not just traffic. Double down on what converts browsers into bookers.
**Lead Quality Insights**: See which sources bring buyers who book meetings versus those who just browse. Optimize for quality conversations, not just clicks.
**Content Performance**: Discover which blog posts, case studies, or landing pages prospects read before booking. Create more of what actually drives meetings.
## Use Cases
**Marketing Attribution**: Discover that your LinkedIn thought leadership campaign drove 20 qualified demos last month, while paid search only drove 5. Shift budget to campaigns that drive real conversations.
**Meeting Type Optimization**: Analyze which event durations convert best. See that prospects who book 30-minute discovery calls are 2x more likely to request pricing than those who book 15-minute intro calls.
**Content Performance**: Identify that prospects who engage with your ROI calculator before booking ask more qualified questions about implementation and close 40% faster.
**Channel Analysis**: Understand that LinkedIn campaigns drive more qualified Cal.com bookings than other channels, even with lower traffic volume. Focus budget where it matters.
**Sales Enablement**: Give your sales team full buyer journey context before every Cal.com meeting—see what prospects viewed, downloaded, and engaged with beforehand.
**Location Optimization**: Test which meeting types (Google Meet vs Zoom) result in better show rates and conversion outcomes. Optimize booking options based on data.
## How It Works
1. **Connect Cal.com**: One-click OAuth connection to your Cal.com workspace (cloud or self-hosted)
2. **Automatic sync**: All event types sync every hour automatically
3. **Track bookings**: Every booking is linked to website touchpoints, marketing campaigns, and content engagement
4. **Company matching**: System automatically matches attendees to companies based on email domains
5. **View insights**: See complete buyer journeys, attribution reports, and meeting analytics in CustomerOS
**What Syncs:**
* Your Cal.com event types (all calendars synced automatically every hour)
* Real-time availability when visitors view the booking widget
* Meeting bookings with attendee details and location information
* Event type metadata (duration, description, location type)
* Host information for proper attribution
**Full booking lifecycle:** Create, cancel, and reschedule bookings directly through CustomerOS with real-time Cal.com sync.
**Your team keeps using Cal.com.** CustomerOS adds the attribution layer behind the scenes without changing your workflow.
## How to Connect
1. Go to **Settings → Integrations → Meetings → Cal.com**
2. Click **Connect Cal.com** and authorize CustomerOS (read-only access)
3. Your event types appear automatically within the hour
4. Start tracking—bookings are attributed to buyer journeys immediately
**Self-hosted Cal.com users**: Enter your Cal.com instance URL during connection setup.
## Smart Features
* **Automatic attribution** - Every booking is linked to the prospect's website activity and marketing touchpoints
* **Real-time availability** - Widget displays your actual Cal.com calendar availability
* **Buyer journey tracking** - See every page visit, content download, and campaign touch before the booking
* **Hourly event sync** - New event types appear automatically within an hour
* **Self-hosted support** - Works with both Cal.com cloud and your own self-hosted instance
* **Multiple location types** - Supports Google Meet, Zoom, Daily, and all Cal.com integrations
* **Full booking management** - Create, cancel, and reschedule bookings with real-time sync
* **Company matching** - Automatically matches attendees to accounts based on email domains
* **Multi-timezone support** - Visitors see availability in their local timezone
* **Open-source friendly** - Built for teams who value flexibility and data control
* **Privacy-first option** - Self-hosted Cal.com keeps all booking data on your infrastructure
## Prerequisites
* Active Cal.com account (cloud or self-hosted) with at least one event type configured
* Event types should have location set (Google Meet, Zoom, Daily, etc.)
* For self-hosted instances: Cal.com v2 or later with OAuth enabled
## Important Notes
* **Event type sync** happens every hour, so new event types may take up to 60 minutes to appear in CustomerOS
* **Bookings track immediately** - Attribution and buyer journey tracking happens in real-time when someone books
* **All event types sync** - You can't select a subset; all active event types are made available
* **Company matching** is automatic based on attendee email domains—ensure attendees use company emails for best results
* **Self-hosted instances** must have OAuth 2.0 enabled and accessible from the internet for the integration to work
* **Location types** - All Cal.com location integrations are supported (Google Meet, Zoom, Daily, Phone, Custom)
***
## Next Steps
* Learn how [Buyer Journeys](/buyers-journey) reveal the path to meeting bookings
* Review the main [Meetings](/meetings) page to understand full attribution capabilities
* Explore [Touchpoints](/touchpoints) to see specific website interactions before bookings
* Review [Briefs](/briefs) for pre-meeting insights and buyer journey context
* Connect [Calendly](/integrations/meetings/calendly) or [HubSpot Meetings](/integrations/meetings/hubspot) if you use multiple schedulers
# Calendly
Source: https://docs.customeros.ai/integrations/meetings/calendly
Track buyer journeys and marketing attribution for every Calendly meeting booking
## What It Does
Connect your Calendly account to CustomerOS to see the complete buyer journey leading up to every meeting booking. Understand which marketing campaigns, content, and website pages drive your most valuable meetings—insights you can't get from Calendly alone.
## Why It Matters for Marketing
**Meeting Attribution**: See exactly which marketing channels, campaigns, and content pieces drive meeting bookings. Stop guessing which efforts generate demos and sales calls.
**Buyer Journey Visibility**: Track the complete path from first website visit to booked meeting. Understand how many touchpoints it takes and which ones matter most.
**Campaign Optimization**: Identify high-performing campaigns that drive qualified meetings, not just traffic. Double down on what works and cut what doesn't.
**Lead Quality Insights**: See which sources bring buyers who actually book meetings versus those who just browse.
## Use Cases
**Marketing Attribution**: Discover that your LinkedIn ad campaign drove 15 demo bookings last month, while your Google Ads only drove 3. Adjust budget accordingly.
**Content Performance**: Identify which blog posts or case studies prospects read before booking meetings. Create more of what converts.
**Channel Analysis**: See that prospects who engage with your pricing page are 3x more likely to book meetings than those who don't.
**Campaign ROI**: Calculate true campaign ROI by connecting ad spend to meeting bookings to closed deals.
**Multi-Touch Attribution**: Understand the combination of touchpoints that lead to meetings—not just the last click.
## How It Works
1. **Connect Calendly**: One-click OAuth connection pulls in all your event types automatically
2. **Embed the widget**: Add CustomerOS booking widget to your website (or keep your existing Calendly embeds)
3. **Track automatically**: Every booking is linked to website touchpoints, marketing campaigns, and content engagement
4. **View insights**: See complete buyer journeys, attribution reports, and meeting analytics in CustomerOS
**What Syncs:**
* Your Calendly event types (synced automatically)
* Real-time availability when visitors view the booking widget
* Meeting bookings with attendee details
* Cancel/reschedule links for attendees
**One-way sync:** Calendly remains your source of truth. CustomerOS adds analytics on top without changing your workflow.
## How to Connect
1. Go to **Settings → Integrations → Meetings → Calendly**
2. Click **Connect Calendly** and authorize CustomerOS (read-only access)
3. Your event types appear automatically within 6 hours (usually faster)
4. Start tracking—bookings are attributed to buyer journeys immediately
## Smart Features
* **Automatic attribution** - Every booking is linked to the prospect's website activity and marketing touchpoints
* **Real-time availability** - Widget displays your actual Calendly availability
* **Buyer journey tracking** - See every page visit, content download, and campaign touch before the booking
* **Multi-timezone support** - Visitors see availability in their local timezone
* **Responsive widget** - Works seamlessly on desktop and mobile
## Prerequisites
* Active Calendly account with at least one event type configured
* Event types should have location set (Zoom, Google Meet, Phone, etc.)
## Important Notes
* **New event types** may take up to 6 hours to sync after creation in Calendly
* **Rescheduling** - Attendees use Calendly's native reschedule link (provided in booking confirmation)
* **All event types sync** - You can't select a subset; all active event types are made available
***
## Next Steps
* Learn how [Buyer Journeys](/buyers-journey) reveal the path to meeting bookings
* Explore [Touchpoints](/touchpoints) to see specific website interactions
* Review [Briefs](/briefs) for pre-meeting insights and context
# HubSpot Meetings
Source: https://docs.customeros.ai/integrations/meetings/hubspot
Track buyer journeys and marketing attribution for HubSpot Scheduler bookings
## What It Does
Connect your HubSpot Scheduler meeting links to CustomerOS to see the complete buyer journey leading up to every meeting booking. Understand which marketing campaigns, content, and website pages drive your most valuable meetings—all while keeping your existing HubSpot workflow intact.
**Uses your existing HubSpot CRM connection** - No additional authentication needed if you've already connected HubSpot CRM to CustomerOS.
## Why It Matters for Marketing
**Meeting Attribution**: See exactly which marketing channels, campaigns, and content pieces drive HubSpot meeting bookings. Connect ad spend directly to booked meetings.
**Buyer Journey Visibility**: Track the complete path from first website visit to booked meeting. Understand how prospects engage with your content before scheduling a call.
**CRM Integration**: Bookings automatically sync to HubSpot CRM with full buyer journey context—contacts, deals, and meeting engagements all connected.
**Lead Quality Insights**: See which sources bring buyers who book meetings versus those who just browse. Optimize for quality, not just quantity.
**Campaign Optimization**: Identify high-performing campaigns that drive qualified meetings. Double down on what converts.
## Use Cases
**Marketing Attribution**: Discover that prospects who read your case study are 4x more likely to book a demo than those who don't. Create more conversion-focused content.
**Content Performance**: Identify which blog posts or landing pages prospects visit before booking. See the content path that drives meetings.
**Channel Analysis**: Understand that LinkedIn campaigns drive more qualified meetings than other channels, even with lower traffic volume.
**Multi-Touch Attribution**: See the combination of touchpoints—first website visit, email campaign, pricing page view, case study download—that lead to meeting bookings.
**Sales Enablement**: Give your sales team full buyer journey context before every HubSpot meeting, automatically synced to CRM.
## How It Works
1. **Use existing connection**: Already connected HubSpot CRM? Your meeting links are automatically discovered
2. **Automatic sync**: All HubSpot Scheduler meeting links sync every 6 hours
3. **Embed the widget**: Add CustomerOS booking widget to your website (or keep existing HubSpot embeds)
4. **Track automatically**: Every booking links to website touchpoints, campaigns, and content engagement
5. **View insights**: See complete buyer journeys, attribution reports, and meeting analytics in CustomerOS
**What Syncs:**
* Your HubSpot Scheduler meeting links (synced automatically every 6 hours)
* Real-time availability when visitors view the booking widget
* Meeting bookings with attendee details, custom form fields, and guest information
* Bookings create engagements in HubSpot CRM automatically
**Bi-directional benefits:** Bookings flow into HubSpot CRM with full buyer journey context attached.
## How to Connect
1. **Connect HubSpot CRM first** (if not already connected) at **Settings → Integrations → CRMs → HubSpot**
2. Your HubSpot Scheduler meeting links are discovered automatically
3. Meeting links appear within 6 hours (usually faster)
4. Start tracking—bookings are attributed to buyer journeys immediately
**Note:** Learn more about the [HubSpot CRM integration](/integrations/crms/hubspot).
## Smart Features
* **Automatic attribution** - Every booking is linked to the prospect's website activity and marketing touchpoints
* **Real-time availability** - Widget displays your actual HubSpot calendar availability
* **Buyer journey tracking** - See every page visit, content download, and campaign touch before the booking
* **CRM sync** - Bookings automatically create engagements in HubSpot CRM
* **Custom form fields** - Collect additional information defined in your HubSpot booking page
* **Guest support** - Allow additional participants if enabled on your meeting link
* **Rescheduling support** - Unlike Calendly, HubSpot API supports native rescheduling
* **Company branding** - Widget displays your company name, logo, and brand colors from HubSpot
## Prerequisites
* Active HubSpot CRM account with HubSpot Scheduler enabled
* At least one active meeting link configured in HubSpot Scheduler
* Connected HubSpot CRM integration in CustomerOS
## Important Notes
* **New meeting links** may take up to 6 hours to sync after creation in HubSpot
* **All meeting links sync** - You can't select a subset; all active meeting links are made available
* **Custom form fields** are automatically pulled from your HubSpot booking page configuration
* **Rescheduling supported** - Unlike Calendly, HubSpot allows full reschedule support via API
***
## Next Steps
* Connect the [HubSpot CRM integration](/integrations/crms/hubspot) first (if not already connected)
* Learn how [Buyer Journeys](/buyers-journey) reveal the path to meeting bookings
* Explore [Touchpoints](/touchpoints) to see specific website interactions
* Review [Briefs](/briefs) for pre-meeting insights and context
# Apollo.io
Source: https://docs.customeros.ai/integrations/outreach/apollo
Push qualified leads to Apollo for prospecting
## What It Does
Pushes qualified CustomerOS leads into Apollo as accounts, enabling sales teams to use Apollo's prospecting tools on your best-fit opportunities.
**Setup:** Register OAuth app in Apollo → Connect to CustomerOS → Configure sync rules → Map users
## Data Flow
### From CustomerOS → Apollo
* **Accounts** created from qualified CustomerOS leads (meeting sync criteria)
* **Company data** syncs: name, domain, website
* **Filters by**: ICP fit (moderate/strong), stage threshold, user assignment
* **Account owner** assigned based on CustomerOS user mapping
* **Updates** sync when CustomerOS lead data changes
### From Apollo → CustomerOS
* **Users** sync for rep assignment
* **User mapping** maintained for attribution
* **Sync status** tracked (created, updated, error)
## What You Can Do
**Auto-push qualified leads**: Leads meeting criteria (ICP fit + stage + user assignment) automatically create Apollo accounts
**Prioritize prospecting**: Sales reps see which Apollo accounts came from CustomerOS qualified leads
**Territory assignment**: Apollo accounts automatically assigned to reps based on CustomerOS user mappings
**Filter by quality**: Only syncs leads with moderate or strong ICP fit, above configured stage threshold
## Smart Features
* **Intelligent filtering**: Only syncs leads meeting ALL criteria (ICP fit + stage + user + not customer)
* **Duplicate prevention**: Checks existing mappings before creating accounts
* **Auto-recovery**: Failed syncs automatically retry with error recovery
* **Owner assignment**: Maps CustomerOS users to Apollo users for automatic ownership
* **Race condition handling**: 5-minute buffer avoids syncing recently modified leads
## Technical Details
* OAuth 2.0 secure authentication
* Bi-directional user sync for rep assignment
* Mapping table tracks CustomerOS leads ↔ Apollo accounts
* Sync status tracking (created, updated, error)
* Batch processing (default 25 leads per batch)
* Scheduled every 15 minutes via cron system
* Automated retry and error recovery
* Supports company-level leads only
## Qualification Criteria
Leads must meet ALL requirements to sync to Apollo:
* Only companies (get in touch for persona prospecting)
* Not already a Customer
* ICP fit: Moderate or Strong
* Stage: Above configured threshold (configurable)
* Quarantine status: Active (not quarantined)
* Company data: Valid name and primary domain
* User assignment: Must have user assigned with Apollo user mapping
* Not already synced to this Apollo connection
# Leads
Source: https://docs.customeros.ai/leads
Learn how CustomerOS defines and manages leads, and how they connect to your ICP and the global company graph.
## What Are Leads in CustomerOS?
In CustomerOS, **leads are companies** — not individuals.\
A lead is a company that:
* Has been matched against your **Ideal Customer Profile (ICP)**
* Shows intent or engagement signals across your channels
* Is exposed to you as a sales opportunity within your workspace
Behind the scenes, every lead is linked to a **central CustomerOS company object**. This means you benefit from our continuously updated **global research layer**, which is re-assessed and re-framed to your specific ICP so that every lead you see is hyper-relevant.
***
## Key Attributes of a Lead
Each lead in CustomerOS includes:
* **Company Profile**\
Firmographic and technographic data (industry, size, tech stack, revenue) enriched from the global company graph.
* **ICP Fit**\
A dynamic assessment of how closely the company aligns to your Ideal Customer Profile.
* **Journey Stage**\
Current stage in the [Buyer's Journey](/buyers-journey): Target, Education, Solution, or Evaluation. High-engagement evaluation leads flag for sales attention.
* **Touchpoints**\
Logged interactions across ads, website, email, or meetings that show how the company is engaging.
* **Lead Briefs & Research**\
Automatically generated summaries of company context, market positioning, and recent activity.
* **Contacts**\
Key people at the company relevant to your sales motion (decision makers, influencers, champions).
***
## Why Leads Matter
* **Single source of truth**: All sales, marketing, and research activities are tied back to the lead.
* **ICP-first approach**: You’ll only see companies that match or nearly match your ICP — no wasted cycles on noise.
* **Continuously refreshed**: Because leads are linked to the CustomerOS company graph, research and insights stay current.
* **Action-ready**: Every lead is assigned a stage, with clear signals on what’s required to progress them.
***
## Working with Leads
* **View & Prioritize** → See all active leads in your workspace, ranked by ICP fit and journey stage.
* **Research** → Use lead briefs to prepare for outreach with contextually relevant insights.
* **Engage** → Trigger outreach sequences or Slack notifications when leads progress stages.
* **Collaborate** → Share notes, assign owners, and coordinate with your team in real-time.
***
## Next Steps
* Explore [Touchpoints](/touchpoints) to see how CustomerOS measures engagement quality.
* Learn how [Briefs](/briefs) give you ready-made research for every lead.
* See how [Contacts](/contacts) connect decision-makers to leads.
# Meeting Intelligence
Source: https://docs.customeros.ai/meeting-transcripts
Automatically extract marketing insights from customer conversations—discover messaging that resonates, content gaps to fill, and positioning opportunities hidden in every call
Keep using Fathom or Grain for call recording. CustomerOS automatically
syncs transcripts and extracts marketing intelligence with zero migration
required.
## The Marketing Intelligence Problem
You're recording sales calls, demos, and customer conversations—but valuable marketing insights remain trapped in individual transcripts. Your meeting recorder (Fathom, Grain) captures *what* was said, but not *how* to use those insights for better content, sharper positioning, or more effective campaigns.
**Common questions you can't answer:**
* What pain points should our content address based on real buyer conversations?
* Which messaging and positioning resonates most with prospects who close?
* What competitor objections come up repeatedly that need better battlecard content?
* Which marketing campaigns drive meetings with qualified, buying-intent conversations?
* What language and terminology do buyers actually use when describing their problems?
* Which content topics and formats would address the most common prospect questions?
**The result:** You have recordings and transcripts, but you're missing the marketing intelligence that drives better content, sharper positioning, and more effective campaigns.
## What CustomerOS Meeting Intelligence Does
CustomerOS automatically syncs transcripts from Fathom and Grain, then extracts actionable marketing intelligence from every conversation. Discover what content to create, which messaging resonates, how to position against competitors, and which campaigns drive the most qualified discussions.
**Key Capabilities:**
* **Automatic Intelligence Extraction** - Every Fathom and Grain recording syncs automatically with AI-powered analysis
* **Content Gap Identification** - Surface the most common questions and pain points that need content to address them
* **Messaging & Positioning Insights** - Discover which value propositions and positioning angles resonate with buyers who close
* **Competitive Intelligence** - Track competitor mentions, objections, and concerns to refine positioning and create targeted content
* **Campaign Quality Analysis** - See which campaigns drive meetings with buying-intent conversations versus exploratory chats
* **Buyer Language Extraction** - Understand the exact terminology and language prospects use to describe their problems
## Marketing Intelligence You'll Get
### Content Strategy Insights
Identify the most frequently asked questions and pain points mentioned in sales calls. Discover that 60% of prospects ask about "data migration timelines" but you have no content addressing it—then create a dedicated guide.
### Messaging That Resonates
Surface which value propositions and benefits prospects respond to positively in calls that close. See that "reduce manual work" resonates 3x better than "increase efficiency" with your target audience.
### Competitive Positioning Intelligence
Track exactly how competitors are mentioned and which concerns come up repeatedly. Discover that prospects worry about Competitor X's "complex onboarding"—then create content and positioning around your simple setup.
### Buyer Language & Terminology
Understand the exact words and phrases prospects use to describe their problems. Find that buyers say "scattered customer data" not "data silos"—then update all your messaging to match their language.
### Content Performance Attribution
See which content prospects engaged with before meetings where they asked qualified questions. Discover that your case studies drive better conversations than whitepapers—then prioritize case study creation.
### Campaign Quality Scoring
Identify which marketing campaigns drive meetings with buying-intent conversations versus basic education. See that LinkedIn thought leadership generates 3x more qualified discussions than paid search.
### Positioning Opportunities
Uncover unmet needs and pain points that competitors aren't addressing. Discover prospects frequently mention "lack of mobile access" across calls—identify a positioning gap to exploit.
## How It Works
1. **Connect your recorder** - Link your Fathom or Grain account via secure OAuth (takes 2 minutes)
2. **Automatic intelligence extraction** - Transcripts sync every 2 hours with AI analysis surfacing marketing insights
3. **Pattern identification** - System identifies common questions, pain points, competitor mentions, and messaging themes
4. **View actionable insights** - Get content recommendations, positioning opportunities, and messaging analysis
5. **Create better marketing** - Use intelligence to build content that addresses real buyer needs and messaging that actually resonates
**No workflow changes required.** Your team keeps using their preferred recording tool. CustomerOS adds the marketing intelligence layer that turns conversations into content strategy.
## Use Cases
**Content Creation Priorities**
Identify the top 10 questions prospects ask repeatedly that you don't have content for. Discover that 45% of prospects ask about "security compliance" in first calls—then create dedicated resources addressing it.
**Messaging Optimization**
Surface which value propositions and benefit statements prospects respond to positively. See that "reduce manual work by 80%" drives engagement while technical features don't—then update homepage messaging.
**Competitive Battlecards**
Track every competitor mention and objection across all calls. Build data-driven battlecards addressing the actual concerns prospects raise about Competitor X's pricing or Competitor Y's complexity.
**Buyer Language Adoption**
Extract the exact terminology prospects use to describe problems. Discover buyers say "juggling multiple tools" not "lack of integration"—then rewrite website copy in their language.
**Campaign Quality Measurement**
Stop measuring campaigns by form fills. See that LinkedIn thought leadership drives meetings where prospects discuss implementation, while paid search drives basic education calls.
**Positioning Strategy**
Uncover pain points and needs that competitors aren't addressing. Find that enterprise prospects mention "audit trails" in 40% of calls but competitors ignore it—then position around this gap.
**Case Study Development**
Identify which customer success stories and use cases prospects ask about most. See that "reducing time-to-value" resonates more than "feature breadth"—then create case studies highlighting quick wins.
**Landing Page Optimization**
Discover which questions prospects have before booking that could be answered on landing pages. Surface that 50% ask about implementation time—then add prominent FAQ addressing it.
## Meeting Intelligence Integrations
CustomerOS works with leading meeting recording platforms. Choose the integration that matches your team's setup:
### [Fathom Meeting Intelligence](/integrations/meeting-transcripts/fathom)
Connect your Fathom account to automatically extract marketing intelligence from every recorded call. Get AI-powered content ideas, positioning insights, and messaging recommendations.
**Best for:** Teams using Fathom for recording Zoom, Google Meet, or Microsoft Teams meetings
**Key Features:** Content gap identification, messaging analysis, competitive intelligence extraction, buyer language insights
### [Grain Meeting Intelligence](/integrations/meeting-transcripts/grain)
Connect your Grain account to automatically extract marketing intelligence from recordings. Uncover positioning opportunities and content strategy from participant conversations.
**Best for:** Teams using Grain for recording and sharing meeting highlights
**Key Features:** Multi-participant insight extraction, buying committee language analysis, content recommendation engine
***
## Best Practices
* **Build your intelligence baseline** - Sync transcripts from day one to accumulate marketing insights over time
* **Monthly content reviews** - Analyze the most common questions and pain points to prioritize content creation
* **Update messaging quarterly** - Review which value props and language resonate in closed deals, then update website copy
* **Competitive monitoring** - Track competitor mentions monthly to keep battlecards and positioning current
* **Language audits** - Extract buyer terminology and update marketing materials to match how prospects actually speak
* **Campaign quality scoring** - Evaluate campaigns by conversation quality, not just meeting volume
* **Positioning gap analysis** - Identify unmet needs mentioned across calls to find positioning opportunities
* **Sales-marketing alignment** - Share conversation insights with marketing to create content that addresses real objections
***
## Next Steps
* Connect [Fathom](/integrations/meeting-transcripts/fathom) to extract marketing intelligence from Fathom recordings
* Connect [Grain](/integrations/meeting-transcripts/grain) to extract marketing intelligence from Grain recordings
* Learn how [Buyer Journeys](/buyers-journey) connect conversation insights to campaigns and content
* Review [Briefs](/briefs) to see conversation history and topics before meetings
* Explore [Touchpoints](/touchpoints) to see website activity that leads to qualified conversations
* Track [Meeting Bookings](/meetings) to understand which campaigns drive meetings worth having
# Meetings
Source: https://docs.customeros.ai/meetings
Track the complete buyer journey behind every meeting booking—see which marketing efforts actually drive demos and sales calls
Keep using Calendly or HubSpot Scheduler. CustomerOS adds marketing
attribution and buyer journey tracking with zero migration required.
## The Meeting Attribution Problem
You're driving traffic, creating content, and running campaigns—but you have no idea which efforts actually drive meeting bookings. Your scheduler (Calendly, HubSpot) tells you *who* booked and *when*, but not *why* they booked or *what journey* led them there.
**Common questions you can't answer:**
* Which marketing campaigns drive the most qualified demo requests?
* What content do prospects consume before booking a sales call?
* How many website visits does it take before someone schedules a meeting?
* Are LinkedIn ads or Google ads driving better meeting quality?
* Which blog posts or landing pages lead to meeting bookings?
**The result:** You're optimizing for traffic and leads, not for what actually matters—booked meetings with qualified buyers.
## What CustomerOS Meetings Does
CustomerOS connects to your existing meeting scheduler (Calendly or HubSpot) and tracks the complete buyer journey leading up to every booking. You get full marketing attribution without changing your workflow.
**Key Capabilities:**
* **Meeting Attribution** - See exactly which campaigns, channels, and content drive meeting bookings
* **Buyer Journey Tracking** - View every website visit, content engagement, and touchpoint before the booking
* **Multi-Touch Attribution** - Understand the combination of marketing efforts that lead to meetings
* **Pipeline Intelligence** - Connect meeting bookings to closed deals and calculate true campaign ROI
* **Lead Quality Insights** - Identify which sources bring buyers who actually book meetings vs. those who just browse
## Marketing Insights You'll Get
### Campaign Performance
See which marketing campaigns drive meetings, not just clicks or form fills. Know your LinkedIn campaign drove 15 qualified demos last month while Google Ads only drove 3—then adjust budget accordingly.
### Content Attribution
Identify which blog posts, case studies, or landing pages prospects read before booking. Discover that prospects who read your ROI calculator page are 5x more likely to book a demo.
### Channel Analysis
Understand which marketing channels bring high-intent buyers who book meetings. Stop wasting budget on channels that drive traffic but not conversions.
### Buyer Journey Patterns
See how many touchpoints it takes before prospects book meetings. Discover that qualified buyers typically visit 3-5 pages over 2 weeks before scheduling a call.
### True ROI Calculation
Connect meeting bookings back to ad spend and forward to closed deals. Calculate actual campaign ROI from first click to closed won.
## How It Works
1. **Connect your scheduler** - Link your Calendly or HubSpot Scheduler account (takes 2 minutes)
2. **Automatic tracking starts** - Every meeting booking is automatically linked to the prospect's website activity
3. **View buyer journeys** - See the complete path from first visit to booked meeting for every prospect
4. **Optimize campaigns** - Use insights to double down on marketing that drives meetings, cut what doesn't
**No migration required.** Your team keeps using the same booking links. CustomerOS adds the attribution layer behind the scenes.
## Use Cases
**Marketing Attribution**
Stop guessing which campaigns drive meetings. See definitive data on which efforts convert browsers into bookers.
**Content Strategy**
Identify high-converting content that drives meeting bookings. Create more of what actually works.
**Budget Allocation**
Shift marketing spend toward channels and campaigns that drive qualified meetings, not just traffic.
**Sales Enablement**
Give sales teams full buyer journey context before every meeting—what the prospect viewed, downloaded, and engaged with.
**Pipeline Forecasting**
Understand leading indicators of meeting bookings to better forecast pipeline and revenue.
## Meeting Integrations
CustomerOS works with your existing meeting scheduler. Choose the integration that matches your setup:
### [Calendly](/integrations/meetings/calendly)
Connect your Calendly account to track meeting bookings with full buyer journey analytics. Keep your existing Calendly workflow while gaining marketing attribution.
**Best for:** Teams using Calendly for meeting scheduling
### [HubSpot Meetings](/integrations/meetings/hubspot)
Connect HubSpot Scheduler to track meeting bookings and automatically sync to HubSpot CRM with buyer journey context.
**Best for:** Teams using HubSpot CRM and HubSpot Scheduler
### [Cal.com](/integrations/meetings/calcom)
Connect your Cal.com account to track meeting bookings with full buyer journey analytics. Works with both Cal.com cloud and self-hosted instances.
**Best for:** Teams using Cal.com, especially those with self-hosted instances or who value open-source solutions
***
## Best Practices
* **Track attribution from day one** - Connect your meeting scheduler early to build historical data on what drives bookings
* **Review buyer journeys regularly** - Look at the paths prospects take before booking to identify patterns
* **Test and optimize** - Use insights to test new campaigns, content, and channels focused on driving meetings
* **Align with sales** - Share buyer journey insights with sales teams for better pre-meeting prep
* **Calculate true ROI** - Connect meeting data to closed deals to understand full-funnel campaign performance
***
## Next Steps
* Connect [Calendly](/integrations/meetings/calendly) to track Calendly bookings
* Connect [HubSpot Meetings](/integrations/meetings/hubspot) to track HubSpot Scheduler bookings
* Connect [Cal.com](/integrations/meetings/calcom) to track Cal.com bookings (cloud or self-hosted)
* Learn how [Buyer Journeys](/buyers-journey) reveal the complete path to booking
* Explore [Touchpoints](/touchpoints) to see specific website interactions
* Review [Briefs](/briefs) for pre-meeting insights and context
# Notifications
Source: https://docs.customeros.ai/notifications
Stay on top of leads and pipeline health with automated daily and weekly updates from CustomerOS.
## Daily Lead Digest
CustomerOS delivers a daily snapshot of new leads, changes in buying stage, and accounts showing notable activity surges or slow-downs. This keeps your team aligned on where momentum is building (or fading) in real time.
## Weekly Pipeline Update
Each week, CustomerOS provides a summary of your pipeline health along with recommended next steps. These updates highlight key risks, opportunities, and ensure ready-to-buy prospects are surfaced automatically—so your team can focus on action, not admin.
***
## Delivery Channels
Notifications are delivered where your team already works, so no insights get lost:
* **Email** → Daily and weekly summaries in your inbox for broader visibility.
# Quickstart
Source: https://docs.customeros.ai/quickstart
Get started with CustomerOS in four simple steps — from setup to seeing your first leads.
## Quickstart
CustomerOS is designed to deliver value fast.\
Follow these four steps to go from setup → live tracking → seeing your first ICP-fit leads and their buying stage.
***
### 1. Book Your Setup Call
* Schedule an onboarding session with the CustomerOS team.
* We’ll walk you through configuration, answer questions, and ensure you’re ready to capture value from day one.
Use the in-app link or [book a call](https://cal.com/mbrown/20min) with our
team to get started.
### 2. Integrate the First-Party Tracker
* Add the CustomerOS tracking snippet to your website.
* This enables us to identify anonymous visitors, resolve companies, and connect behavior to your pipeline.
* Once installed, you’ll begin seeing traffic identified in real time.
### 3. Connect Your CRM & Ad Platforms
* Link your CRM (HubSpot, Salesforce, etc.) so CustomerOS can unify deals, contracts, and pipeline data.
* Connect your ad platforms (Google Ads, LinkedIn, Microsoft Ads) to attribute campaigns and measure ICP pipeline creation.
* The integrations are designed to be **one-click** and sync automatically.
### 4. See Your Leads & Their Buying Stage
* Once integrations are live, CustomerOS surfaces ICP-fit leads in your dashboard.
* Every account shows **ICP fit**, classified by **buying stage** (Target, Education, Solution, Evaluation), and enriched with firmographic details.
* Sales can immediately prioritize high-engagement leads needing attention, while marketing can nurture leads in earlier stages.
***
## Next Steps
* Explore the [Reporting](/insights) dashboards for real-time pipeline visibility.
* Review the [Integrations](/integrations) guide to connect additional tools.
* Dive into [Use Cases](/index#example-use-cases) to see how teams apply CustomerOS to win more revenue.
# Security & Compliance
Source: https://docs.customeros.ai/security-and-compliance
CustomerOS maintains a strong security posture as one of it\'s highest values
## Access Management
CustomerOS has 3 types of user access management: our own, 3rd party SSOs and BYO (using OpenID Connect).
### 1. Magic Link
The most basic way of logging into CustomerOS is to provide your email and CustomerOS sends you a one-time unique login link.
### 2. SSO with Google & Microsoft
To enable SSO reach out to support and we will get you set up!
The recommended way of logging into CustomerOS is to use Google's and Microsoft's SSO feature, so that you can easily import your customer data to CustomerOS.
This method also inherits the security related to your Google or Microsoft account, such as 2FA or biometric security, so if you lose access or control of your account you can manage the security of your customer data in one place.
### 3. OpenID Connect
To enable OpenID Connect reach out to support and we will get you set up!
Finally we also support OpenID Connect as a user access management standard. We support self-hosted, open source solutions such as KeyCloak amongst others. To enable for your workspace, first create a workspace either using a Magic Link or Google/Microsoft SSO for an email address that has the same domain as you use for OpenID Connect. Once this is done then reach out to support with the following information:
1. Discovery URL
2. Client ID
3. Client Secret
We will update your workspace which will change the magic link login into an OpenID Connect for the domain you specify.
If you require additional login security such as 2FA or other SSO/SAML
providers, please reach out.
## Compliance
### GDPR
CustomerOS is fully compliant with GDPR. Any data removal request is possible both within your workspace and within CustomerOS as a whole.
You can find more information on our web tracker's page regarding it's specific compliance with GDPR.
Reach out to support if you require more information on how CustomerOS helps
you remain GDPR compliant, or if you have a data removal request that we can
help with as part of your, or your users rights under EU and UK law.
## Certifications
### CASA Type 2 (Google Security Certification)
As we provide tight integrations with Google, we are audited and certified by the CASA security standard.
We are recertified on a yearly basis, and this certification includes code vulnerability scanning.
## 3rd Party Data Processors
As a European-based company, we pride ourselves on our data security and confidentiality. All data is stored encrypted and any data that leaves our own servers and applications goes to vendors that have been vetted for their own data security policies, processes and overall data safety.
For more information on which 3rd parties we work with to provide you a better experience, find more information in our [Data Processing Agreement](https://customeros.ai/standard-agreement/dpa).
# Touchpoints
Source: https://docs.customeros.ai/touchpoints
Understand how CustomerOS tracks meaningful engagement events that drive buyer journey progression.
## What Are Touchpoints?
In CustomerOS, **touchpoints are meaningful engagement events** between a company (lead) and your brand.\
They capture *quality interactions* that demonstrate intent and help move a lead forward in the [Buyer’s Journey](/buyers-journey).
Not every interaction creates a touchpoint. For example, a web session where someone immediately bounces won’t count. Only engagements that show real **attention, consumption, or intent** are recorded as touchpoints.
***
## Types of Touchpoints
Touchpoints can be generated across multiple channels:
* **Website** → Page visits with high attention ratios, downloads, or tool usage
* **Content** → Whitepaper downloads, case study reads, webinar attendance
* **Advertising** → Meaningful ad engagements that lead to on-site interaction
* **Email** → Click-throughs and deep engagement (not just opens)
* **Meetings** → Booked or attended demos, consultations, or events
* **Forms** → Submissions or assessments completed
* **Documents** → Interactions with proposals, pricing, or contracts
***
## What Makes a Touchpoint "Meaningful"?
CustomerOS applies filters so only high-quality interactions count as touchpoints:
* **Attention Ratio**\
Time spent ÷ expected reading/viewing time
* > 1.0 = meaningful (likely a touchpoint)
* \<0.5 = noise (no touchpoint created)
* **Engagement Depth**\
Downloads, video completions, tool results, or form fills get higher weight than simple clicks.
* **Recency & Frequency**\
Consistent or repeat engagement is logged as touchpoints, while sporadic clicks may not be.
* **Channel Attribution**\
Direct visits, search-driven interactions, and referrals often carry higher intent than broad display ads.
***
## Why Touchpoints Matter
* **Stage Progression** → Lead stage movement depends more on *quality* of touchpoints than quantity.
* **Sales Context** → Each touchpoint enriches the lead’s brief with actionable signals.
* **Noise Reduction** → You see only interactions that actually matter for pipeline creation.
* **Forecasting** → Touchpoint velocity helps predict when leads will move stages.
***
## Example
* A user spends **25 minutes** reading a 15-minute industry report → ✅ Touchpoint created (high attention).
* A user lands on a pricing page and leaves after **10 seconds** → ❌ No touchpoint created.
* A company books a **demo meeting** → ✅ Touchpoint created (auto high-score).
***
## Next Steps
* Learn how [Leads](/leads) are enriched with touchpoints.
* See how [Briefs](/briefs) summarize key interactions for easy sales prep.
* Explore [Notifications](/notifications) to stay updated on new or important touchpoints.
# Custom Events
Source: https://docs.customeros.ai/tracker/custom-events
Currently in Alpha, please reach out if you have a use case that would
benefit from Custom Signal tracking
# Docusaurus
Source: https://docs.customeros.ai/tracker/docusaurus
Install the CustomerOS tracker on your Docusaurus documentation site
## Overview
Docusaurus allows you to add custom scripts to your documentation site through the `docusaurus.config.js` configuration file. Scripts are automatically included in the `` section of every page.
## Installation
Get the HTML Snippet from the CustomerOS app to add to your website. It is specific to your domain so that you aren't blocked by adblockers and privacy modes.
### Adding the Tracker Script
1. In your Docusaurus project's `src` directory, create a new JavaScript file:
```bash theme={"system"}
touch src/customeros-tracker.js
```
2. Open `src/customeros-tracker.js` and paste the JavaScript code from the CustomerOS app
3. Open your `docusaurus.config.js` file and add the script to the `scripts` array:
```javascript theme={"system"}
module.exports = {
// ... other configurations ...
scripts: ["/src/customeros-tracker.js"],
// ... other configurations ...
};
```
4. Save the file and restart your development server:
```bash theme={"system"}
npm start
# or
yarn start
```
5. Build and deploy your site:
```bash theme={"system"}
npm run build
# or
yarn build
```
The tracker will now be included on all pages of your documentation.
The JavaScript file should be placed in the `src` directory, and the path in
`scripts` should start with `/`.
## Alternative: Page-Specific Installation
If you only want to track specific pages, you can create a custom component that includes the tracker script:
1. Create a component file (e.g., `src/components/CustomerOSTracker.js`):
```javascript theme={"system"}
import { useEffect } from "react";
export default function CustomerOSTracker() {
useEffect(() => {
// Paste the JavaScript code from the CustomerOS app here
(function () {
const SRC =
"https://your-tracker-subdomain.example.com/analytics-0.1.js";
const ID = "customeros-metrics-loader";
// ... rest of the JavaScript code from the app
})();
}, []);
return null; // This component doesn't render anything
}
```
2. Import and use the component in any page where you want tracking:
```javascript theme={"system"}
import CustomerOSTracker from "../components/CustomerOSTracker";
function MyPage() {
return (
<>
{/* Page content */}
);
}
export default MyPage;
```
## Verifying Installation
After building and deploying your site:
1. Visit your Docusaurus documentation
2. Open your browser's developer console (F12 or right-click → Inspect)
3. Check the **Network** tab for a request to your tracker domain
4. Look for successful 200s and 202s from the tracker subdomain
5. Check the **Console** tab for any errors
You should see page views appearing in your CustomerOS dashboard within a few minutes.
## Troubleshooting
If the tracker isn't working:
* Ensure the JavaScript file is in the `src` directory
* Check that the script path is correctly added to `docusaurus.config.js` in the `scripts` array
* Verify the path starts with `/` (e.g., `/src/customeros-tracker.js`)
* Ensure you've restarted your development server after making changes
* Check that you've built and deployed your site (changes don't appear in development mode)
* Verify that your tracker domain is correct and accessible
* Check the browser console for any JavaScript errors
For more help, see our [Troubleshooting guide](/tracker/troubleshooting).
## Additional Resources
* [Docusaurus Scripts Documentation](https://docusaurus.io/docs/api/docusaurus-config#scripts)
* [Custom Events Tracking](/tracker/custom-events)
* [Website Tracker Overview](/tracker)
# Fern
Source: https://docs.customeros.ai/tracker/fern
Install the CustomerOS tracker on your Fern documentation site
## Overview
Fern allows you to add custom JavaScript to your documentation site through the `docs.yml` configuration file. This enables you to include the CustomerOS tracker across all pages.
## Installation
Get the JavaScript snippet from the CustomerOS app - it's specific to your domain so that you aren't blocked by adblockers and privacy modes.
1. In your Fern project, create a JavaScript file for the tracker:
```bash theme={"system"}
mkdir -p fern/js
touch fern/js/customeros-tracker.js
```
2. Open `fern/js/customeros-tracker.js` and paste the JavaScript code from the CustomerOS app
3. Update your `docs.yml` file to include the custom JavaScript:
```yaml theme={"system"}
js:
- path: ./js/customeros-tracker.js
```
4. Commit and push your changes:
```bash theme={"system"}
git add fern/js/customeros-tracker.js fern/docs.yml
git commit -m "Add CustomerOS tracker"
git push
```
5. Deploy your Fern documentation
The tracker will now be included on all pages of your documentation.
Make sure the path in your `docs.yml` correctly points to your JavaScript
file location.
## Verifying Installation
After deploying your site:
1. Visit your Fern documentation
2. Open your browser's developer console (F12 or right-click → Inspect)
3. Check the **Network** tab for a request to your tracker domain
4. Look for successful 200s and 202s from the tracker subdomain
5. Check the **Console** tab for any errors
You should see page views appearing in your CustomerOS dashboard within a few minutes.
## Troubleshooting
If the tracker isn't working:
* Ensure the JavaScript file path in `docs.yml` is correct
* Check that you've deployed the changes to your Fern site
* Verify that your tracker domain is correct and accessible
* Check the browser console for any JavaScript errors
For more help, see our [Troubleshooting guide](/tracker/troubleshooting).
## Additional Resources
* [Fern Custom JavaScript Documentation](https://buildwithfern.com/learn/docs/customization/custom-css-js)
* [Custom Events Tracking](/tracker/custom-events)
* [Website Tracker Overview](/tracker)
# Framer
Source: https://docs.customeros.ai/tracker/framer
Install the CustomerOS tracker on your Framer website
## Overview
Framer allows you to add custom code to your website through the Custom Code settings. You can add the CustomerOS tracker to your entire site or to individual pages.
## Installation
Find the HTML Snippet in the CustomerOS app to add to your website. It is specific to your domain so that you aren't blocked by adblockers and privacy modes.
### Option 1: Site-Wide Installation (Recommended)
To add the tracker to your entire Framer site:
1. Open your Framer project
2. Click on the **Settings** icon (gear icon) in the top-right corner
3. Scroll down to the **Custom Code** section
4. Under **Start of `` tag**, paste the CustomerOS tracker script
5. Click **Save**
### Option 2: Single Page Installation
To add the tracker to a specific page:
1. Navigate to the page you want to track
2. Click on the **Settings** option in the page's menu
3. Scroll to the **Custom Code** section
4. Under **Start of `` tag**, paste the CustomerOS tracker script
5. Click **Save**
For most use cases, we recommend site-wide installation to track visitors
across all pages of your website.
## Verifying Installation
After adding the tracker script and publishing your site:
1. Visit your Framer site
2. Open your browser's developer console (F12 or right-click → Inspect)
3. Check the **Network** tab for a request to your tracker domain
4. Look for successful 200s and 202s from the tracker subdomain
5. Check the **Console** tab for any errors
You should see page views appearing in your CustomerOS dashboard within a few minutes.
We automatically handle capturing information from form submissions in
Framer, you don't need to do anything differently to capture this signal!
## Troubleshooting
If the tracker isn't working:
* Ensure you've published your site (the tracker won't work in preview mode)
* Check that your tracker domain is correct and accessible
* Verify that the script is in the **Start of `` tag** section
* Check the browser console for any JavaScript errors
For more help, see our [Troubleshooting guide](/tracker/troubleshooting).
## Additional Resources
* [Framer Custom Code Documentation](https://www.framer.com/academy/lessons/custom-code)
* [Custom Events Tracking](/tracker/custom-events)
* [Website Tracker Overview](/tracker)
# GitBook
Source: https://docs.customeros.ai/tracker/gitbook
CustomerOS tracker integration for GitBook documentation
## Custom Code Not Supported
Unfortunately GitBook does not currently support adding custom code or JavaScript to documentation sites through their platform.
## Official Integration Available
If you need to track visitors on your GitBook documentation, please reach out to our team at [help@customeros.ai](mailto:help@customeros.ai) and we can explore creating an official GitBook integration for CustomerOS.
We're always looking to expand our integrations to support the platforms our customers use!
## Additional Resources
* [Website Tracker Overview](/tracker)
* [Contact Support](mailto:help@customeros.ai)
# Google Tag Manager
Source: https://docs.customeros.ai/tracker/google-tag-manager
Install the CustomerOS tracker via Google Tag Manager (not recommended)
We don't recommend using Google Tag Manager as the majority of modern
browsers who block scripts and trackers will prevent any scripts loading
from Google Tag Manager. If you are okay with reducing the amount of signal
that CustomerOS can collect, then you can install it using the following
steps.
## Installation
Find the HTML Snippet in the CustomerOS app to add to your website.
1. Log in to [Google Tag Manager](https://tagmanager.google.com/)
2. Select your container
3. Click **Add a new tag**
4. Click **Tag Configuration** and choose **Custom HTML**
5. Paste the CustomerOS tracker script from the app
6. Under **Triggering**, select **All Pages**
7. Click **Save**
8. Click **Submit** to publish your changes
That's it. The tracker should now load on all pages where your GTM container is installed.
## Additional Resources
* [Website Tracker Overview](/tracker)
* [Troubleshooting guide](/tracker/troubleshooting)
# Website Tracker
Source: https://docs.customeros.ai/tracker/index
Track visitor behavior and identify users on your website
## Overview
The CustomerOS website tracker allows you to monitor visitor behavior and identify users across your website. Once installed, it automatically tracks page views and custom events, providing valuable insights into how visitors interact with your site.
## Installation
To install the CustomerOS tracker, follow the instructions in the app with your specific reverse-proxied domain. Choose between the HTML script or JavaScript snippet depending on the application you are using.
## Identifying Users
Once the tracker script is loaded, you can identify users and attach custom properties to their profile using the `identify` function.
### Basic Usage
```javascript theme={"system"}
window.cos.identify({
email: "user@example.com",
name: "John Doe",
});
```
### When to Use Identify
Call the `identify` function at key moments in your user journey:
* **After user login**: Identify the user with their profile information
* **After signup**: Capture new user details
* **On profile updates**: Update user properties when they change
* **On page load (for authenticated users)**: Ensure returning users are identified
### Example: Identify on Login
```javascript theme={"system"}
// After successful login
async function handleLogin(email, password) {
const user = await loginUser(email, password);
// Identify the user in CustomerOS
window.cos.identify({
email: user.email,
name: user.name,
user_id: user.id,
plan: user.subscription.plan,
});
}
```
### Disabling Automatic Event Tracking
By default, the tracker automatically captures page views and events. If you want to disable automatic event tracking and only track events manually, set the `c.__disableCosEvents__` parameter to `true`.
This is especially helpful for preventing unwanted collection of data within applications where PII and other data may be sent and received.
```html HTML Script {12} theme={"system"}
```
```javascript JavaScript {15} theme={"system"}
(function () {
const SRC = "https://reverse-proxy.example.com/analytics-0.1.js";
const ID = "customeros-metrics-loader";
function inject() {
if (
!document.getElementById(ID) &&
!document.querySelector('script[src="' + SRC + "']")
) {
const s = document.createElement("script");
s.id = ID;
s.async = true;
s.src = SRC;
window.__disableCosEvents__ = true;
(document.head || document.body).appendChild(s);
}
}
document.readyState === "loading"
? document.addEventListener("DOMContentLoaded", inject)
: inject();
})();
```
## Platform-Specific Guides
For specific implementation instructions for your platform, see the guides below:
Install on Webflow sites
Install on Framer sites
Install on Mintlify docs
Install via Google Tag Manager
Install on GitBook docs
Install on Docusaurus sites
Install on Fern docs
Install on Scalar API docs
## Troubleshooting
Having issues with the tracker? Check out our [troubleshooting guide](/tracker/troubleshooting) for common solutions.
# Mintlify
Source: https://docs.customeros.ai/tracker/mintlify
Install the CustomerOS tracker on your Mintlify documentation site
## Overview
Mintlify allows you to add custom JavaScript files to your documentation site through the `docs.json` configuration file. Custom scripts are included across all pages of your documentation.
## Installation
Get the JavaScript snippet from the CustomerOS app - it's specific to your domain so that you aren't blocked by adblockers and privacy modes.
1. In your Mintlify project's root directory, create a new JavaScript file:
```bash theme={"system"}
touch customeros-tracker.js
```
2. Open `customeros-tracker.js` and paste the JavaScript code from the CustomerOS app
3. Update your `docs.json` file to include the custom script:
```json theme={"system"}
{
"settings": {
"customScripts": ["/customeros-tracker.js"]
}
}
```
If you already have a `settings` section, just add the script to the `customScripts` array:
```json theme={"system"}
{
"settings": {
"customScripts": ["/customeros-tracker.js", "/other-script.js"]
}
}
```
4. Commit and push the files to your repository:
```bash theme={"system"}
git add customeros-tracker.js docs.json
git commit -m "Add CustomerOS tracker"
git push
```
5. Deploy your Mintlify site
The tracker will now be automatically included on all pages of your documentation.
The JavaScript file should be placed in the root directory of your Mintlify
project, and the path in `docs.json` should start with `/`.
## Verifying Installation
After deploying your site:
1. Visit your Mintlify documentation
2. Open your browser's developer console (F12 or right-click → Inspect)
3. Check the **Network** tab for a request to your tracker domain
4. Look for successful 200s and 202s from the tracker subdomain
5. Check the **Console** tab for any errors
You should see page views appearing in your CustomerOS dashboard within a few minutes.
## Troubleshooting
If the tracker isn't working:
* Ensure the `.js` file is in the root directory of your project
* Check that the script path is correctly added to `docs.json` in the `settings.customScripts` array
* Verify the path starts with `/` (e.g., `/customeros-tracker.js`)
* Check that you've deployed the changes to your Mintlify site
* Verify that your tracker domain is correct and accessible
* Check the browser console for any JavaScript errors
For more help, see our [Troubleshooting guide](/tracker/troubleshooting).
## Additional Resources
* [Mintlify Custom Scripts Documentation](https://mintlify.com/docs/settings/custom-scripts)
* [Custom Events Tracking](/tracker/custom-events)
* [Website Tracker Overview](/tracker)
# Scalar
Source: https://docs.customeros.ai/tracker/scalar
Install the CustomerOS tracker on your Scalar API documentation
## Overview
Scalar allows you to inject custom JavaScript code into your API documentation through the Customize panel. You can add the CustomerOS tracker to the `` section of your documentation.
## Installation
Get the HTML Snippet from the CustomerOS app to add to your website. It is specific to your domain so that you aren't blocked by adblockers and privacy modes.
### Adding the Tracker Script
1. Open your Scalar documentation project
2. In the top right corner, click **Customize**
3. Click on the **Code** tab
4. In the **"In ``"** section, paste the CustomerOS tracker script
5. Click **Save** or **Publish** your documentation
The tracker will now be included on all pages of your documentation.
The script should be placed in the "In ``" section, not in the "After ``" section.
## Verifying Installation
After publishing your documentation:
1. Visit your Scalar documentation site
2. Open your browser's developer console (F12 or right-click → Inspect)
3. Check the **Network** tab for a request to your tracker domain
4. Look for successful 200s and 202s from the tracker subdomain
5. Check the **Console** tab for any errors
You should see page views appearing in your CustomerOS dashboard within a few minutes.
## Troubleshooting
If the tracker isn't working:
* Ensure you've published your documentation (the tracker won't work in preview mode)
* Check that your tracker domain is correct and accessible
* Verify that the script is in the **"In ``"** section
* Check the browser console for any JavaScript errors
For more help, see our [Troubleshooting guide](/tracker/troubleshooting).
## Additional Resources
* [Scalar Documentation](https://scalar.com/docs)
* [Custom Events Tracking](/tracker/custom-events)
* [Website Tracker Overview](/tracker)
# null
Source: https://docs.customeros.ai/tracker/troubleshooting
# Troubleshooting
## Content Security Policy (CSP) Issues
### Identifying CSP Errors
If the CustomerOS tracker is not working, check your browser's console for CSP-related errors. Common CSP errors look like:
```
Refused to connect to 'https://api64.ipify.org/?format=json' because it violates the following Content Security Policy directive...
```
or
```
Fetch API cannot load https://api64.ipify.org/?format=json
```
### Required Domains
The CustomerOS tracker needs to make requests to the following domains to function properly:
* **`api64.ipify.org`** - Used to detect the visitor's IP address for accurate geolocation
### How to Resolve CSP Issues
If you're using AWS CloudFront, you can add a Response Headers Policy:
1. Go to CloudFront → Policies → Response Headers
2. Edit your policy or create a new one
3. Add to the `connect-src` directive:
* `https://api64.ipify.org`
* Your CustomerOS tracker domain
4. Save the policy
Changes to CloudFront policies typically take 10-15 minutes to propagate globally
Add or modify the `Content-Security-Policy` header in your server configuration:
```
Content-Security-Policy: connect-src 'self' https://api64.ipify.org https://your-customeros-domain.com
```
**Apache (.htaccess)**
```apache theme={"system"}
Header set Content-Security-Policy "connect-src 'self' https://api64.ipify.org https://your-customeros-domain.com"
```
**Nginx**
```nginx theme={"system"}
add_header Content-Security-Policy "connect-src 'self' https://api64.ipify.org https://your-customeros-domain.com";
```
Add a meta tag to your HTML ``:
```html theme={"system"}
```
This method is less recommended as it only applies to the page itself, not scripts loaded from it
Add a `_headers` file to your project root or public directory:
```
/*
Content-Security-Policy: connect-src 'self' https://api64.ipify.org https://your-customeros-domain.com
```
Or use the platform's dashboard to configure security headers.
### Verifying the Fix
After updating your CSP configuration:
1. Clear your browser cache
2. Wait for the changes to propagate (10-15 minutes for CDN changes)
3. Reload your website
4. Check the browser console - CSP errors should be gone
5. Verify that tracking events are being captured in CustomerOS
### Still Having Issues?
If you're still experiencing problems after configuring CSP:
* Check that all required domains are included in your CSP policy
* Verify that your CSP policy isn't being overridden by another security layer
* Ensure the tracker script is loading correctly (check Network tab in DevTools)
* Contact support with your browser console errors for additional help
# Webflow
Source: https://docs.customeros.ai/tracker/webflow
Install the CustomerOS tracker on your Webflow website
## Overview
Webflow allows you to add custom code to your website through the Custom Code settings in both the Designer and Site Settings. You can add the CustomerOS tracker to your entire site or to individual pages.
## Installation
Find the HTML Snippet in the CustomerOS app to add to your website. It is specific to your domain so that you aren't blocked by adblockers and privacy modes.
### Option 1: Site-Wide Installation (Recommended)
To add the tracker to your entire Webflow site:
1. Open your Webflow project in the **Designer**
2. Click on **Settings** (gear icon) in the left sidebar
3. Navigate to the **Custom Code** tab
4. Under **Head Code**, paste the CustomerOS tracker script
5. Click **Save Changes**
6. Publish your site for the changes to take effect
### Option 2: Single Page Installation
To add the tracker to a specific page:
1. In the **Designer**, navigate to the page you want to track
2. Open **Pages** panel (press **P** or click the pages icon)
3. Click the settings icon next to the page name
4. Scroll to the **Custom Code** section
5. Under **Head Code**, paste the CustomerOS tracker script
6. Click **Save**
7. Publish your site for the changes to take effect
For most use cases, we recommend site-wide installation to track visitors
across all pages of your website.
## Verifying Installation
After adding the tracker script and publishing your site:
1. Visit your Webflow site
2. Open your browser's developer console (F12 or right-click → Inspect)
3. Check the **Network** tab for a request to your tracker domain
4. Look for successful 200s and 202s from the tracker subdomain
5. Check the **Console** tab for any errors
You should see page views appearing in your CustomerOS dashboard within a few minutes.
We automatically handle capturing information from form submissions in
Webflow, you don't need to do anything differently to capture this signal!
## Troubleshooting
If the tracker isn't working:
* Ensure you've published your site (the tracker won't work in the Designer preview)
* Check that your tracker domain is correct and accessible
* Verify that the script is in the **Head Code** section (not Footer Code)
* Check the browser console for any JavaScript errors
* If using Webflow hosting, ensure your custom code is enabled on your plan
For more help, see our [Troubleshooting guide](/tracker/troubleshooting).
## Additional Resources
* [Webflow Custom Code Documentation](https://help.webflow.com/hc/en-us/articles/33961357265299-Custom-code-in-head-and-body-tags)
* [Custom Events Tracking](/tracker/custom-events)
* [Website Tracker Overview](/tracker)
# Use Cases
Source: https://docs.customeros.ai/use-cases
See how CustomerOS helps sales and marketing teams identify, engage, and measure pipeline that actually matters.
## Use Cases
CustomerOS gives B2B revenue teams clarity on which accounts matter, when to act, and how to prove impact.\
Below are common use cases where teams see immediate value.
***
### 1. Identify: See the Right Opportunities
* **Website Visitor Identification** → Reveal anonymous traffic and connect it to real companies.
* **ICP Fit Analysis** → Filter out noise by automatically assessing accounts against your Ideal and Aspirational Customer Profiles.
* **Buying Stage Detection** → Classify leads as Target, Education, Solution, or Evaluation based on live behavior. Flag high-engagement evaluation leads for sales attention.
### 2. Engage: Take the Right Action
* **Lead Routing & Alerts** → Send high-intent accounts to the right rep in real time via Slack or CRM.
* **Sales Briefs** → Arm reps with firmographic, technographic, and contact details for targeted outreach.
* **Content & Campaign Orchestration** → Trigger personalized emails, ads, and follow-ups based on buying stage.
* **Surge & Cool-Down Tracking** → Know when an account suddenly spikes in activity—or goes cold—so you can act fast.
### 3. Measure: Prove What’s Working
* **Content Performance** → See which articles, guides, or case studies actually influence pipeline progression.
* **Ad Campaign Performance** → Track which campaigns generate ICP-fit opportunities (and which waste budget).
* **Pipeline Health** → Monitor velocity, conversion, and drop-off points across your funnel.
* **Attribution & ROI** → Connect marketing activities directly to revenue impact.
***
## Next Steps
* Start with the [Quickstart](/quickstart) guide to connect your data.
* Explore [Insights](/insights) to measure impact.
* Learn about [Notifications](/notifications) to keep your team aligned on pipeline shifts.
# Track Website Visitors
Source: https://docs.customeros.ai/website-tracker
Track your website visitors using our simple tracker
CustomerOS can identify 30-40% of the companies that your website visitors work from their IP address. To get started, you need to provide your domain(s) to the CustomerOS team in order to link the visitors to your website to your CustomerOS Workspace.
We will set up a reverse proxy for you to use to maximise the amount of users you can receive events from, without causing too much technical complexity. All you need to do is add a CNAME DNS record to your websites domain that will allow us to have our reverse proxy behind your domain.
During a setup call you will add the following script tag to the `Header` of your website, replacing the URL domain with that of your new reverse proxy
Once done, the CustomerOS team will verify that this is working, and if not will help troubleshoot any issues identifying traffic.
With the tracker working, all ICP fit organizations from your web traffic will be created as leads in your workspace, and usage added as a [Touchpoint](/touchpoints) to the respective [Lead](/leads).
**Common Error:** If you use a Content Security Policy (CSP) list to block
websites please add `ipify.org` to your website's list. CustomerOS uses
`ipify.org` to log the users IP address.
## GDPR Compliance
**TL;DR** Website Visitor Identification is GDPR compliant.
1. CustomerOS falls under the basis of "legitimate interest" under GDPR rules
2. We recommend that you state your usage of CustomerOS in any places you list your use of other software that utilizes customer data
3. We recommend that you update your cookie policy to indicate that CustomerOS may set a cookie named 'CosUserId', with a lifetime of the remainder of the user's session, and with the purpose to distinguish between visitors.
CustomerOS's tracker collects data of your website's visitors to our infrastructure and our partner infrastructure hosted on AWS (Amazon Web Services), located in Dublin, Ireland (eu-west-1) and Frankfurt, Germany (eu-central-1) respectively. All collected data is encrypted both on transfer and while at rest.
We collect behavioral data of all your website's visitors. This includes; the pages they viewed, by which source they were referred, and how much time they spent on your site.
We process your visitors' IP addresses which we match against our proprietary database to check the company behind the visit and their geographic location. All visitor data is then aggregated at the company level.
Our legal justification falls under legitimate interest. We do not share a visitor's IP address and provide our customers only with publicly accessible corporate data, which is exempt from GDPR.
> "processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child."
*See [Art. 6(f) GDPR - Lawfulness of processing](https://gdpr-info.eu/art-6-gdpr/) for reference.*
When it comes to B2B marketing and analytics, legitimate interest is the most suitable basis, and commonly used. The justification of "legitimate interest" is based on the simple ground that the individual whose visit data is processed could have a legitimate interest in what you're offering them.
Furthermore, CustomerOS's focus is on providing business identifications rather than data on a personal level. For that reason, CustomerOS uses personal data to a minimal extent.
### Cookies
The CustomerOS tracker sets a cookie in the visitor's browser for it to be able to distinguish between different visitors on the same network:
```
Cookie: CosUserId
Purpose: A unique identifier to distinguish between different visitors
Lifetime: Session
```
If you use CustomerOS and need to comply with GDPR, we recommend you do the following:
* Update your privacy statement to inform visitors about your usage of CustomerOS.
* Update your cookie notice to notify visitors about cookies set by CustomerOS.
GDPR requires you to inform visitors about what happens to their personal data. Hence, you need to add a note in your privacy statement that explains that you are gathering information and for what purpose. You'll also need to update your cookie notice to notify visitors about the cookie set by CustomerOS.
Here's an exemplary text snippet you can include:
"We use CustomerOS to measure the business usage of our website. This service shows us the company names and addresses based on the IP addresses of our visitors. For CustomerOS to distinguish between different visitors on our website, it sets a cookie named 'CosUserId' with a lifetime of the remainder of the user's session."
## Third-party Visitor Identification Integrations
CustomerOS opts to be fully compliant with the Data Protection Act and only
deanonymises companies. If you wish to deanonymise individuals using 3rd
parties it is your and your solution's responsibility to not identify European
website visitors to remain in compliance with this Act.
Reach out if you have an existing solution you would like to feed into CustomerOS.
# Workspace & Users
Source: https://docs.customeros.ai/workspaces-and-users
Learn how CustomerOS organizes your company into workspaces and how users are automatically added.
## Workspaces in CustomerOS
When the first person from your company signs up to CustomerOS, a **workspace** is automatically created.\
This workspace acts as your company’s secure tenant — all of your data, integrations, and reports live inside it.
The workspace is tied to your company’s **email domain**.\
For example:
* If `alex@example.com` is the first to sign up, a workspace for `example.com` is created.
* All colleagues with an `@example.com` email address can then join that same workspace automatically.
***
## Users in a Workspace
### Automatic Access
* Any teammate signing in with the same company domain is routed into the existing workspace.
* No manual invites or setup required.
### Roles & Permissions
* The first user becomes the **workspace owner** by default.
* Additional colleagues join as **members**.
* Owners can later promote members to admin roles or manage permissions in **Settings → Users**.
***
## Benefits of Domain-Based Workspaces
* **Seamless onboarding**: Your whole team can access CustomerOS without chasing invites.
* **Single source of truth**: All leads, reports, and dashboards live in one shared tenant.
* **Security**: Only verified users with your domain can access your workspace.
***
## Next Steps
* First to sign up? Let's get started by booking a call and adding the website first-party tracker.
* Teammate joining later? Just get them to log in with your company email and you’ll be added automatically.
* Need to invite external collaborators? Get in touch with us and we can help you via the support chat.