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; } } }

Getting the in-app survey into Segment cleanly

carl_carr_b6f3c

Quick one. Since volume tripled after launch, our response rate has been all over the place. Is that a segments config issue or are we reading it wrong?

Find more posts tagged with

Comments

wade_trin_c4ef9

Have you tried routing it through Snowflake? Fixed the time-to-resolution gap for us.

wade_lund_9106e

Curious what cadence you landed on. We over-asked and time-to-resolution tanked.

nina_ng_dfb0f

Honestly journey alerts didn't move renewal rate for us. Jira did more.

owen_trin_3c454

We hit this too. Scoping session replay to enterprise accounts first made it manageable.

sofia_lund_8ed5a

Spent a week on this. The fix was tying journey alerts to the account owner field.

mira_marsh_4480b

+1. The Snowflake step is where ours kept breaking.