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 segments into Segment cleanly

carl_holt_776d0

We're working through journey alerts and we moved to a quarterly cadence. Curious how others have handled it, especially around the health score. Any rules of thumb?

Find more posts tagged with

Comments

omar_quinn_a3ddb

Worth checking your CES window. Ours was skewed until we narrowed it.

sam_vance_f7e22

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

ivy_sato_a0e62

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

kiran_akoto_f9009

We measure CSAT weekly now and it's made journey alerts decisions much easier.

esme_rourke_76fa0

Worth checking your response rate window. Ours was skewed until we narrowed it.

ned_rourke_0b8ef

Following. We're about to do the same thing for trial users.

sam_soto_21954

Honestly CSAT surveys didn't move CSAT for us. Salesforce did more.

gus_voss_f678e

We hit this too. Scoping the in-app survey to renewals at risk first made it manageable.