> ## Documentation Index
> Fetch the complete documentation index at: https://docs.permutive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Audience Insights

> Understand your audience composition, behavior, and content preferences

export const NoBadge = () => {
  return <span style={{
    display: 'inline-block',
    padding: '0.125rem 0.5rem',
    borderRadius: '0.25rem',
    fontSize: '0.625rem',
    background: '#F7D0E2',
    color: '#1A1A1A',
    fontWeight: '500'
  }}>
      No
    </span>;
};

export const YesBadge = () => {
  return <span style={{
    display: 'inline-block',
    padding: '0.125rem 0.5rem',
    borderRadius: '0.25rem',
    fontSize: '0.625rem',
    background: '#C7E8F9',
    color: '#1A1A1A',
    fontWeight: '500'
  }}>
      Yes
    </span>;
};

<CardGroup cols={3}>
  <Card title="Guides" icon="book-open" href="#guides" />

  <Card title="Issues" icon="triangle-exclamation" href="#troubleshooting" />

  <Card title="FAQ" icon="circle-question" href="#faq" />
</CardGroup>

## Overview

**Audience Insights** provides a holistic overview of the users visiting your site and their on-site behaviors. By analyzing cohort composition, engagement patterns, and content preferences, publishers can build compelling data narratives for advertisers, optimize targeting strategies, and demonstrate the value of their first-party audiences.

Audience Insights enables you to filter by cohorts or tags and explore five key dimensions: Engagement, Technographics, Index & Overlap, Third-Party data, and Content Read. Each dimension provides unique insights into who your audiences are and how they interact with your content.

## Why Use Audience Insights?

**Understand audience behavior at scale** — Engagement metrics reveal how users in your cohorts interact with your site, from session length to articles viewed, helping you quantify audience value for advertisers.

**Create compelling RFP responses** — Transform raw data into rich narratives that demonstrate audience quality, engagement depth, and content affinity to win more direct-sold campaigns.

**Discover audience relationships** — Index and Overlap analysis shows how your cohorts compare to each other, revealing hidden connections and opportunities for audience extension.

## Concepts

### Definitions

* **Base Cohort**: The baseline audience used for comparison in Index calculations. Typically set to "Everyone" to compare a specific cohort against all site users. Only one base cohort can be selected at a time.
* **Comparison Cohorts**: The cohorts you want to measure against the base cohort in Index & Overlap reports. You can select multiple comparison cohorts or tag groups.
* **Index**: A score indicating how much more or less likely users in a cohort are to exhibit a behavior compared to the base cohort. An index of 100 is the baseline (equal likelihood), above 100 indicates higher likelihood (e.g., 125 = 25% more likely or 1.25x), and below 100 indicates lower likelihood.
* **Overlap**: The percentage of users in your selected cohort who also belong to a comparison cohort. For example, a 53% overlap with "Pet Owners" means 53% of users in your cohort are also in the Pet Owners cohort.
* **Uniques**: The number of unique users who have been active on-site during the filtered date range and are members of the selected cohort.
* **Sessions**: The number of sessions completed by users in the selected cohorts during the filtered timeframe. A session ends after 30 minutes of inactivity.
* **Pageviews**: The number of pageview events fired by users in the selected cohorts during the filtered timeframe.
* **Minimum Uniques**: A filter threshold that excludes comparison cohorts below a specified size from Index & Overlap reports, ensuring statistical relevance.

## Workflows

### Filtering Audience Insights

Publishers configure Audience Insights by selecting cohorts or tags to analyze, then applying secondary filters such as date range, domain, device type, country, and platform. These filters allow precise segmentation of audience data for specific analysis needs.

### Analyzing Engagement Metrics

The Engagement tab displays key metrics about audience activity including unique users, sessions, pageviews, average time spent, average session length, and articles viewed per session. This data supports RFP responses by quantifying how engaged a cohort is with your content.

### Comparing Cohorts with Index & Overlap

Index & Overlap analysis reveals relationships between cohorts by showing both how likely users are to belong to multiple cohorts (index) and what percentage actually overlap. This helps identify audience extension opportunities and validate targeting assumptions.

### Exploring Content Preferences

Content Read insights surface the custom properties from your Pageview events that resonate most with specific cohorts—from most-read authors to highest-indexed article categories. This enables content-based targeting recommendations for advertisers.

## Guides

### Configuring Audience Insights Filters

All Audience Insights reports share a common filtering system that allows you to focus on specific audiences and contexts.

<Steps>
  <Step title="Select your audience">
    Click *Edit* next to *Audience* to choose which cohorts to analyze. You can select:

    * A single cohort
    * Multiple cohorts
    * A tag group (all cohorts with a specific tag)
  </Step>

  <Step title="Configure secondary filters">
    Click *Edit* next to *Filter* to apply additional parameters:

    * **Date Range**: Last day, last 7 days, last 30 days, or custom range (up to 18 months lookback)
    * **Domain**: Filter by specific domains if Permutive is deployed across multiple sites
    * **Device Type**: Desktop, Mobile, or Tablet
    * **Countries**: Filter by geographic location
    * **Platform**: Web, AMP, FIA, iOS, or Android
  </Step>

  <Step title="Apply filters">
    Click *Apply* to update the reports with your selected filters.
  </Step>
</Steps>

<Tip>
  If you encounter timeout errors, reduce the complexity of your report by removing some filters or narrowing the date range. Complex queries with multiple cohorts and filters may take longer to process.
</Tip>

### Viewing Engagement Insights

Engagement insights provide data about the level of on-site activity for your selected cohorts.

<Steps>
  <Step title="Navigate to Engagement">
    In Audience Insights, select the *Engagement* tab.
  </Step>

  <Step title="Review key metrics">
    Analyze the following data points:

    * **Uniques**: Number of unique users active in the cohort during the date range
    * **Sessions**: Total sessions completed by cohort members
    * **Pageviews**: Total pageview events from cohort members
    * **Average Time Spent (Mins)**: Average browsing time per user
    * **Average Session Length**: Average duration of each session
    * **Articles Viewed Per Session**: Average pageviews per session
  </Step>

  <Step title="Download data">
    Click the download icon in the upper right corner of any chart to export as CSV or PNG.
  </Step>
</Steps>

<Warning>
  Some platforms have data collection limitations that affect Engagement metrics. See the [Environment Compatibility](#environment-compatibility) section for details on which metrics are available per platform.
</Warning>

### Using Index & Overlap

Index & Overlap helps you understand how your audiences relate to each other.

<Steps>
  <Step title="Navigate to Index & Overlap">
    In Audience Insights, select the *Index & Overlap* tab.
  </Step>

  <Step title="Set the base cohort">
    Select a base cohort from the dropdown. This is the baseline for index calculations.

    <Tip>
      It is common practice to select *Everyone* to see how likely cohort members are to belong to other cohorts compared to all site users. However, if you have a lot of "passerby" traffic (single pageview visitors) it can also be useful to set this to a group of users that have done at least 2 or 3 pageviews across all of your properties to view a more normalized set of indices.
    </Tip>
  </Step>

  <Step title="Select comparison cohorts">
    Choose the cohorts or tag groups you want to compare against. You can also click *Select All Cohorts* to compare against your entire cohort library.

    <Warning>
      Selecting too many / all cohorts for comparison can cause slow loading times or timeout issues due to the significant processing required for these reports. Try creating a tag for cohorts that are valuable for insights reporting in order to quickly filter this view to relevant comparison cohorts.
    </Warning>
  </Step>

  <Step title="Set minimum uniques (optional)">
    Apply a minimum uniques threshold to filter out small cohorts that may not provide statistically meaningful results.
  </Step>

  <Step title="Interpret the results">
    For each comparison cohort, review:

    * **Overlap %**: What percentage of your selected cohort also belongs to the comparison cohort
    * **Index**: How much more or less likely users are to be in the comparison cohort vs. the base
  </Step>
</Steps>

<Expandable title="Understanding Index Scores">
  Index scores use 100 as the baseline:

  | Index Score | Interpretation          | Example                                     |
  | :---------- | :---------------------- | :------------------------------------------ |
  | 100         | Equal likelihood        | Users are just as likely as the base cohort |
  | 125         | 25% more likely (1.25x) | Users are somewhat more likely              |
  | 200         | 100% more likely (2x)   | Users are twice as likely                   |
  | 75          | 25% less likely (0.75x) | Users are somewhat less likely              |

  **Example**: If your "Foodies" cohort (primary cohort) shows an index of 145 against "New York Residents" (comparison cohort) with the base set to "Everyone," users in the Foodies cohort are 45% (or 1.45x) more likely to also be in the New York Residents cohort than the average site user.
</Expandable>

### Viewing Technographics

Technographics provide insights into the devices, platforms, browsers, and locations of your audience.

<Steps>
  <Step title="Navigate to Technographics">
    In Audience Insights, select the *Technographics* tab.
  </Step>

  <Step title="Review breakdowns">
    Analyze audience composition across:

    * **Device Type**: Desktop, Mobile, Tablet distribution
    * **Platform**: Web, AMP, FIA, iOS, Android distribution
    * **Browser**: Chrome, Safari, Firefox, Edge, etc.
    * **Country**: Geographic distribution
    * **Province/City**: Regional breakdowns (where available)
  </Step>

  <Step title="Export visualizations">
    Download pie charts as CSV data or PNG images for presentations.
  </Step>
</Steps>

### Viewing Third-Party Insights (Beta)

<Note>
  Third-Party Insights is currently in **Beta**. Data is provided by Eyeota and shows how your cohorts index against third-party audience segments.
</Note>

<Steps>
  <Step title="Navigate to Third-Party">
    In Audience Insights, select the *Third-Party* tab.
  </Step>

  <Step title="Select a data category">
    Choose from available categories:

    * **Demographics**: Age, gender, household composition
    * **B2B**: Industry, company size, job function
    * **Consumer Intent**: Purchase intent signals
    * **Automobile Intent**: Vehicle purchase interests
    * **Travel Intent**: Travel and destination interests
  </Step>

  <Step title="Set the base cohort">
    Select the base cohort for index comparison (typically "Everyone").
  </Step>

  <Step title="Interpret results">
    Review how your cohort indexes against Eyeota's third-party segments. For example, an index of 104 for "Female" means users in your cohort are 4% more likely to be female than the average user.
  </Step>
</Steps>

### Viewing Content Read Insights

Content Read surfaces the custom properties from your Pageview events that are most associated with your selected cohorts.

<Steps>
  <Step title="Navigate to Content Read">
    In Audience Insights, select the *Content Read* tab.
  </Step>

  <Step title="Review indexed properties">
    The dashboard displays your custom Pageview properties (e.g., article.author, article.category, article.keywords) ranked by how strongly they index for your selected cohort.
  </Step>

  <Step title="Identify content patterns">
    Use the data to understand what content types, authors, sections, or topics resonate most with specific audiences.
  </Step>
</Steps>

<Expandable title="Why Some Values Show as Null">
  Content Read uses **quantile limits** to keep only the most popular items and filter out the long tail. This optimization improves performance and reduces storage costs.

  For example, with a 0.5 (50%) quantile limit on article titles, only the top 50% most-viewed titles are retained. Less popular content may appear as null values.

  If you're seeing unexpected null values, contact your Customer Success Manager to review your quantile limit configuration.
</Expandable>

### Viewing Hourly/Daily Activity

<Warning>
  **Deprecation Notice**: The Hourly/Daily Activity feature will be removed from the platform effective **January 19, 2026** and may already be ineffective in some workspaces. Plan to transition any workflows that depend on this feature.
</Warning>

Hourly/Daily Activity shows when your audiences are most likely to be online, enabling optimized ad scheduling.

<Steps>
  <Step title="Navigate to Hourly/Daily Activity">
    In Audience Insights, select the *Hourly/Daily Activity* tab (if available).
  </Step>

  <Step title="Configure filters">
    Note that the date range filter does not apply to this tab. Data is always aggregated from the last week. Hover over the information icon to see the exact date range.
  </Step>

  <Step title="Set the base cohort">
    Select a base cohort to compare activity patterns against.
  </Step>

  <Step title="Choose a breakdown">
    Select how to segment the data:

    * **All**: Entire cohort across all platforms and devices
    * **Device**: Breakdown by Desktop, Mobile, Tablet
    * **Platform**: Breakdown by AMP, Android, FIA, iOS, Web
  </Step>

  <Step title="Analyze activity patterns">
    Review the two graphs:

    * **Activity: Time of Day**: 24-hour activity pattern showing when users are most likely to be online
    * **Activity: Day of Week**: 7-day pattern showing which days have highest engagement
  </Step>
</Steps>

<Note>
  All times in Hourly/Daily Activity reports are displayed in **UTC**.
</Note>

### Adding Domains to Filters

If you have Permutive deployed across multiple domains, you can add them to enable domain-specific filtering.

<Steps>
  <Step title="Navigate to Settings">
    Go to *Settings* in the Permutive Dashboard.
  </Step>

  <Step title="Open Project settings">
    Click on the *Project* tab.
  </Step>

  <Step title="Edit domains">
    Under *Domains*, click *Edit*.
  </Step>

  <Step title="Add a domain">
    Enter the domain in its cleanest form (e.g., `support.permutive.com` rather than `https://support.permutive.com`) and click *+ Add*.
  </Step>

  <Step title="Save changes">
    Click *Save* to apply the changes.
  </Step>
</Steps>

<Note>
  Permutive will only start collecting data for a domain from when it was added to the Domains list. Historical data is not retroactively associated with newly added domains.
</Note>

### Exporting Audience Insights Reports

Export your insights as images, spreadsheets, or PDF reports for presentations and stakeholder sharing.

<Steps>
  <Step title="Configure your filters">
    Set all desired filters before exporting, as they cannot be changed during the export process.
  </Step>

  <Step title="Start the export">
    Click the green *Export Report* button in the top right corner of the Insights page.
  </Step>

  <Step title="Wait for charts to load">
    A loading indicator shows progress. Depending on filter complexity, this may take some time.

    If some charts fail to load, a *Retry* button will appear to reload them.
  </Step>

  <Step title="Preview and export">
    Review the export preview, then choose an export format:

    * **Export chart images**: Downloads all charts as individual images in a ZIP file
    * **Export to Excel**: Downloads raw data as an Excel spreadsheet with each chart as a separate sheet
    * **Print Report**: Opens print dialog where you can save as PDF
  </Step>
</Steps>

### Introduction to Enterprise Workspaces

Enterprise Workspaces organize publishers and alliances into a hierarchy, with each business unit having its own Permutive workspace. Understanding how data flows through this hierarchy is essential for interpreting Audience Insights correctly.

<Expandable title="What are Enterprise Workspaces?">
  Enterprise Workspaces allow large organizations to structure their Permutive deployment by business unit, region, or publication. A typical structure includes:

  * **Organization Workspace**: The top-level workspace representing the global organization
  * **Parent Workspaces**: Business units or regional divisions
  * **Child Workspaces**: Individual publications or properties

  This hierarchy enables centralized management while allowing each unit to maintain its own cohorts, activations, and insights.
</Expandable>

<Steps>
  <Step title="Understand data rollup">
    Data in Enterprise Workspaces flows **upward** through the hierarchy:

    * **Organization Workspace**: Has access to data from all workspaces
    * **Parent Workspace**: Can access data from its child workspaces
    * **Child Workspace**: Only has access to its own data

    When viewing Audience Insights, you see data aggregated from your current workspace and all its descendants.
  </Step>

  <Step title="Understand cohort propagation">
    Cohorts flow **downward** through the hierarchy:

    * Cohorts created in a parent workspace are deployed to all child workspaces
    * Cohorts created in a child workspace are **not** visible in parent workspaces

    **Example**: A cohort created in the Organization workspace will be available in all Business Unit and Publication workspaces below it.
  </Step>

  <Step title="Check your workspace context">
    The Audience filter in Insights only shows cohorts available to your current workspace. This includes:

    * Cohorts created in your current workspace
    * Cohorts inherited from parent workspaces

    This ensures no data leakage between organizational units.
  </Step>

  <Step title="Interpret your Insights data">
    Remember that Insights data reflects your workspace's position in the hierarchy:

    * **At Organization level**: Data aggregated from all workspaces
    * **At Business Unit level**: Data from that unit and its publications
    * **At Publication level**: Data from that publication only

    Cohort sizes and metrics will vary based on which workspace you're viewing.
  </Step>
</Steps>

<Note>
  **Predicted Audience Size** (the historical estimate shown in the Cohort Builder) and **Live Audience Size** (the real-time count of users currently qualifying) always reflect the workspace you're currently viewing, even for cohorts inherited from parent workspaces. For more about these metrics, see [Custom Cohorts: Audience Size Definitions](/products/signals/cohorts/custom#whats-the-difference-between-predicted-audience-size-and-live-audience-size).
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Timeout error when loading reports">
    **Cause**: The query is too complex due to multiple filters, large date ranges, or many cohorts selected.

    **Solution**:

    * Reduce the number of cohorts or filters selected
    * Narrow the date range
    * Remove less critical secondary filters
    * If the issue persists, contact support
  </Accordion>

  <Accordion title="Domain not appearing in filter options">
    **Cause**: The domain hasn't been added to your project settings.

    **Solution**:

    * Navigate to *Settings > Project > Domains*
    * Add the domain and save
    * Note: Data collection begins from when the domain is added; historical data won't appear
  </Accordion>

  <Accordion title="Content Read showing null values">
    **Cause**: Quantile limits filter out less popular content to optimize performance.

    **Solution**:

    * This is expected behavior for long-tail content
    * Contact your Customer Success Manager if you need to adjust quantile thresholds for specific properties
  </Accordion>

  <Accordion title="Missing data for AMP or mobile platforms">
    **Cause**: Some platforms have SDK limitations that prevent certain metrics from being collected.

    **Solution**:

    * Review the [Environment Compatibility](#environment-compatibility) table to understand which metrics are available per platform
    * This is a platform limitation, not a configuration issue
  </Accordion>

  <Accordion title="Index & Overlap showing no comparison cohorts">
    **Cause**: The minimum uniques threshold is filtering out all comparison cohorts.

    **Solution**:

    * Lower or remove the minimum uniques filter
    * Ensure the selected comparison cohorts have sufficient user activity in the date range
  </Accordion>

  <Accordion title="Export loading bar not reaching 100%">
    **Cause**: Some charts failed to load due to query complexity or timeout.

    **Solution**:

    * Click the *Retry* button to attempt reloading failed charts
    * If retries fail, simplify your filters and try again
    * Charts that don't load won't appear in the export
  </Accordion>

  <Accordion title="Cohort not appearing in Audience filter (Enterprise Workspaces)">
    **Cause**: The cohort was created in a child workspace and you're viewing a parent workspace.

    **Solution**:

    * Cohorts only propagate downward in the hierarchy
    * To use a cohort across multiple workspaces, create it in a parent workspace
    * Navigate to the workspace where the cohort was created to access it
  </Accordion>
</AccordionGroup>

## Environment Compatibility

#### Core Product

Audience Insights data availability varies by platform due to SDK limitations:

| Metric                      | Web          | AMP          | FIA          | iOS          | Android      |
| :-------------------------- | :----------- | :----------- | :----------- | :----------- | :----------- |
| Uniques                     | <YesBadge /> | <YesBadge /> | <YesBadge /> | <YesBadge /> | <YesBadge /> |
| Sessions                    | <YesBadge /> | <NoBadge />  | <YesBadge /> | <YesBadge /> | <YesBadge /> |
| Pageviews                   | <YesBadge /> | <NoBadge />  | <YesBadge /> | <NoBadge />  | <NoBadge />  |
| Articles Viewed Per Session | <YesBadge /> | <NoBadge />  | <YesBadge /> | <YesBadge /> | <YesBadge /> |
| Average Session Length      | <YesBadge /> | <NoBadge />  | <YesBadge /> | <NoBadge />  | <NoBadge />  |

#### Platform-Specific Notes

| Platform | Support | Notes                                                                                             |
| :------- | :-----: | :------------------------------------------------------------------------------------------------ |
| Web      |    ✓    | Full support for all Audience Insights features                                                   |
| AMP      |    \~   | Limited support; Sessions, Pageviews, and Session Length not available                            |
| FIA      |    ✓    | Full support for all features                                                                     |
| iOS      |    \~   | Uniques, Sessions, and Articles Per Session available; Pageviews and Session Length not available |
| Android  |    \~   | Uniques, Sessions, and Articles Per Session available; Pageviews and Session Length not available |

## Dependencies

| Dependency           | Required | Description                                                                        |
| :------------------- | :------- | :--------------------------------------------------------------------------------- |
| Permutive SDK        | ✓        | Required for collecting user behavior data that powers all Audience Insights       |
| Cohorts              | ✓        | At least one cohort must exist to filter Audience Insights reports                 |
| Eyeota Integration   | \~       | Required only for Third-Party Insights (Beta). Contact your CSM to enable.         |
| Domain Configuration | \~       | Required only if filtering by domain. Domains must be added in Settings > Project. |

## Limits

#### Data Retention

| Feature               | Description                                    | Limit               |
| :-------------------- | :--------------------------------------------- | :------------------ |
| Lookback Window       | Maximum historical data available for analysis | 18 months           |
| Hourly/Daily Activity | Data aggregation period                        | Last 7 days (fixed) |

#### Performance Limits

| Metric           | Description                                 | Limit                       |
| :--------------- | :------------------------------------------ | :-------------------------- |
| Query Timeout    | Maximum time for report generation          | Varies by complexity        |
| Export Load Time | Time for charts to render in export preview | Varies by filter complexity |

#### Feature Limits

| Feature               | Description                           | Limit                |
| :-------------------- | :------------------------------------ | :------------------- |
| Base Cohort Selection | Number of base cohorts per report     | 1                    |
| Comparison Cohorts    | Number of cohorts for Index & Overlap | Varies by complexity |

## FAQ

<AccordionGroup>
  <Accordion title="What's the difference between Audience Insights and Campaign Insights?">
    **Audience Insights** analyze users based on cohort membership and on-site behavior, helping you understand who your audiences are and how they engage with content.

    **Campaign Insights** analyze users who have interacted with specific advertising campaigns (via SlotClicked and SlotViewable events), helping you measure and optimize campaign performance.
  </Accordion>

  <Accordion title="How do I interpret an index score?">
    Index scores use 100 as the baseline:

    * **100** = Equal likelihood to the base cohort
    * **Above 100** = More likely (e.g., 150 = 50% more likely, or 1.5x)
    * **Below 100** = Less likely (e.g., 75 = 25% less likely, or 0.75x)

    For example, an index of 125 means users are either 1.25x more likely or 25% more likely than the base cohort.
  </Accordion>

  <Accordion title="Why is some data missing for AMP and mobile platforms?">
    AMP and mobile SDKs have platform limitations that prevent certain metrics from being collected. For example, AMP doesn't support session tracking, so Sessions, Pageviews, and Session Length metrics are unavailable. This is a platform constraint, not a configuration issue.
  </Accordion>

  <Accordion title="What is a quantile limit in Content Read?">
    Quantile limits filter out less popular content to optimize performance. For example, a 0.5 (50%) limit on article titles keeps only the top 50% most-viewed titles. Content below the threshold appears as null values. This reduces storage costs and improves query speed while retaining the most meaningful data.
  </Accordion>

  <Accordion title="How far back can I analyze data?">
    Audience Insights supports an 18-month lookback window, starting from when you first deployed Permutive on your site. This extended history is possible because Permutive uses first-party cookies, and it enables seasonal campaign optimization and long-term trend analysis.
  </Accordion>

  <Accordion title="Can I export reports for client presentations?">
    Yes. Use the *Export Report* button to download:

    * **Chart images** (ZIP file of individual PNGs)
    * **Excel spreadsheet** (raw data with each chart as a sheet)
    * **PDF** (via Print dialog, save as PDF)

    Set all your filters before exporting, as they cannot be modified during the export process.
  </Accordion>

  <Accordion title="What happened to Hourly/Daily Activity?">
    Hourly/Daily Activity is being deprecated and will be removed from the platform on **January 19, 2026**. If you rely on this feature, plan to transition your workflows before that date.
  </Accordion>

  <Accordion title="How do Third-Party Insights work?">
    Third-Party Insights (currently in Beta) show how your cohorts index against third-party audience segments provided by Eyeota. Categories include Demographics, B2B, Consumer Intent, Automobile Intent, and Travel Intent. This helps enrich your first-party data with additional audience characteristics.
  </Accordion>

  <Accordion title="Why do I need to set a base cohort?">
    The base cohort establishes the baseline for index calculations. Setting it to "Everyone" compares your selected cohort against all site users, answering "how much more likely are these users to exhibit X behavior than the average user?" You can also set a specific cohort as the base for more targeted comparisons.
  </Accordion>

  <Accordion title="How do Enterprise Workspaces affect Audience Insights?">
    In Enterprise Workspaces, Insights data rolls up through the hierarchy:

    * **Organization level** sees aggregated data from all workspaces
    * **Parent workspaces** see data from their child workspaces
    * **Child workspaces** see only their own data

    The Audience filter shows only cohorts available to your workspace (those created locally or inherited from parent workspaces). Cohort sizes reflect data from your current workspace and its descendants.
  </Accordion>
</AccordionGroup>

## Changelog

### 2026

**January 2026**

* Hourly/Daily Activity feature will be removed from the platform

### 2023

**February 2023**

* Added Export Reports functionality for Audience, Campaign, and Revenue Insights
* Support for PDF, Excel, and image exports

### 2021

**July 2021**

* Updated Hourly/Daily Activity with improved filtering and breakdown options

### 2020

**June 2020**

* Added Third-Party Insights (Beta) with Eyeota integration
* Categories: Demographics, B2B, Consumer Intent, Automobile Intent, Travel Intent

**May 2020**

* Launched Audience Insights with Engagement, Technographics, Index & Overlap, and Content Read tabs

<Info>
  For detailed changelog information, visit our [Changelog](https://changelog.permutive.com/).
</Info>