Difference between revisions of "opportunities to reverse engineer adtech (Q3395)"
Jump to navigation
Jump to search
(Changed claim: has part (P6): Pubmatic cookie naming scheme (Q3339)) |
(Created claim: reference URL (P33): https://wiki.personaldata.io/wiki/Requesting_data) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Property / has part: AppNexus / qualifier | |||
| + | comment: AppNexus has an immediate data transparency portal, giving quite granular access to segments | ||
| Property / has part: AppNexus / qualifier | |||
| + | |||
| Property / reference URL | |||
| + | |||
| Property / reference URL: https://wiki.personaldata.io/wiki/Requesting_data / rank | |||
| + | Normal rank | ||
Latest revision as of 23:17, 13 January 2020
No description defined
| Language | Label | Description | Also known as |
|---|---|---|---|
| English |
opportunities to reverse engineer adtech
|
No description defined
|
Statements
TripleLift has a nice data access portal, giving quick access to many identifiers. Nice to use in a training situation, because the data there is easily accessible from the cookie jar (without name of companies).
0 references
PubMatic cookies have a predictable form, giving easy access to the cookie matching done by Pubmatic
part of the cookie naming scheme relies on the demand side platform indexing scheme described below
0 references
AppNexus has an immediate data transparency portal, giving quite granular access to segments
0 references