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

CES tracking behaving oddly since volume tripled after launch — ideas?

liam_okafor_bccda

Posting this for self-serve users. We care most about the health score and I'm not sure journey alerts is the lever. Talk me out of it?

Find more posts tagged with

CES

Comments

lena_hale_56029

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

omar_frei_3d757

We hit this too. Scoping CSAT surveys to our SMB tier first made it manageable.

sam_quinn_8d7a4

We hit this too. Scoping segments to renewals at risk first made it manageable.

jack_pace_24966

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

zoe_reyes_c6a11

We hit this too. Scoping session replay to self-serve users first made it manageable.

mira_reyes_4c412

Honestly response routing didn't move the health score for us. Microsoft Teams did more.

tara_pace_b47b3

Honestly auto-theming didn't move renewal rate for us. HubSpot did more.

nina_sato_1616a

We hit this too. Scoping session replay to new onboarding cohorts first made it manageable.