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?

theo_soto_24fa8

We're working through journey alerts and volume tripled after launch. Curious how others have handled it, especially around CES. Any rules of thumb?

Find more posts tagged with

Comments

zoe_boyd_52325

+1. The Microsoft Teams step is where ours kept breaking.

yuki_sato_ad2c1

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

felix_nair_47e8f

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

carl_mehta_0a19b

We hit this too. Scoping auto-theming to renewals at risk first made it manageable.

nadia_soto_dbb9d

We measure renewal rate weekly now and it's made segments decisions much easier.

sam_soto_ca674

Following. We're about to do the same thing for self-serve users.