Skip to content

Add Userflow (Staging only)#37686

Open
kaapstorm wants to merge 8 commits intomasterfrom
nh/userflow
Open

Add Userflow (Staging only)#37686
kaapstorm wants to merge 8 commits intomasterfrom
nh/userflow

Conversation

@kaapstorm
Copy link
Copy Markdown
Contributor

@kaapstorm kaapstorm commented May 6, 2026

Technical Summary

Important

This is only open for review

The Product team will be evaluating Userflow on Staging for guiding users and improving feature awareness.

Jira: SAAS-19721

This change is paired with PR dimagi/commcare-cloud#6870

Safety Assurance

Safety story

Only affects Staging.

Automated test coverage

No

QA Plan

No

Rollback instructions

  • This PR can be reverted after deploy with no further considerations

Labels & Review

  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

@kaapstorm kaapstorm requested a review from a team as a code owner May 6, 2026 19:57
@kaapstorm kaapstorm added Open for review: do not merge A work in progress product/invisible Change has no end-user visible impact labels May 6, 2026
@dimagimon dimagimon added dependencies Pull requests that update a dependency file Risk: High Change affects files that have been flagged as high risk. Risk: Medium Change affects files that have been flagged as medium risk. labels May 6, 2026
@@ -0,0 +1,5 @@
import userflow from "userflow.js";

window.userflow = userflow;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is setting a global required (and the best way) now that we're on Webpack? Wonder if @nospame or @jingcheng16 might have input on that?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I would be interested in a better way to do this. The objective here is for userflow to be available in base.html so that is can be initialized and associated with request.couch_user.user_id.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about ce5432f ?

Copy link
Copy Markdown
Contributor

@millerdev millerdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is only for staging, maybe put the branch on staging (before merging) to verify that it works (both with and without a real USERFLOW_TOKEN in settings)? I couldn't tell from the PR description if this has already been tested in both of those modes, but the "without" mode seems especially important since it will be the one that applies on non-staging environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file Open for review: do not merge A work in progress product/invisible Change has no end-user visible impact Risk: High Change affects files that have been flagged as high risk. Risk: Medium Change affects files that have been flagged as medium risk.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants