File: anonymous-ping.rst

package info (click to toggle)
firefox 134.0.2-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,345,684 kB
  • sloc: cpp: 7,244,582; javascript: 6,236,669; ansic: 3,654,775; python: 1,359,774; xml: 618,542; asm: 426,944; java: 183,315; sh: 66,206; makefile: 19,398; perl: 13,009; objc: 12,453; yacc: 4,583; cs: 3,846; pascal: 2,989; lex: 1,720; ruby: 1,194; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10
file content (68 lines) | stat: -rw-r--r-- 2,237 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68

"anonymous" ping
================

.. note::

    This ping is no longer sent by Firefox or Fennec.

This ping is only for product survey purpose and will not track/associate client ID or profile group ID. It's used
to evaluate custom tab usage and see which app is using our custom tab.

Submission interval & triggers
Since this ping is used to measure the feature usage, it should be sent each time the client app uses our custom tab.

Dataset:
Only opt-in users will send out this ping.
Since all other pings will collect client ID and profile group ID. We need this custom ping to not do that.

Size and volume:
The size of submitted payload is small. And this custom ping should be deprecated after it's released for 6 months.

Privacy:
We won't collect customer information so there'll be no PI leak.

Data contents:
The content of this ping will let us know which app is using our custom tab.
Just like other feature usage measurement, we only need it for opt-in users (which consider as heavy users).

Structure:

.. code-block:: js

    {
      "payload": {
        "client":  <string> // The package name of the caller app.
      }
      type: <string>, // "anonymous", "activation", "deletion", "saved-session", ...
      id: <UUID>, // a UUID that identifies this ping
      creationDate: <ISO date>, // the date the ping was generated
      version: <number>, // the version of the ping format, currently 4

      application: {
        architecture: <string>, // build architecture, e.g. x86
        buildId: <string>, // "20141126041045"
        name: <string>, // "Firefox"
        version: <string>, // "35.0"
        displayVersion: <string>, // "35.0b3"
        vendor: <string>, // "Mozilla"
        platformVersion: <string>, // "35.0"
        xpcomAbi: <string>, // e.g. "x86-msvc"
        channel: <string>, // "beta"
      },
    }

Field details
-------------

client
~~~~~~
It could be ``com.example.app``, which is the identifier of the app.

Version history
---------------
* v1: initial version - Will be shipped in `Fennec 55 <https://bugzilla.mozilla.org/show_bug.cgi?id=1329157>`_.

Notes
~~~~~
There's no option in this custom ping since we don't collect clientId, profileGroupId nor environment data.