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?

dana_trin_07405

Posting this for trial users. We care most about time-to-resolution and I'm not sure session replay is the lever. Talk me out of it?

Find more posts tagged with

Comments

ivy_sato_5f807

We hit this too. Scoping auto-theming to trial users first made it manageable.

sam_pratt_2651c

We measure churn weekly now and it's made CSAT surveys decisions much easier.

esme_trin_eae51

We hit this too. Scoping CSAT surveys to trial users first made it manageable.

mira_mehta_ac93f

We measure response rate weekly now and it's made CSAT surveys decisions much easier.

dana_rourke_46023

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

esme_soto_b0794

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