Skip to content

Commit 1f81c36

Browse files
authored
Fix a couple of markup issues (#4377)
* Fix ecommerce markup issue * Fix third-party markup typo
1 parent 362adbf commit 1f81c36

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

src/content/en/2025/ecommerce.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -321,10 +321,10 @@ Different tiers have different top platforms.
321321
<tr>
322322
<td class="numeric">5</td>
323323
<td></td>
324-
<td>Shopify/td>
325-
<td>WooCommerce/td>
326-
<td>1C-Bitrix/td>
327-
<td>Wix eCommerce/td>
324+
<td>Shopify</td>>
325+
<td>WooCommerce</td>>
326+
<td>1C-Bitrix</td>>
327+
<td>Wix eCommerce</td>>
328328
<td>PrestaShop</td>
329329
</tr>
330330
</tbody>
@@ -391,10 +391,10 @@ Different tiers have different top platforms.
391391
<tr>
392392
<td class="numeric">5</td>
393393
<td></td>
394-
<td>Shopify/td>
395-
<td>WooCommerce/td>
396-
<td>1C-Bitrix/td>
397-
<td>Wix eCommerce/td>
394+
<td>Shopify</td>>
395+
<td>WooCommerce</td>>
396+
<td>1C-Bitrix</td>>
397+
<td>Wix eCommerce</td>>
398398
<td>PrestaShop</td>
399399
</tr>
400400
</tbody>

src/content/en/2025/third-parties.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ The top 10 third-party domains are dominated by Google-owned services, including
165165

166166
## Consent propagation among third parties
167167

168-
In this section, we examine how different third parties transmit user consent across the web. <a hreflang="en" href="https://petsymposium.org/popets/2024/popets-2024-0120.pdf">Previous research</a> has shown that third parties often rely on industry-standard frameworks to communicate consent information. In our analysis, we focus primarily on the IAB's three consent standards: the <a hrefland="en" href="https://iabeurope.eu/transparency-consent-framework/">Transparency and Consent Framework (TCF)</a>, the <a hreflang="en" href="https://iabtechlab.com/standards/ccpa/">CCPA Framework</a>, and the <a hrefland="en" href="https://iabtechlab.com/gpp/">Global Privacy Protocol (GPP)</a>.
168+
In this section, we examine how different third parties transmit user consent across the web. <a hreflang="en" href="https://petsymposium.org/popets/2024/popets-2024-0120.pdf">Previous research</a> has shown that third parties often rely on industry-standard frameworks to communicate consent information. In our analysis, we focus primarily on the IAB's three consent standards: the <a hreflang="en" href="https://iabeurope.eu/transparency-consent-framework/">Transparency and Consent Framework (TCF)</a>, the <a hreflang="en" href="https://iabtechlab.com/standards/ccpa/">CCPA Framework</a>, and the <a hreflang="en" href="https://iabtechlab.com/gpp/">Global Privacy Protocol (GPP)</a>.
169169

170170
These frameworks define how consent information is encoded and shared between websites and third parties. We begin by identifying which consent standards are most prevalent among the third parties observed in our dataset. To determine which framework a third party uses, we rely on the presence of specific parameters in the request URLs. Details of the different standards are below:
171171

0 commit comments

Comments
 (0)