Closed Bug 2079077 Opened 1 month ago Closed 1 month ago

play-store-attribution ping not received for ~35% of Meta (Facebook/Instagram) installs since Fenix 153

Categories

(Firefox for Android :: Experimentation and Telemetry, defect, P3)

Firefox 153
All
Android
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: Alekhya, Unassigned)

References

Details

Steps to reproduce

Expected behavior

A play-store-attribution ping is submitted for every Play Store install once the install referrer has been read, carrying play_store_attribution_install_referrer_response and the parsed UTM values. The ping has send_if_empty: true, so it should be sent even when empty.

Actual behavior

For ~35% of Meta-referred installs on 153+, no play-store-attribution ping is ever received, even though the client read and parsed the referrer:

  • The UTM values (apps.facebook.com/fb4a, apps.instagram.com/ig4a) appear in client_info.attribution on the baseline ping for ~95% of affected installs.
  • The marketing opt-in card, which InstallReferrerHandlingService.kt only shows when the referrer is non-empty, is accepted at 92%, versus 93% for unaffected Meta installs.
  • The ping isn't late; it never arrives. Of 24,159 affected installs in September 2026, 99.8% had no play-store-attribution ping at all within 5 weeks; only 1 arrived late. That suggests there's no retry.

Device information

  • Firefox version: 153 and later (153–157 confirmed). Not seen on 150–152.
  • Android device model: all makers affected. Highest on vivo (~45%) and Xiaomi (~46%), lowest on Google Pixel (~15%) and Nothing (~16%).
  • Android OS version: not limited to a particular version in the data so far (distribution available on request).

Any additional information?

It started at Fenix 153 (installs Adjust credits to Meta with no referrer in fenix.new_profile_clients, Play Store installs only):

| Fenix version | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 |
| No referrer | 0.68% | 0.37% | 0.26% | 40.3% | 28.1% | 38.2% | 33.5% | 29.7% |

  • It follows the app version, not the ad campaigns: in the same week (Jul 19, 2026), v152 had 0% of 343 installs affected and v153 had 38% of 310.
  • Mostly Meta: non-Meta Play Store installs stay at 0.5–1.1% across 151–157. Countries are evenly spread (IN 35.5%, ID 38.2%, BD 34.9%, MX 39.9%, US 31.7%).
  • The device pattern (vivo and Xiaomi worst) suggests background work in InstallReferrerWorker.kt (WorkManager) being stopped before the ping is submitted.
    Data-side workaround: Data Engineering is adding a fallback to baseline_clients_first_seen.attribution, which recovers ~95% of these installs (Jira DENG-11673). A client fix is still needed: gclid-only referrers can't be recovered that way.
Flags: needinfo?(joberhauser)
Severity: -- → S3
Priority: -- → P3

I'm not up to date with the ad campaign stuff. Maybe Roger is

Flags: needinfo?(joberhauser) → needinfo?(royang)

Investigation confirms that this was a Glean issue triggered by the truncation of Meta attribution data.
https://github.com/mozilla/glean/pull/3564.

Glean's fix is landing in v158 and we should see this issue fixed then.

Also created an issue to request for double the length before truncation. https://bugzilla.mozilla.org/show_bug.cgi?id=2079526

Flags: needinfo?(royang)
See Also: → 2079526

Closing as fixed. Please reopen if the issue is not fixed in v158. Thanks

Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.