In this article
We will show you how to enable the Permutive Browser Extension.
Permutive's Chrome extension allows you to validate your Permutive deployment. You can check what data is being collected if there are any schema errors, what cohorts you belong to, and if all ad requests are targeted.
Tip: Click here to download the browser extension
After installing the Permutive extension, please follow these steps to get full access: 1. Right-click on the extension icon and select 'Options'
2. Enter your organization ID and click 'Save'.
Note: You can find your Organization ID in the Permutive dashboard under 'Settings > Workspace'
3. To enable the popup, click on the icon, which will be black if Permutive is detected and you are allowed.
The Permutive extension currently has 4 views:
All requests will show in this tab. If the row has a check next to it, it means the request was sent correctly. If the row has an “x”, it means the request has experienced an error. You can open the request to see the payload.
- You can also check our consent framework calls on the current page; if a user on a website has given consent and if it’s required or not.
- You can see all requests which have been collected on the current and previous pageview
- By clicking on the event name you can see all of the properties of the event
- If an event is rejected, you will see an error message and an “x” by the request
- The extension supports identity requests, this event is also expandable to show what aliases are passed to Permutive
Note: Generally there are 2 reasons why events can be rejected: The event is unknown or there might be schema rejections. The extension shows why an event has been rejected, and in the case of schema rejections, you'll see detailed error messages when inspecting the event properties.
- The Cohorts tab shows you all of the cohorts you currently fall into
- You’ll only see cohort codes, so you’ll need to look up the cohort names in the dashboard
This shows the GAM ad units. A star next to the row means it was targeted with real-time data (the SDK computed the cohorts before sending them to the ad unit. A check means the ad unit was targeted with cohorts located in local storage and was sent before the SDK was initialized. An “x” means the ad unit was not targeted with cohorts.
- If you're using Google Ad Manager, this tab will give you an overview of all ad requests on the current page
- You can see whether the ad request was targeted by Permutive or not
- The ‘i’ info icon is next to the cohorts parameter to quickly show where Permutive cohorts are in the ad request
- Click on an individual ad request to see more details, like targeting keys
- Hovering over the icon will show you some more details, e.g. if the request was initialized on the parent page or inside an iframe
Tip: A check indicates that the ad was targeted with Permutive cohorts from a previous page. A star indicates that the ad was targeted with real-time cohorts implemented on that page. A circled exclamation point indicates that the displayed ad was not targeted using Permutive cohorts. This new feature was added as a visibility function to inform about ads related to your cohorts.
Prebid is a solution for header bidding. This allows publishers to programmatically auction their ad inventory to multiple ad exchanges and networks at the same time.
- Check the PreBid configuration, defined bidders, and what type of cohorts are currently being sent. Supports custom cohorts and standard cohorts.
- Indicates if the default required modules are installed correctly
- All red X’s under “Cohorts Passed In Auctions” indicate it is installed incorrectly
- Custom configurations are indicated If all red exclamations under “PreBid Configuration Checks” are displayed and all green checks are shown under “Cohorts Passed in Auctions”
In the extension settings:Display PreBid Event Requests:
- Can turn on/off displaying PreBid events in the requests tab
Each event is also expandable
- We by default collect logs for SDK, but not user logging nor collecting PII.