# Privacy Triage: Apple - CPM Extension Health Pixels

Status: **DRAFT**

**Name:** Alex M  
**Email:** amartemyanov@duckduckgo.com  
**Objective:** O-E  
**PR:** [Add PR link]  
**Project:** https://app.asana.com/1/137249556945/project/1163321984198618/task/1216761517055116?focus=true

## Pixels

| Pixel                                                        | When it fires                                                              |
| ------------------------------------------------------------ | -------------------------------------------------------------------------- |
| `m_debug_web_extension_cpm_page_initialization_missing`      | A finished HTTP(S) page load does not receive the initial CPM status.      |
| `m_debug_web_extension_cpm_page_initialization_recovered`    | CPM works on the next page load or reload without reloading the extension. |
| `m_debug_web_extension_cpm_messaging_suspected_stuck`        | CPM fails repeatedly, including after a page reload and in another tab.    |
| `m_debug_web_extension_cpm_messaging_recovered_after_reload` | CPM starts working after the app reloads the extension.                    |
| `m_debug_web_extension_cpm_messaging_reload_failed`          | CPM still does not work after the app reloads the extension.               |

macOS uses the same names with the `m_mac_debug_` prefix. iOS uses the standard platform and form-factor suffixes.

The pixels send only the standard parameters: `appVersion`, plus `pixelSource` and `channel` on macOS.

## Privacy Questions

**Do the pixels use transparent names?**  
Yes.

**Do they share parameters with other pixels?**  
Yes. They use only existing standard parameters.

**Could the parameters link pixels to the same user?**  
No. No identifier is added.

**Do the pixels include a URL or search query?**  
No. They also do not include hostnames, page titles, tab IDs, document IDs, error text, or CPM rules.

**Are the pixels temporary?**  
The two page-initialization pixels are temporary diagnostics. The three stuck-state and reload-result pixels are permanent health monitoring.

**Why are the permanent pixels needed?**  
To measure how often CPM messaging becomes stuck and whether reloading the extension fixes it.

**Do any parameters or suffixes fall outside the standard criteria?**  
No.

**Do the pixels fire on sensitive user events?**  
No. They report only CPM extension health states.

**Can multiple occurrences be tied to the same user or a small group?**  
No. The pixels contain no correlation identifier or browsing data.

**Does this meet the self-service criteria?**  
Yes.