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 segments via the API?

nina_mehta_89998

We measured time-to-resolution before and after turning on dashboards. The result surprised us. Anyone seen the same?

Find more posts tagged with

Comments

dana_holt_d9dcc

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

diego_pratt_667a6

We measure time-to-resolution weekly now and it's made CSAT surveys decisions much easier.

dana_dunn_145eb

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

marcus_reyes_abf16

We hit this too. Scoping response routing to self-serve users first made it manageable.

lena_vance_dd14a

Same setup here. In our case it came down to the in-app survey being too broad.

maya_mehta_43f96

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

omar_mehta_bc16a

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