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

ivy_nair_bde69

Posting this for trial users. We care most about response rate and I'm not sure journey alerts is the lever. Talk me out of it?

Find more posts tagged with

Comments

diego_hale_51d4d

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

marcus_holt_fb8df

Have you tried routing it through Zendesk? Fixed the time-to-resolution gap for us.

tara_frei_3bd16

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

bea_sato_471c8

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

tom_pratt_3ad2e

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

nina_marsh_a58ff

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

maya_sato_a66f2

We hit this too. Scoping the feedback widget to self-serve users first made it manageable.

gus_reyes_fda1c

We hit this too. Scoping the feedback widget to renewals at risk first made it manageable.