> ## 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.

# Implementation

> A high-level guide to deploying Permutive across your properties

This page provides an overview of the typical Permutive implementation journey. Your [Technical Services](mailto:technical-services@permutive.com) team will guide you through each phase, but this overview helps you understand what's involved and where to find detailed documentation.

<Info>
  We strongly recommend deploying changes to a staging environment first, so your [Technical Services](mailto:technical-services@permutive.com) team can verify the implementation before production rollout.
</Info>

## Prerequisites

Before beginning implementation, ensure you have:

* **Workspace credentials**: Your Organization ID, Workspace ID, and API keys (provided by your Customer Success Manager)
* **Dashboard access**: Login credentials for the [Permutive Dashboard](https://dash.permutive.com)
* **Technical resources**: Development access to deploy code to your web, mobile, or CTV properties

## Implementation phases

A typical Permutive implementation follows these phases:

```mermaid theme={"dark"}
flowchart LR
    A[Planning] --> B[SDK Deployment]
    B --> C[Cohort Creation]
    C --> D[Activation]
```

### 1. Planning

Before any code is deployed, your [Technical Services](mailto:technical-services@permutive.com) team will work with you to define what data you'll capture and which identifiers you'll collect. This planning phase shapes the deployment itself.

#### Event schema design

Your [Technical Services](mailto:technical-services@permutive.com) team will help you define the event schemas that capture your user behavior and contextual data. This includes:

**Standard events (Collectors):**

* **Pageview**: Page metadata such as article category, author, publish date, content type
* **Engagement**: Time on page, scroll depth, and interaction signals
* **Video**: Play, pause, complete, and quartile events for video content

**Custom events:**
Business-specific events such as subscription actions, search queries, or e-commerce activity. Your [Technical Services](mailto:technical-services@permutive.com) team will design schemas that capture the properties needed for your targeting use cases.

<Card title="Events Concept" icon="bars-staggered" href="/concepts/events">
  Learn more about events and how they power segmentation
</Card>

#### Identity planning

Determine which identifiers you'll collect and how they'll be passed to Permutive:

* **First-party IDs**: Authenticated user IDs from your login system—requires calling `permutive.identify()` in your deployment
* **Third-party IDs**: Partner identifiers like UID2, ID5, or RampID—may require additional SDK configuration or server-side integration
* **Device IDs**: IDFA (iOS) or AAID (Android)—requires deploying the appropriate provider module in mobile SDKs
* **Household IDs**: For CTV environments—typically imported via Connectivity from your data warehouse

Identifiers are configured in the Dashboard under **Settings → Identity**, and your [Technical Services](mailto:technical-services@permutive.com) team will advise on the technical requirements for each.

<Card title="Identity Concept" icon="passport" href="/concepts/identity">
  Learn more about identifiers and identity management
</Card>

### 2. SDK deployment

With your event schemas and identity requirements defined, deploy the Permutive SDK to your properties. The SDK runs on-device to capture events, process cohorts in real-time, and activate audiences.

<CardGroup cols={2}>
  <Card title="Web (JavaScript)" icon="browser" href="/sdks/web/javascript-sdk">
    For desktop and mobile web properties
  </Card>

  <Card title="iOS" icon="apple" href="/sdks/mobile/ios/overview">
    For native iOS applications
  </Card>

  <Card title="Android" icon="android" href="/sdks/mobile/android/overview">
    For native Android applications
  </Card>

  <Card title="CTV" icon="tv" href="/sdks/ctv/tvos">
    For connected TV applications
  </Card>
</CardGroup>

**Deployment includes:**

* Adding the SDK snippet or package to your codebase
* Configuring your Workspace ID and API key
* Implementing event tracking according to your agreed schemas
* Adding `permutive.identify()` calls for any first-party or third-party identifiers
* Configuring consent handling for your regions (see below)
* Placing the SDK early in your page/app lifecycle to ensure cohorts are available for ad requests

**Verification:**
Use the [Permutive Chrome Extension](https://chrome.google.com/webstore/detail/permutive) (web) or SDK logging (mobile/CTV) to verify events fire correctly with expected properties. Your [Technical Services](mailto:technical-services@permutive.com) team will perform a full verification before signing off on production deployment.

<Note>
  **API Direct deployment**: In some environments where SDK deployment isn't possible (e.g., certain CTV or server-side contexts), Permutive can be integrated directly via API. If this applies to your use case, your [Technical Services](mailto:technical-services@permutive.com) team will guide you through an API Direct deployment approach.
</Note>

### 3. Cohort creation

Once your SDK is deployed and data is flowing, build audiences using the cohort builder in the Permutive Dashboard. Cohorts can be based on:

* **Behavioral rules**: Users who performed specific actions (e.g., "read 3+ sports articles in 7 days")
* **Contextual signals**: Page content classifications, keywords, or affinity scores
* **Imported data**: Audiences from your data warehouse or third-party providers

Your Customer Success Manager can help you define cohorts that align with your commercial strategy.

<CardGroup cols={2}>
  <Card title="Cohorts Concept" icon="users" href="/concepts/cohorts">
    Understand cohort types and how they work
  </Card>

  <Card title="Creating Custom Cohorts" icon="plus" href="/guides/signals/cohorts/custom/creating-custom-cohorts">
    Step-by-step guide to building cohorts
  </Card>
</CardGroup>

### 4. Activation

Connect Permutive to your ad servers, SSPs, and other platforms to activate cohorts for targeting.

**Common activation destinations:**

| Type            | Platforms                                        |
| --------------- | ------------------------------------------------ |
| Ad Servers      | Google Ad Manager, FreeWheel, Xandr, Equativ     |
| SSPs            | Prebid, Magnite, PubMatic, Index Exchange, OpenX |
| DSPs            | The Trade Desk, DV360                            |
| Data Warehouses | BigQuery, Snowflake, AWS S3                      |

Activations are configured in the Dashboard under **Settings → Integrations**, and your [Technical Services](mailto:technical-services@permutive.com) team will help ensure cohorts flow correctly to each platform.

<Card title="Integrations" icon="plug" href="/integrations/overview">
  Browse all available integrations
</Card>

## Handling consent

Permutive supports flexible consent handling to comply with GDPR, CCPA, and other privacy regulations. Consent configuration is part of your SDK deployment.

**Typical configurations:**

| Region              | Configuration                                                                              |
| ------------------- | ------------------------------------------------------------------------------------------ |
| GDPR (opt-in)       | Set `consentRequired: true`; call `permutive.consent()` when CMP grants consent            |
| CCPA (opt-out)      | Set `consentRequired: false`; call `permutive.consent({ opt_in: false })` if user opts out |
| No consent required | Set `consentRequired: false`                                                               |

<Card title="Consent & Privacy" icon="shield" href="/governance/consent">
  Learn more about consent handling
</Card>

## Getting help

Throughout your implementation, you have access to:

* **Customer Success Manager**: For strategy, cohort planning, and commercial alignment
* **[Technical Services](mailto:technical-services@permutive.com)**: For technical setup and configuration
* **[Support](mailto:support@permutive.com)**: For troubleshooting and help

<CardGroup cols={2}>
  <Card title="API Reference" icon="code" href="/api">
    Technical API documentation
  </Card>
</CardGroup>