Reducing user drop-off in the Entri Connect flow

The Connection Success Rate on your Entri dashboard tells you what percentage of unique domains successfully completed the Connect flow. When that rate drops below 75%, it's a good signal to investigate what's causing users to leave before completing setup

This guide intends to help our clients to improve the Success rate percentage in some steps.

1 - Use prefilledDomain property

If your application already knows the user's domain from onboarding, account settings, or a previous step — pass it via the prefilledDomain property. This bypasses the domain input screen entirely, reducing the chance of losing the user in that step.

showEntri({
  applicationId: "your-app-id",
  prefilledDomain: "user-domain.com",
  dnsRecords: [...]
});

Best practice

Collecting the user's domain earlier in your onboarding flow (before opening Entri) is the most reliable way to enable pre-filling and the single most effective change you can make.

2 - Simplify the experience for non-technical users

If your users aren't technically savvy, several whiteLabel.customProperties options let you hide or skip certain screens or options, resulting in a cleaner, more focused experience with fewer distractions.

The properties we recommend:

initialScreen.disableScreen

existingRecords.disableScreen

providerLogin.changeProvider.hide

providerLogin.forwardLink.disable

providerLogin.gotoManualLink.disable

providerLogin.recordsPreview.hide

congratulations.disableScreen

Keep in mind

Some of these properties hide technical details from your users, for example, which DNS records are being configured, or warnings about existing conflicting records that Entri will replace. If that information is important to your users or your support workflow, leave those properties out and apply only the ones that make sense for your use case.

3 - Trigger the modal at the right moment

Only call showEntri() at a point in the user journey where they are actively focused on domain setup, not buried in a settings page or as a secondary step. Contextual triggers dramatically improve engagement and reduce idle abandonment.

Good moments to open the modal include: immediately after a user adds a custom domain, as a focused step in a setup wizard, or in response to an explicit "Connect your domain" action.

4 - Use onEntriClose to diagnose drop-offs

Diagnostic

Implementing the onEntriClose callback gives you visibility into when and where users are leaving. This helps confirm whether drop-offs are happening at the input screen versus another point in the flow, so you can target your improvements accurately.

window.addEventListener("onEntriClose", (event) => {
  const { lastFilledField, reason } = event.detail;
  // Log or act on abandonment data
});

Use the lastStatus field to segment your users and trigger tailored follow-up messaging, for example, a nudge email or an in-app prompt to resume setup.

5 - Set a fallback for unsupported providers

For DNS providers where automatic setup isn't supported, set forceManualSetup: true together with prefilledDomain. This prevents users from getting stuck trying to enter a domain that Entri cannot automate, which reduces confusion-driven abandonment.

showEntri({
  applicationId: "your-app-id",
  prefilledDomain: "user-domain.com",
  forceManualSetup: true,
  dnsRecords: [...]
});

Tip

You can use entri.checkDomain(domain, config) before opening the modal to detect whether automatic setup is available for a given domain, and conditionally set forceManualSetup accordingly.

User retry behaviour

Users who don't complete the flow can return and restart the Entri Connect flow at any time whenever they feel ready. There is no need to create a separate recovery mechanism beyond surfacing the entry point again in your UI.