1872904 - Send trusted_deals_placement upon fetching the Fakespot ad unit from a server

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: Shopping, task, P2)

Description

[Chris Peterson [:cpeterson]]

User story
As server-side engineering and experimentation teams, we need to know that a client has fetched an ad unit, so that we can collect data on how many ad units would have been displayed to a user without actually displaying them on the client.

Acceptance criteria

1. A placement event – trusted_deals_placement is sent to PE, regardless of whether the component containing the trusted deals is visible on the screen or not (please note that this event is not a replacement or duplicate of trusted_deals_impression event, sent once the

2. The event must include “aidvs”. Other optional data included for metrics are component location, current asin, and current product url.

Please see the full sample event in the doc here and the diagram of the client-server interactions in the attached image.

Comment 1

[Chris Peterson [:cpeterson]]

This bug is a clone of desktop bug 1872872.

Comment 2

[Chris Peterson [:cpeterson]]

Jared says it might be possible to record this telemetry in the toolkit code, in which case android would get this for free as a result of the desktop fix for bug 1872872.

Comment 3

[Chris Peterson [:cpeterson]]

How does this trusted_deals_placement event different from the shopping.ads_exposure event added in bug 1866992?

https://dictionary.telemetry.mozilla.org/apps/fenix/metrics/shopping_ads_exposure

Comment 4

[Chris Peterson [:cpeterson]]

Cathy has completed the GV and AC parts and just needs to add it to Fenix.

Comment 5

[Joe McBride]

I think there is missing context on the Acceptance criteria, item 1:

A placement event – trusted_deals_placement is sent to PE, regardless of whether the component containing the trusted deals is visible on the screen or not (please note that this event is not a replacement or duplicate of trusted_deals_impression event, sent once the ad is visible to the user for 1.5 seconds.

Comment 6

[Joe McBride]

The desktop bug for this: https://bugzilla.mozilla.org/show_bug.cgi?id=1872872

Comment 7

[Joe M [:jmahon]]

Marking this as a P2 to make sure it's considered high priority before we do any kind of roll out for fakespot product recommendations. (But it's not a P2 in the sense that we need someone to do it in this release cycle - it only becomes important if we do roll out those product recs)