Quickbooky

Accounting News

Marketing & Email

Inactive Mailchimp Subscribers: Finding Them When Menu Names Don't Match

The French help page for finding inactive Mailchimp subscribers points to menus that do not exist; here are the working segment conditions and steps.

COMMUNITY ISSUESQUICKBOOKY

A small but stubborn snag has surfaced for businesses that market to their QuickBooks customer lists through Intuit’s Mailchimp platform. The French edition of the vendor’s guide to finding inactive subscribers sends readers after menu tabs the product never displays. The task itself is simple. The obstacle is mostly a translation layer sitting between the instructions and the interface.

What counts as an inactive subscriber?

An inactive subscriber is a contact who opted in with a valid email address or SMS number and then went quiet on your marketing. How long the silence must last is your call, not a fixed rule. It depends on how often you send and on what you sell. The guide’s own examples: a short sales cycle might treat anyone who skipped your last five emails as inactive. A seasonal business may need a year of silence before the same label is fair.

A translated guide with menus that do not exist

The French page renders English interface names into words you will not find on screen. It directs you to a tab it calls “Audition”, to figures under “Analyses”, and to a “banque” chosen from an “assistance” list. None of those controls exist. Their real counterparts are the Audience menu, the Analytics view inside it, the audience picker, and the Create Regular Segment button.

The page also stops partway through its own procedure. It breaks off just after telling you to open the condition drop-down in the segment builder. Everything after that click is left to guesswork, which is where most readers stall.

Long-term inactives: segment by contact rating

The first method suits contacts who have drifted away over months or years. The entry path is shared by both approaches.

  1. Open the Audience menu and go to Analytics.
  2. If you run more than one audience, use the drop-down to select the one you want.
  3. Click Create Regular Segment.
  4. Open the first condition selector in the builder.

Set the segment to match all conditions. Add a contact rating condition and set it to the lowest mark, shown as a single star. That one-star rating signals negative engagement. Preview the matching contacts, name the segment, and save it.

One caveat matters. Contact rating reflects only regular campaigns and A/B test emails. It ignores SMS activity, automations, ads, and landing pages. Treat it as a verdict on long-term email engagement, nothing more.

Recent silence: segment by interaction

The second method catches people who went quiet recently, on either channel. Enter through the same Audience and Analytics path, then build the segment on interaction instead of rating. Add an email interaction condition for contacts who did not open, scoped to your most recent sends. If you text your list, add the matching SMS condition in the same segment. The lookback window is yours to set. Five campaigns suits a fast cycle; a full year suits a seasonal one.

What should you do once the segment is saved?

Two prerequisites come with the guide. It assumes you already understand how segments work, so practice with a single condition if you are new to them. It also wants this sorting finished before any contact cleanup or win-back send.

The point of the exercise is the next message, not the list itself. Send those contacts a reminder by email or by SMS. The French text labels this a renewal message, which reads oddly; the intent is a re-engagement note. Do this before you delete anyone. If a subscriber still ignores a few attempts, the guide’s suggested next step is archiving, which sets them aside without destroying their history.

For shops that sync customer contacts from QuickBooks Online into Mailchimp, the payoff is an audience that reflects reality. Campaigns land with people who actually read them. Your quiet contacts sit in a labelled segment instead of diluting every send.

← Back to Community Issues