In rare cases, we may need to add event listeners in the content process which also trigger
a network event that would be parsed by the network observer. To avoid counting double
engagements, I propose we add a new array of regular expressions that when a URL matches, will
never be parsed by the SERP telemetry logic in the network observer. This would rely on the
content process events listeners to register the engagement event.
I think the regular expression should be specific enough that it shouldn't match something
in a search result lest we ignore a click on it.
Differential Revision: https://phabricator.services.mozilla.com/D202583
771da539f9