Fix missing product surface usage pixels for autocomplete and data clearing and update website loaded pixel usage

[catalinradoiu]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1211724162604201/task/1216240606378290?focus=true
Tech Design URL (if applicable):
API Proposals URL(s) (if applicable): None

Description

Two product surface usage pixels were under-reporting because they were wired to the wrong moment.

m_product_telemetry_surface_usage_autocomplete: It was fired from BrowserTabViewModel.autoCompleteSuggestionsGone(), on dismissal. Tapping a suggestion never reaches that method. It now fires on the transition into "suggestions on screen", inside onAutoCompleteResultReceived.

m_product_telemetry_surface_usage_data_clearing: It was fired from only one of the four clearing actions the fire dialog offers (regular-mode "clear all tabs and data"). Clearing a single tab, burning all Fire tabs, using the fire button inside a Duck.ai chat — cleared data without counting anything.

m_product_telemetry_surface_usage_website: Duck.ai loads in the browser WebView and isn't a DuckDuckGo query URL, but was counted as a website visit. Since Duck.ai already has its own surface pixel (m_product_telemetry_surface_usage_duck_ai), the same surface was being counted twice — once correctly, once as a website.

Steps to test this PR

Autocomplete surface pixel fires when suggestions are shown

• Install and open the browser, focus the omnibar and type a query until suggestions appear
• Verify m_product_telemetry_surface_usage_autocomplete (and ..._daily once per day) fires as soon as the list appears, without dismissing it
• Keep typing to refine the query while the list stays up; verify no extra impressions are counted
• Tap a suggestion to navigate; no new pixel should be sent for autocomplete
• Clear the omnibar, type again so the list re-appears; verify a new impression is counted

Data clearing surface pixel fires for every clearing action

• Fire button → Delete all tabs: verify m_product_telemetry_surface_usage_data_clearing fires (as before)
• Fire button → Delete a single tab: verify it fires
• In Fire mode, fire button → Delete all tabs/ single tab: verify it fires
• Fire button inside a Duck.ai chat → delete the chat: verify it fires
• Repeat any two actions on the same day: verify ..._data_clearing fires each time and ..._data_clearing_daily only once

Duck.ai loads no longer counted as website surface usage

• Open a Duck.ai chat (omnibar Duck.ai mode, or navigate to duck.ai) and send a prompt
• Verify m_product_telemetry_surface_usage_website / ..._website_daily do not fire for the chat load
• Load a regular website; verify ..._website still fires as before
• Run a search on DuckDuckGo; verify ..._serp still fires and ..._website does not

UI changes

Before	After
No UI changes	No UI changes

---

Note

Low Risk
Telemetry-only changes to pixel timing and coverage; no auth, data handling, or user-facing behavior changes beyond analytics accuracy.

Overview
Fixes under-reporting and double-counting in product surface usage telemetry by changing when pixels fire and which navigation paths count.

Autocomplete — m_product_telemetry_surface_usage_autocomplete no longer fires on dismissal (autoCompleteSuggestionsGone). It fires when suggestions first appear in onAutoCompleteResultReceived, using a transition check so repeated updates while the list stays visible do not add extra impressions.

Data clearing — m_product_telemetry_surface_usage_data_clearing is emitted from a shared fireDataClearingSurfacePixels() for every confirmed Fire Dialog action: clear all (regular and Fire mode), clear this tab, and delete Duck.ai chats. The daily pixel uses the standard Daily() pixel type instead of custom date/store logic (DateProvider / fireButtonStore removed from this path).

Website vs SERP vs Duck.ai — UriLoadedManager splits URI-loaded pixels from surface SERP/website pixels (sendUriLoadedPixels() vs sendSurfaceUsagePixels(isDuckDuckGoUrl)). On page finish, Duck.ai URLs skip website/SERP surface pixels because Duck.ai has its own surface pixel.

Pixel definition text in mobile_surfaces_telemetry.json5 is updated to match these semantics.

^{Reviewed by Cursor Bugbot for commit e77a342. Bugbot is set up for automated code reviews on this repo. Configure here.}

[catalinradoiu]

• Fix missing product surface usage pixels for autocomplete and data clearing and update website loaded pixel usage #9348 👈 (View in Graphite)
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.