Overview
Set up Google Publisher Provided Signals (PPS) to pass Standard Contextual Cohorts into the Ad Exchange auction. This enables programmatic buyers to target your contextual inventory using standardized IAB categories.Prerequisites:
- Standard Contextual Cohorts enabled and activated to Google Ad Manager
- Google Ad Manager account with AdX enabled
- GAM integration configured in Permutive with appropriate API permissions
- The
prmtvctxkey configured in GAM key-value targeting
Understanding PPS
Publisher Provided Signals (PPS) is a Google Ad Manager feature that allows publishers to pass first-party contextual signals into the open auction. By mapping your Standard Contextual Cohorts to PPS, you enable buyers to bid more intelligently on contextually-enriched inventory.PPS uses standardized taxonomies: Google PPS requires standardized taxonomies to ensure consistent targeting across publishers. Standard Contextual Cohorts based on IAB Content Taxonomy 2.0 are specifically designed for this use case.
Steps
Ensure Standard Contextual Cohorts are activated to GAM
Before setting up PPS, verify that your Standard Contextual Cohorts are activated to Google Ad Manager in the Permutive Dashboard. Navigate to Contextual and confirm activation status.
Contact Technical Services
PPS mapping file generation is typically handled by Technical Services. Reach out to them to request PPS setup for your workspace.
Generate the PPS mapping file
Technical Services will generate a CSV mapping file that connects your Permutive Standard Contextual Cohort codes to the Google PPS taxonomy. This file maps the
prmtvctx key-value pairs to PPS categories.Upload the mapping file to Google Ad Manager
Once you receive the PPS mapping CSV file:
- Log into Google Ad Manager
- Navigate to Admin > PPS Taxonomy
- Upload the CSV mapping file
- Verify that the mapping is active
Enable PPS in your ad units
In Google Ad Manager, enable PPS on the relevant ad units or inventory where you want to pass contextual signals to buyers.
PPS Mapping File Structure
The PPS mapping CSV file contains:| Column | Description |
|---|---|
| Key | The GAM key-value targeting key (typically prmtvctx) |
| Value | Your Permutive cohort code (e.g., IAB1-1, IAB12-3) |
| PPS Taxonomy ID | The corresponding Google PPS taxonomy ID |
| Category Name | Human-readable category name (e.g., “Sports > Football”) |
Measuring PPS Impact
After PPS is live, measure its impact on your revenue:- Run PPS lift reports in GAM: Compare PPS-tagged inventory against open AdX baseline
- Calculate eCPM delta: Measure the incremental value of PPS-enriched impressions
- Analyze by category: Identify which contextual categories drive the highest premiums
Allow time for optimization: Buyers need time to adjust their bidding strategies to incorporate PPS signals. Allow at least 2-4 weeks before evaluating PPS impact.
Troubleshooting
For troubleshooting PPS mapping issues such as mapping file generation failures or categories rejected by Google, see Standard Contextual Cohorts — Troubleshooting.PPS values not appearing in bid requests
PPS values not appearing in bid requests
Cause: PPS may not be enabled on your ad units, or there’s a delay in the mapping being applied.Solution:
- Verify PPS is enabled on your ad units in Google Ad Manager
- Check that the mapping file was successfully uploaded
- Allow up to 24 hours for mapping changes to propagate
- Use Google Publisher Console to debug bid requests