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

# Setting Up Google PPS

> How to generate PPS mapping files and upload to Google Ad Manager

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

<Info>
  **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 `prmtvctx` key configured in GAM key-value targeting
</Info>

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

<Note>
  **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.
</Note>

## Steps

<Steps>
  <Step title="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.
  </Step>

  <Step title="Contact Technical Services">
    PPS mapping file generation is typically handled by [Technical Services](mailto:technical-services@permutive.com). Reach out to them to request PPS setup for your workspace.
  </Step>

  <Step title="Generate the PPS mapping file">
    [Technical Services](mailto:technical-services@permutive.com) 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.

    <Warning>
      **Sensitive categories are filtered**: Google automatically excludes certain sensitive categories from PPS (e.g., war/conflicts, medical health, religion, politics). The mapping tool filters these categories automatically.
    </Warning>
  </Step>

  <Step title="Upload the mapping file to Google Ad Manager">
    Once you receive the PPS mapping CSV file:

    1. Log into Google Ad Manager
    2. Navigate to *Admin > PPS Taxonomy*
    3. Upload the CSV mapping file
    4. Verify that the mapping is active
  </Step>

  <Step title="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.
  </Step>

  <Step title="Verify PPS is working">
    Test that PPS values are being passed correctly:

    * Use the Google Publisher Console to inspect ad requests
    * Verify that `prmtvctx` key-value pairs appear in the auction
    * Check that PPS taxonomy IDs are included in the bid request
  </Step>
</Steps>

## 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") |

<Tip>
  **Incremental updates**: If new Standard Contextual Cohorts are added to your workspace (e.g., when your classification provider adds new categories), you may need to regenerate and re-upload the PPS mapping file to ensure complete coverage.
</Tip>

## Measuring PPS Impact

After PPS is live, measure its impact on your revenue:

1. **Run PPS lift reports in GAM**: Compare PPS-tagged inventory against open AdX baseline
2. **Calculate eCPM delta**: Measure the incremental value of PPS-enriched impressions
3. **Analyze by category**: Identify which contextual categories drive the highest premiums

<Note>
  **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.
</Note>

## Troubleshooting

For troubleshooting PPS mapping issues such as mapping file generation failures or categories rejected by Google, see [Standard Contextual Cohorts — Troubleshooting](/products/signals/cohorts/standard-contextual#troubleshooting).

<AccordionGroup>
  <Accordion title="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
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Google Ad Manager Integration" icon="ad" href="/integrations/advertising/ad-servers/google-ad-manager">
    View full GAM integration documentation
  </Card>

  <Card title="Activating Standard Contextual Cohorts" icon="bullhorn" href="/guides/signals/cohorts/standard-contextual/activating-standard-contextual-cohorts">
    Learn more about cohort activation
  </Card>

  <Card title="Back to Standard Contextual Cohorts" icon="arrow-left" href="/products/signals/cohorts/standard-contextual">
    Return to product overview
  </Card>
</CardGroup>