The internal "disqualified" status is now called "flagged," with two clearer reasons behind it: "Low sending volume" and "Low deliverability."

Nothing changes about what you can do — flagged accounts still collect contacts, cancel, and upgrade exactly as before.

In Intercom, the single "Disqualified" company attribute is now two separate fields: "Low sending volume" and "Low deliverability."

If you're on the $0.15/contact pay-per-contact plan, your billing page now shows an Estimated bill this cycle — a projected total based on your current collection rate, with a projected-by date.

In the first 3 days of a new billing cycle, the estimate shows Calculating instead of a number based on limited early data.

This is a read-only estimate — it never affects your actual charges, Stripe billing, or credit balance. Accounts on the legacy $79/month plan and trials will not see this estimate.

Connecting Mailchimp from the integrations catalog was failing for self-serve customers due to an OAuth error. This is now fixed.

Mailchimp now connects successfully when you go through the OAuth flow in the integrations catalog.

If an error does occur during setup, you'll be returned to the integrations page with a clear error message rather than being silently redirected to the dashboard.

New Klaviyo OAuth connections were not syncing any contacts to Klaviyo. This has been fixed — contacts now flow through correctly.

Existing accounts that connected via Klaviyo OAuth before this fix will need a one-time backfill — reach out to support if you're affected.

If your account has multiple Klaviyo connections, contacts now sync through one connection (OAuth takes precedence over legacy API key) to prevent duplicate syncing.

Zapier is no longer available as a new integration option in the self-serve catalog.

Existing Zapier connections that were already set up are unaffected.

For sending contacts to tools outside our supported integrations, the Webhook integration supports the same use cases and works with automation platforms like Make and others.

The Warm [Retention] segment now uses broader criteria — a contact qualifies if they're on your Retention list and meet any one of: added in the last 14 days, received fewer than 4 emails all-time, or opened at least one email in the last 30 days.

Previously, contacts had to meet both the 14-day recency and email-count conditions, which left out engaged contacts.

The Cold [Retention] segment is unchanged.

When you register a new account, we now automatically authorize both your bare domain (e.g. example.com) and its www. variant — so sites that redirect from the apex to www. pass script verification correctly.

Previously, this redirect could cause script verification to fail even with the script installed correctly.

Applies to new accounts only. If you entered a www. or subdomain address at signup, nothing changes.

The HubSpot integration in the self-serve catalog has been updated to use HubSpot's current authentication method. The previous version used a deprecated API key approach that HubSpot retired in 2022, causing every connection attempt to fail.

To connect HubSpot, paste your HubSpot Private App access token (it starts with pat-) during setup.

If you previously tried to connect HubSpot and received an error, you can now retry successfully.

The Klaviyo setup wizard now always shows the list picker step, so you can choose which Klaviyo list your contacts sync to. Previously this step was being skipped.

The auto-created Retention list is pre-selected by default (marked as Recommended) — you can still choose a different list if you prefer.

The Klaviyo setup guide help link has been restored in the integration setup form.

Smart Cap — which recommends a daily collection limit based on your Klaviyo sending volume — was not being applied to accounts using Klaviyo OAuth connections. This is now fixed.

New Klaviyo OAuth connections and any accounts that reconnect will start receiving Smart Cap recommendations automatically.

If you're already connected via Klaviyo OAuth and don't have a Smart Cap in place, re-authorizing your connection will grant the updated scopes. You can also contact support to request a backfill.

Smart caps weren't being set for accounts using the newer Klaviyo OAuth integrations. The Smart Cap service was only matching the legacy API-key integration, so OAuth accounts silently received no daily-throttle recommendation.

All Klaviyo integration types (legacy API key + both OAuth flavors) now match correctly. Existing affected accounts can be backfilled on request.

Manually-set caps are preserved — the backfill only refreshes the stored recommendation and the volume snapshot.

When you connect a Webhook integration in self-serve, a new "Sync your existing contacts" card now appears so you can tell us about contacts you already have — so we don't identify them as net-new (and don't double-charge).

Two sync methods: a one-time CSV upload and an ongoing API sync that provisions an API key on demand.

The card appears on the Webhook integration edit page, the onboarding success step, and the integrations-page setup wizard success step.

Retention.com self-serve pricing has changed for all accounts: the $79/month flat fee is gone.

The new model is $0.15 per contact with no monthly fee — starting from your first contact.

Trial accounts are unaffected — new accounts still get 1,000 free contacts or 14 days, whichever comes first.

The Verify Script step in onboarding now has a "Don't see your domain? + Add one here" option — you no longer have to go back to the Domains step to add a new URL before testing.

Newly added domains appear in the dropdown with a "New" badge and are pre-selected automatically.

The Mailchimp integration in the catalog and onboarding now uses the OAuth flow exclusively — the legacy API-key option is no longer shown to new self-serve customers.

Existing accounts that already connected Mailchimp via API key continue to work as before — only new connections from the catalog are affected.

The Klaviyo integration card in rflow's catalog and onboarding now shows an OAuth tab alongside the API-key option — customers can authorize via Klaviyo's consent screen instead of pasting an API key.

On successful OAuth, the Retention list is auto-provisioned in Klaviyo, suppression sync fires immediately, and Smart Cap / Deliverability Score / Klaviyo segment setup all run in the background.

Disconnecting a Klaviyo OAuth connection revokes the token on Klaviyo's side.

Note: end-to-end OAuth requires Klaviyo to approve the expanded scope set on their side; code is shipped and ready.

The rflow signup form now collects only email, website, and password. First name, last name, and company name fields are gone.

Company name is automatically derived from the website URL, with smart handling of multi-level TLDs, subdomains, and hosting platforms like Shopify.

If first/last names aren't provided, the user's display name falls back to the email local-part so existing analytics and UI that reference "current user" still render correctly.

Self-serve customers can now install the Retention tracking script via Google Tag Manager — authorize with Google, pick a GTM container, and Retention automatically creates the tag, trigger, and publishes the container version. No copy-paste required.

Available as a new option on the rflow onboarding script-install step and the standalone /rflow/script_install page, alongside the existing Shopify and manual install methods.

If a Retention tag already exists in your GTM workspace, the flow detects it and offers to update, skip, or get help instead of duplicating.

On successful install, your domains are marked verified immediately — no need to wait for live visitor traffic.

The "top landing pages" chart on the rflow contacts dashboard now labels each bar with the page's actual title (e.g. "Summer Sale Collection") instead of a URL slug (e.g. "summer-sale").

For older contacts captured before titles were tracked, the slug fallback is still used, and bar tooltips still show the full URL on hover.

The signup form no longer asks for a phone number; you can register with just an email and password.

Existing accounts that already have a phone on file are unaffected, and phone can still be added later in account settings.

The tracking script and "Copy script" button now appear at the top of the Shopify install flow as Step 1, instead of being buried at the bottom of Step 3.

Step 2 combines the "Open Themes" and "Edit code" steps, with the store URL input now sitting directly next to the "Open Themes Page" button it unlocks.

The annotated editor diagram in Step 3 is collapsed by default so it doesn't dominate the paste step, and the "Stuck?" help card now sits at the end of the flow.

Testing your script now returns results inline within seconds — no more redirect or waiting for a separate tab to finish loading.

Adding and verifying a new domain happens in a single step. The domain activates as soon as we confirm the script is installed correctly, so you no longer have to wait for live visitor traffic before it's usable.

When something's off, you'll see exactly what — whether the script is missing, installed more than once, or attached to a different account.