Change Details

This task blocks the release of Newcomer Tasks 1.0 because it will affect the instrumentation for mobile. **Desired behavior** When a user visits the mobile homepage, they are supposed to end up seven events: one for each module, with event.action = 'impression' and event.mode = 'mobile-summary'. Then when they tap a module preview, they are supposed to get an event with event.action = 'impression' and event.mode = 'mobile-overlay'. **Current behavior** Right now, when a user visits the mobile homepage, they get fourteen events: seven impression events with event.mode ='mobile-summary' //and// seven impression events with event.mode = 'mobile-overlay'. This makes it impossible to tell when a user taps a module preview from the homepage to open it up.

This task blocks the release of Newcomer Tasks 1.0 because it will affect the instrumentation for mobile. **Desired behavior** When a user visits the mobile homepage, they are supposed to end up with seven events: one for each module, with event.action = 'impression' and event.mode = 'mobile-summary'. Then when they tap a module preview, they are supposed to get an event with event.action = 'impression' and event.mode = 'mobile-overlay'. **Current behavior** Right now, when a user visits the mobile homepage, they get fourteen events: seven impression events with event.mode ='mobile-summary' //and// seven impression events with event.mode = 'mobile-overlay'. This makes it impossible to tell when a user //actually// taps a module preview from the homepage to open it up, because the extra 'mobile-overlay' impressions from visiting pollute the data.

This task blocks the release of Newcomer Tasks 1.0 because it will affect the instrumentation for mobile. **Desired behavior** When a user visits the mobile homepage, they are supposed to end up with seven events: one for each module, with event.action = 'impression' and event.mode = 'mobile-summary'. Then when they tap a module preview, they are supposed to get an event with event.action = 'impression' and event.mode = 'mobile-overlay'. **Current behavior** Right now, when a user visits the mobile homepage, they get fourteen events: seven impression events with event.mode ='mobile-summary' //and// seven impression events with event.mode = 'mobile-overlay'. This makes it impossible to tell when a user //actually// taps a module preview from the homepage to open it up, because the extra 'mobile-overlay' impressions from visiting pollute the data.