Cohorts
Activations
Contextual
What are Cohorts?
A cohort is a privacy-safe representation of an audience.
Traditionally, user IDs like third-party cookies have been used to communicate information about audiences and activate (target) them. A publisher might communicate behavioral data for a user to an ad server by attaching the data to a cookie ID. The ad server uses the cookie ID to record information about the user—both information from the publisher and other data parties they work with—and the ad server can later target an ad for a request from that user based on the information it has attached to their cookie ID.
With cohorts, a code represents the group of users that fall into an audience. In the example above, when the publisher requests an ad from the ad server for the user, it includes the cohort code in the request, but not a user ID. The ad server can use the cohort code(s) to decision on the ad to respond with, but no other publisher or user data is leaked and a profile of the user cannot be built.
By removing user identifiers from the equation, users' privacy is protected, the publisher's data cannot be targeted off of their site/app, and publishers can provide reachability (scale) to the ecosystem since cohorts can be built & activated in environments like Apple Safari, Mozilla Firefox, and iOS where third-party cookies and other deterministic identifiers are prohibited.
Cohort Types
- Behavioral
- Classification Model
- Contextual
Based on user actions and event patterns tracked through the SDK.
Example: A user who reads 5+ sports articles becomes part of the "sports_enthusiast" cohort.
User reads article about tennis
↓
Track event: "Pageview" with properties
↓
Permutive evaluates: "User read 3+ sports articles in 7 days?"
↓
User enters cohort: "sports_enthusiast"What are Activations?
Activations are subsets of cohorts configured for specific ad platforms. Not all cohorts are activated for all platforms—activations allow you to control which cohorts are sent to which ad networks.
Why use Activations?
Why use Activations?
- Platform-specific targeting - Different ad platforms may need different cohorts
- Data governance - Control which platforms receive which user segments
- Performance optimization - Only send relevant cohorts to each platform
- Compliance - Manage consent and privacy requirements per platform
Available Activation Types
| Activation Type | Platform | Use Case |
|---|---|---|
dfp | Google Ad Manager | Standard behavioral cohort activations |
dfp_contextual | Google Ad Manager | Real-time contextual cohorts |
appnexus_adserver | Xandr/AppNexus | Standard behavioral cohort activations |
appnexus_adserver_contextual | Xandr/AppNexus | Real-time contextual cohorts |
freewheel | Freewheel | CTV/video ad targeting |
Cohorts vs. Activations
| Aspect | Cohorts | Activations |
|---|---|---|
| Definition | All segments a user belongs to | Cohorts configured for specific platforms |
| Scope | Entire Permutive system | Platform-specific |
| Purpose | User segmentation | Ad targeting |
| Configuration | Automatic based on events | Configured in dashboard |
cohorts and activations via activations.
Example:
Accessing Cohorts and Activations
- Get Cohorts
- Get Activations
- Reactive Updates
Async API
async/await) and are available in Swift only.cohorts(), activations(), and googleCustomTargeting(adTargetable:) - wait for cohorts and activations to settle (for any events still being processed) before returning the current values. If they don’t settle within a short timeout (defaults to 500ms), the methods fall back to the currently cached values.
This matters most for time-sensitive ad requests: after tracking the page a user just opened, you want the ad request’s targeting to reflect that page rather than the previous one. Awaiting googleCustomTargeting(adTargetable:) gives the new cohorts a brief window to settle, then builds targeting from the freshest values available.
Get cohorts, awaiting any pending events:
Use Cases
Personalization
Personalization
Feature Flags / A/B Testing
Feature Flags / A/B Testing
Dynamic Ad Targeting
Dynamic Ad Targeting
Analytics and Logging
Analytics and Logging
Contextual Cohorts
Contextual cohorts are generated in real-time based on content being viewed. They require SDK version 2.0.0+ and feature enablement by your CSM.Contextual Data Guide
tvOS Considerations
Troubleshooting
Empty cohorts
Empty cohorts
cohorts returns an empty set.Solutions:- Wait a few seconds after initialization
- Track some events to generate data
- Use TriggerProvider for reactive updates
- Enable debug logging to see sync status
- Verify cohorts are configured in your dashboard
Activations different from cohorts
Activations different from cohorts
Contextual cohorts not appearing
Contextual cohorts not appearing
dfp_contextual activations are empty.Solutions:- Verify feature is enabled with your CSM
- Update to SDK 2.0.0+
- Ensure you’re using PageTracker with valid URLs
- Verify the URL is publicly accessible
- Check debug logs for classification errors
Best Practices
- Do
- Don't
- Use
cohortsfor one-time checks - Use TriggerProvider for reactive updates
- Check activation keys exist before accessing
- Handle empty sets gracefully
- Log cohorts for debugging (in development only)
- Cache cohort checks that are expensive to re-evaluate