Search results
Jump to navigation
Jump to search
Page title matches
- Addressability Framework Working Group for User Experience '''Scope''': User Experience requirements and nominal design819 bytes (103 words) - 10:18, 12 January 2022
- #REDIRECT [[PAF User Experience]]33 bytes (4 words) - 09:59, 12 January 2022
- ...t supports.<ref>https://github.com/WICG/ua-client-hints#explainer-reducing-user-agent-granularity</ref> ...to inform the web server, site, and service about the capabilities of the user's agent. Here's an example from a Pixel 2 XL:5 KB (740 words) - 15:39, 14 June 2021
Page text matches
- ...ere the creative will render or the pipeline for the creative to reach the user's client, such as publisher ID, size, location, referring URL, etc.578 bytes (94 words) - 02:34, 12 January 2021
- Addressability Framework Working Group for User Experience '''Scope''': User Experience requirements and nominal design819 bytes (103 words) - 10:18, 12 January 2022
- ...sing (also called Behavioral Targeting (BT)) generates an attribute from a user's prior activity, such as the number of pages visited about a particular to317 bytes (43 words) - 15:14, 11 January 2021
- {{User}}8 bytes (1 word) - 13:56, 21 May 2021
- {{User}}8 bytes (1 word) - 18:13, 11 May 2021
- {{User}}8 bytes (1 word) - 11:52, 24 May 2021
- {{User}}8 bytes (1 word) - 15:48, 17 May 2021
- {{User}}8 bytes (1 word) - 14:17, 25 May 2021
- {{User}}8 bytes (1 word) - 13:38, 18 May 2021
- {{User}}8 bytes (1 word) - 15:28, 21 May 2021
- {{User}}8 bytes (1 word) - 14:10, 18 May 2021
- {{User}}8 bytes (1 word) - 17:03, 21 May 2021
- {{User}}8 bytes (1 word) - 14:59, 18 May 2021
- {{User}}8 bytes (1 word) - 14:14, 10 February 2022
- {{User}}8 bytes (1 word) - 21:09, 18 May 2021
- {{User}}8 bytes (1 word) - 11:44, 21 May 2021
- {{User}}8 bytes (1 word) - 17:14, 24 February 2021
- {{User}}8 bytes (1 word) - 13:16, 21 May 2021
- {{User}}8 bytes (1 word) - 17:46, 24 February 2021
- {{User}}8 bytes (1 word) - 13:27, 21 May 2021
- {{User}}8 bytes (1 word) - 08:10, 1 March 2021
- {{User}}8 bytes (1 word) - 13:41, 21 May 2021
- {{User}}8 bytes (1 word) - 20:59, 9 June 2021
- ...gives some amount of credit to each of the prior events associated that a user's subsequent conversion.691 bytes (104 words) - 23:49, 23 January 2021
- #REDIRECT [[PAF User Experience]]33 bytes (4 words) - 09:59, 12 January 2022
- '''Scope''': User Identifiers and Policy * [[PAF User Experience]]708 bytes (90 words) - 01:11, 3 February 2022
- Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.1 KB (133 words) - 15:11, 18 October 2021
- '''Description''': Document architecture for data rights management and user preferences that enables seamless workflows and integrations with client we * [[PAF User Experience]]890 bytes (112 words) - 10:15, 12 January 2022
- ...to buyers and sellers determining which creative will be shown to a given user's client in a particular placement in real-time, often determined via an au537 bytes (86 words) - 15:19, 11 January 2021
- ...in the [[Parakeet]] proposal, a "representation" is an encoded vector of a user's interaction with previous contexts.<ref>https://github.com/microsoft/priv769 bytes (93 words) - 21:59, 26 May 2021
- '''Scope''': Technical, UX and Contractual framework to generate User Identifiers, update preferences and policies associated with their responsi * [[PAF User Experience]]1,016 bytes (134 words) - 10:18, 12 January 2022
- ...s collected and owned by a separate organization than the one with which a user directly interacts.167 bytes (26 words) - 15:07, 11 January 2021
- ...eb client presents warnings associated with organization's request for the user to sign-in. # Mediation. Consent prompts are bundled with the user's initial action to request to sign-in, such as always declaring their offl4 KB (584 words) - 00:00, 18 October 2021
- ...t supports.<ref>https://github.com/WICG/ua-client-hints#explainer-reducing-user-agent-granularity</ref> ...to inform the web server, site, and service about the capabilities of the user's agent. Here's an example from a Pixel 2 XL:5 KB (740 words) - 15:39, 14 June 2021
- ...cally optimizing the creative]]. The ad server may also track delivery and user engagement metrics associated with the creative (e.g., impressions, clicks,949 bytes (148 words) - 18:34, 24 June 2021
- ** Allowing 3P cookies to store user's favorite location ** Allowing 3P cookies to store user's pre-authorized customer ID during account signup3 KB (479 words) - 21:53, 25 June 2021
- Adroll's Mechanism for User Reports with Regulated [[Privacy Budget|Epsilon]] (Murre) is designed to en ...acy|Differential Privacy]] is a framework for understanding and protecting user privacy.1 KB (215 words) - 19:47, 13 February 2022
- ...e template based on rule sets that take as inputs publisher data feeds and user attributes, or algorithms that learn what content correlates to particular294 bytes (41 words) - 15:01, 11 January 2021
- ...t a limit on this information will be provided to an organization for each user session. Once the Google-specific limit on access to this information has b * Detailed user agent strings including operating system and browser minor version;2 KB (330 words) - 14:01, 19 February 2022
- SharedID stores a pseudonymous user identifier in first-party cookie storage via Prebid's UserID Module framewo ...g to ensure a consistent cross-site identifier, but now relies on a random user ID per domain.1 KB (168 words) - 18:31, 25 June 2021
- * Granting unpartitioned storage access without impairing user experience via a permission prompt ...e will only have network access beyond the web client, when initiated by a user (e.g., a click).3 KB (501 words) - 16:26, 19 July 2021
- ...lled property or data element) is a piece of information associated with a user ID (e.g., gender=male, interest=sports, purchase=car) often with timestamps ...(e.g., view, interaction, registration, purchase) or information about the user (e.g., gender=male).5 KB (784 words) - 17:45, 20 June 2021
- '''Scope''': User Identification and Identifiers435 bytes (52 words) - 14:17, 11 January 2021
- ...esigned to inform the browser of whether a site is currently authorizing a user to access registration-only services, otherwise known as the login "state". Apple's proposal would "Require websites to take the user through a login flow according to rules that the browser can check. This wo3 KB (469 words) - 23:49, 17 October 2021
- ...marketers would be more inclined to match more content associated with the user-provided hint. ...ith “click jacking,” or automating the feedback rather than ensuring it is user provided. To mitigate this risk, the authors propose visual feedback when i6 KB (931 words) - 13:54, 17 October 2021
- ...ables marketers to engage people with interest attributes, with additional user-level controls over which attributes will be available to marketers.<ref>ht ...ed to improve the matching of content. These attributes are visible to the user, who can enable which organizations may have access to their profile and to8 KB (1,172 words) - 13:49, 17 October 2021
- ...o that product, the site would now be showing less relevant content to the user that would negatively impact their experience. Larger sites that both sell ...ontext, geography or even registration data. To more directly address such user concerns, these proposals could be improved by storing sets of “paused”4 KB (679 words) - 13:43, 17 October 2021
- ...ata collected, processed and owned by a separate company. Examples include user activities collected on a brand's website to be used by that brand. If that406 bytes (65 words) - 15:08, 11 January 2021
- ...r any participant in the system to map a specific ad request to a specific user.” <ref>https://github.com/WICG/privacy-preserving-ads/blob/main/MACAW.md< ...quired by [[Fledge]]. Unlike Fledge, Macaw allows real-time computation of user and current context signals to influence bidding logic. The improved accura3 KB (496 words) - 13:17, 17 October 2021
- The goal of Google's Trust Tokens is to "show that a user is who they say they are."<ref>https://web.dev/trust-tokens</ref> ...aud detection services, but instead the only means of validating whether a user is a human requires the web client to remember this individual has previous3 KB (494 words) - 00:28, 4 February 2022