Demo Data from EDBT 2026 / reviewers in the wild / expert
Asmaa El Fraihi
dblp:380/8587
· DBLP profile ↗
3ranked-venue papers
2as first author
3since 2021 · last 2026
0009-0003-3065-9172ORCID · verified
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 2 · 1 first-author · 2 since 2021Databases, data management, data science and information retrieval · 1 · 1 first-author · 1 since 2021Applied, interdisciplinary, general and emerging computing · 1 · 1 first-author · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Network and information security
1 paper |
Web and mobile security · 50% Systems and software security · 50% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Web and mobile security › web security
online advertising security |
1.0 | 1 | 2026 | Is Contextual Advertising Safe? Analyzing Systemic Risks with Ads on YouTube · WWW 2026 |
Systems and software security
platform security |
1.0 | 1 | 2026 | Is Contextual Advertising Safe? Analyzing Systemic Risks with Ads on YouTube · WWW 2026 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2026 | Is Contextual Advertising Safe? Analyzing Systemic Risks with Ads on YouTube
Asmaa El Fraihi, Ines Abdelaziz, Oana Goga |
WWW | 1 |
| 2026 | A Year Under the DSA: Ad Transparency's Uneven LandscapeabstractThe Digital Services Act (DSA) has put platform accountability on center stage, requiring online platforms to provide greater transparency into how advertisements are targeted and delivered to users. Central to these obligations are two mechanisms: user-facing ad explanations, which inform individuals why they were shown a given ad, and public ad repositories, which are intended to enable independent auditing of advertising practices. This study provides the first multi-platform evaluation of these two mechanisms across Facebook, Instagram, YouTube and X. Using 48,511 user-facing “Why am I seeing this ad?” (WAIST) notices, and a systematic analysis of each platform’s public ad repository, we assess how well current implementations disclose the parameters and decision processes involved in targeting. To do so, we develop and apply an operational framework based on Articles 26 and 39 of the DSA—capturing the granularity, attribution of targeting and delivery choices, data source disclosures, and accuracy—and apply it across both user-facing notices and public ad repositories. Our findings show that transparency remains fragmented and inconsistent across platforms. User-facing explanations vary widely in precision and often omit key targeting information, while repositories provide incomplete, misattributed, and at times difficult-to-interpret targeting data. Moreover, discrepancies between explanations and repository entries undermine the reliability of both mechanisms. Overall, current transparency infrastructures fall short of the DSA’s expectations and highlight the need for clearer and more enforceable standards for advertising transparency moving forward. Abir Benzaamia, Asmaa El Fraihi, Ines Abdelaziz, Oana Goga |
Proc. Priv. Enhancing Technol. | 2 |
| 2024 | Client-side and Server-side Tracking on Meta: Effectiveness and AccuracyabstractGrowing concern over digital privacy has led to the widespread use of tracking restriction tools, such as ad blockers, Virtual Private Networks (VPN), and privacy-focused web browsers. All major browser vendors have also deprecated, or plan to deprecate, third-party cookies to reduce tracking. Despite these efforts, advertising companies continuously innovate to overcome these restrictions. Recently, advertising platforms, like Meta, have been promoting server-side tracking solutions to bypass traditional browser-based tracking restrictions. This paper explores how server-side tracking technologies can link website visitors with their user accounts on Meta products. The goal is to assess the effectiveness and accuracy of employing this technology, as well as the effect of tracking restrictions on online tracking. Our methodology involves a series of experiments where we integrate Meta's client-side tracker (the Meta Pixel) and server-side technology (the Conversions API) on different web pages. We then drive traffic to these pages and evaluate the success rate of linking website visitors to their profiles on Meta products. Our findings show that Meta's server-side technology can match between 34% and 51% of website visitors to user profiles on Meta products using basic information like the visitor's IP address, user agent, and location data. This is comparable to Pixel-based user matching in optimal conditions (i.e., in the absence of tracking restrictions), which links between 42% and 61% of user profiles. Nevertheless, we see a considerable difference in accuracy: while the Pixel-based tracking achieves 100% accuracy, less than 65% of the profiles matched by server-side tracking are accurate. Asmaa El Fraihi, Nardjes Amieur, Walter Rudametkin, Oana Goga |
Proc. Priv. Enhancing Technol. | 1 |