Skip to content

I2I: Permutive component for dynamic ad targeting #28095

@joshfg

Description

@joshfg

Summary

Permutive is a Data Management Platform (DMP) for publishers. We have a strong focus on privacy and first-party data: enabling publishers to use their data to power advertising and personalization in real-time, across every device, browser and environment, while respecting user privacy.

One of the essential capabilities we provide publishers is the ability to dynamically target their ads, based on a user's behaviour. We want to provide publishers with this capability in AMP, to the same standard as we do on standard Web pages. This proposal describes an AMP component that achieves this.

Motivation

Many publishers have asked us to integrate with their AMP pages and provide the same benefits in the AMP environment that we've been able to provide on their standard Web pages.

We believe we can offer publishers the same benefits they have seen on standard Web in AMP, by building a custom amp-permutive component. This component would allow publishers to target dynamically, without reliance on AMP RTC. We believe this approach has significant benefits for publishers and end-users:

  • By avoiding reliance on a third-party cookie, we can provide dynamic ad targeting across every browser, in every environment.
  • By avoiding AMP RTC calls, the publisher can avoid a blocking network request prior to the ad-request - leading to a better end-user experience and reduced competition for network resources on the user's device.
  • We believe long-term, there are significant privacy benefits from processing and decisioning on data on-device, rather than in the cloud. Behavioral data can be processed without ever leaving the user's device. In this world, only the result (e.g. a list of audience segment IDs) needs to leave the user's device. We believe this is the most privacy-compliant approach to audience targeting, which is good for publishers and end-users.

Design Document

Please find our proposal and the reasoning behind these design choices, here:

https://docs.google.com/document/d/1IHCjfuQCGcDmptJZFXWA9qNj8A0hdmsciDi7P7hBgjo

/cc @ampproject/wg-approvers
/cc @ampproject/wg-ads

Metadata

Metadata

Assignees

Labels

INTENT TO IMPLEMENTProposes implementation of a significant new feature. https://bit.ly/amp-contribute-code

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions