Closed Bug 1284932 Opened 6 years ago Closed 4 years ago

Investigate Fennec Telemetry retention mismatch with Adjust data


(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)



(Not tracked)



(Reporter: gfritzsche, Assigned: frank)


(Blocks 2 open bugs)


This is following up to the findings from bug 1260715.
We need to understand why the retention numbers between Adjust & Telemetry is off by a big amount.

* unsorted London notes:
* re-structured docs of the issues & status:
Priority: P2 → P1
to you Georg, please re-assign/unassign if that wrong.
Assignee: nobody → gfritzsche
It was scheduled for this iteration, i'll assign myself to it when i'm back on this.
Assignee: gfritzsche → nobody
Assignee: nobody → gfritzsche
In a first step, i've updated the new document with charts for active users and retention:

Active user numbers seem fine from a high-level look. They are trending towards 10% below the Adjust numbers, which seems reasonable given update lag (we only get proper UT data from Fennec 46 on).

Retention is definitely off:
* d0 (or new_records) is way higher in UT than in Adjust (trending towards UT being 140% of Adjust)
* d1 is less of, trending towards UT being 124% of Adjust
* d7 and d30 are less off respectively
Depends on: 1291265
Priority: P1 → P2
Assignee: gfritzsche → nobody
Priority: P2 → P3
Points: 3 → ---
Priority: P3 → --
Whiteboard: [measurement:client]
please update once you start working on it FRank
Assignee: nobody → fbertsch
Priority: -- → P2
I'll be working on this, if needed, after the KPI dashboard reboot.
Priority: P2 → P3
Closing abandoned bugs in this product per
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.