nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rate limits when backfilling the in-app survey via the API?

esme_voss_44c5f

Trying to get journey mapping right for new onboarding cohorts. The defaults don't quite fit. What did you change?

Find more posts tagged with

Comments

ruth_carr_58faa

We measure response rate weekly now and it's made session replay decisions much easier.

marcus_vance_525c6

Curious what cadence you landed on. We over-asked and churn tanked.

omar_dunn_b467c

We hit this too. Scoping auto-theming to our SMB tier first made it manageable.

omar_pace_2ee77

We hit this too. Scoping CSAT surveys to enterprise accounts first made it manageable.

nadia_carr_b6c5d

Same setup here. In our case it came down to journey alerts being too broad.

elena_carr_9bfd5

Spent a week on this. The fix was tying response routing to the account owner field.