-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backfill Missing "Product ID" in fxa_pay_setup - 3ds_success events #12564
Comments
➤ Barry Chen commented: Claas https://mozilla-hub.atlassian.net/browse/FXA-4837 ( https://mozilla-hub.atlassian.net/browse/FXA-4837|smart-link ) is marked as a duplicate of this and that’s already done. Is that accurate? |
➤ Claas commented: Barry Chen Thanks for asking:
|
➤ Claas commented: Now that new PayPal subscription events properly record the Product ID, the remainder of this ticket is about back-filling the Product ID (prod_LKvr8fYGbBxcaZ) of all old PayPal subscription events (fxa_pay_setup - 3ds_success) with the following Plan IDs that have no Product ID set yet:
Anna Sobiepanek You mentioned ( https://mozilla.slack.com/archives/CG0AJ6E77/p1649952649911179?thread_ts=1649950742.583339&cid=CG0AJ6E77 ) that this needs to go through SRE. Do I need to file a separate ticket for this? |
➤ Claas commented: Dustin Lactin Jon Buckley Please don’t hesitate to ping me on Slack if you need any additional details about this. We would like to analyze the subscriptions of our launches in US/CA and EU via Looker, but these incomplete PayPal subscription events are effectively blocking us from doing so. |
➤ Jon Buckley commented: Claas I looked into the Looker data set you’re using for this dashboard and it’s using mozdata.firefox_accounts.fxa_content_auth_stdout_events - this is not a table that Dustin Lactin and I have access to update. I am asking around to see who can assist you in backfilling this data. |
➤ Jon Buckley commented: Daniel Thorn Anna Scholtz Would either of you be able to assist in running this backfill? |
➤ Anna Scholtz commented: How far back should we backfill the data? |
➤ Claas commented: Anna Scholtz We launched in March’22, so the oldest affected event should be from 2022-03-24. |
➤ Anna Scholtz commented: The backfill is running and should be done in an hour or so. |
➤ Claas commented: Anna Scholtz Thank you. How long does it take until the backfill will be visible in Looker ( https://mozilla.cloud.looker.com/dashboards/596 )? |
➤ Anna Scholtz commented: It should be up-to-date |
➤ Claas commented: Hm, either Looker is not yet up-to-date or the backfill did not work as expected. 😕
PS: Since this issue is synced with GitHub, I cannot share any screenshots here. |
➤ Jon Buckley commented: Sorry, I goofed here - I asked for a backfill before actually doing the update on the BQ tables in the fxa-prod project. Let me get than done, then we should be in position to run the backfill again and then Looker should be updated correctly |
➤ Claas commented: Jon Buckley No worries! Have you already finished the update so that the backfill could be run again? |
➤ Jon Buckley commented: Here’s the query I ran to get all of the rows missing the product ID and generate a new event_properties JSON string SELECT UPDATE |
FxA is no longer synchronizing all issues between Jira and Github. We are closing open issues and will selectively synchronize in the future. |
Background
As a member of the MDN team, I have created a Looker dashboard to track MDN Plus subscriptions over time, by visualising
fxa_pay_setup - 3ds_success
events.Problem
We would like to filter those events using the Product ID field, but unfortunately about half of the events have no product ID set, i.e. it is
null
for those events (see this dashboard for a distribution by Plan ID and Timestamp Date).As a workaround, we are currently filtering via the Plan ID field:
While we only have 4 plans so far, we will add several new plans this week as part of the EU launch.
Acceptance criteria
All
fxa_pay_setup - 3ds_success
events for MDN Plus subscriptions (both old events and new events) should have the Product ID field set toprod_LKvr8fYGbBxcaZ
.┆Issue is synchronized with this Jira Bug
The text was updated successfully, but these errors were encountered: