Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aligning Privacy Dashboard EventMapping with iOS #3744

Merged

Conversation

mgurgel
Copy link
Collaborator

@mgurgel mgurgel commented Jan 16, 2025

Task/Issue URL: https://app.asana.com/0/1206594217596623/1209173355503842/f

Description:

Set ups Privacy Dashboard EventMapping as to align with iOS. Each mapped event fires a pixel when invoked by the Privacy Dashboard. See duckduckgo/BrowserServicesKit#1167

Note: not all events are currently used by the Dashboard. Some are being deprecated, which is why they might not be fired at all even though they still exist in the mapping.

Optional E2E tests:

  • Run PIR E2E tests
    Check this to run the Personal Information Removal end to end tests. If updating CCF, or any PIR related code, tick this.

Steps to test this PR:

  1. Invoke the breakage form in the two possible ways:
    Open the Privacy Dashboard and click on "Report a problem with this site"
    Open the app menu ••• and click on "Report Broken Site” (iOS)

  2. Confirm that the pixel m_report-broken-site_shown was fired

  3. Submit a report

  4. Confirm that the pixels epbf_macos_desktop and m_report-broken-site_sent were fired

Definition of Done:


Internal references:

Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

@mgurgel mgurgel changed the title Aligning EventMapping with iOS Aligning Privacy Dashboard EventMapping with iOS Jan 16, 2025
@duckduckgo duckduckgo deleted a comment from github-actions bot Jan 17, 2025
@mgurgel mgurgel force-pushed the mgurgel/improved-breakage-form branch from deff857 to 783a83f Compare January 17, 2025 14:25
@mgurgel mgurgel force-pushed the mgurgel/improved-breakage-form-pixel branch from 0481e40 to 676c605 Compare January 17, 2025 14:27
@mgurgel mgurgel self-assigned this Jan 17, 2025
@mgurgel mgurgel force-pushed the mgurgel/improved-breakage-form branch from 783a83f to 7ea9a8f Compare January 17, 2025 14:54
@mgurgel mgurgel force-pushed the mgurgel/improved-breakage-form-pixel branch from 1343302 to 9dd2078 Compare January 17, 2025 14:57
@mgurgel mgurgel marked this pull request as ready for review January 17, 2025 15:24
Copy link
Contributor

@afterxleep afterxleep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Working as described and pixels firing correctly.
Screenshot 2025-01-17 at 18 41 26

@mgurgel mgurgel merged commit ca102ac into mgurgel/improved-breakage-form Jan 17, 2025
27 checks passed
@mgurgel mgurgel deleted the mgurgel/improved-breakage-form-pixel branch January 17, 2025 17:54
mgurgel added a commit to duckduckgo/BrowserServicesKit that referenced this pull request Jan 17, 2025
**Required**:

Task/Issue URL:
https://app.asana.com/0/1206594217596623/1209173355503842/f
iOS PR: duckduckgo/iOS#3822
macOS PR: duckduckgo/macos-browser#3744
What kind of version bump will this require?: Minor

**Description**:

Implements Privacy Dashboard message `ReportBrokenSiteShown` which will
trigger a pixel on macOS and iOS

This PR contains a fix for
#1160 which is why
it is stacked on it. Please let me know if this is not the best way to
have this code reviewed.

**Steps to test this PR**:
1. Invoke the breakage form in the two possible ways:
Open the Privacy Dashboard and click on "Report a problem with this
site"
Open the app menu ••• and click on "Report Broken Site” (iOS)

2. Confirm that the pixel `m_report-broken-site_shown` was fired
3. Submit a report
4. Confirm that the pixels `epbf` (iOS) / `epbf_macos_desktop` (macOS)
and `m_report-broken-site_sent` were fired

<!--
Before submitting a PR, please ensure you have tested the combinations
you expect the reviewer to test, then delete configurations you *know*
do not need explicit testing.

Using a simulator where a physical device is unavailable is acceptable.
-->

**OS Testing**:

* [ ] iOS 14
* [ ] iOS 15
* [ ] iOS 16
* [ ] macOS 10.15
* [ ] macOS 11
* [ ] macOS 12

---
###### Internal references:
[Software Engineering
Expectations](https://app.asana.com/0/59792373528535/199064865822552)
[Technical Design
Template](https://app.asana.com/0/59792373528535/184709971311943)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants