How to Create Lists in HubSpot for a Bilingual Database

A list in HubSpot is a saved group of records that share criteria, and you build one from Lists under Contacts in about five minutes. The slower decision, and the one that determines whether the list is worth anything, is which property it filters on: in a database that holds Arabic and English contacts, that decision has to be made before the first list exists.

The most successful users of HubSpot are those who are able to seamlessly align their marketing efforts with their sales efforts, and lists are where that alignment is stored. They are the building blocks for targeted campaigns, personalized experiences and highly effective workflows. Yet in a bilingual portal most of them are built on English-shaped assumptions, which is why the counts look plausible, the preview looks correct, and the send still misses people.

Here is what lists are, how to create them, and what quietly shortens a regional one.

What is a List in HubSpot?

A list in HubSpot is a curated grouping of contacts or companies that share specific criteria, allowing you to sort your database into manageable groups. These groups can be as broad or as specific as you need, allowing you to target your marketing and sales efforts better.

They are used for sending emails, enrolling records in workflows, sending feedback forms, and running bulk updates against a defined set of records rather than the whole database.

Active Lists and Static Lists: Which One, and When

Use an active list wherever membership is a question you will ask again, and a static list wherever you need a record of who was in the group at one moment.

Active Lists

These are living, breathing lists that automatically update as your database changes. If a contact meets the criteria you've set, they're added; if they no longer qualify, they're removed. This is ideal for segmenting your audience based on dynamic behaviours or properties.

Static Lists

These lists are snapshots in time. Once created, they remain unchanged unless manually edited. They're perfect for one-time campaigns or specific segments that don't require constant updates.

The trade-off is not the one it looks like. Static feels like the cautious choice because nothing moves underneath you, and that is exactly what it is: a snapshot of who met the criteria when the list was saved, which never picks up a record that qualifies later. An active list does update, but not instantly. HubSpot's own guidance is that a record should join an active list straight after its properties change, and that for complex segments or bulk property updates the refresh may take up to an hour. So a language segment rebuilt by bulk edit and sent against immediately can go out short, with nothing raising an error.

The one send route where HubSpot states the recipient set outright does not rescue that either. On an email scheduled by recipient time zone, which needs Marketing Hub Professional or Enterprise, contacts added to the list after the email was scheduled are not sent it at all: recipients are fixed at schedule time, not at send time. A segment you have not finished building is not a send you can repair afterwards; it is a send you have to run again.

Set the Language Property Before You Build the First List

The property that has to exist before any of these lists do is preferred language, because it is the one that cannot be applied backwards.

Which language a contact wants is not a minority attribute somebody can hold in their head. Our own research on MENA CRM buyers finds 72% expect Arabic-language content, so on a regional database that question splits the file rather than carving a small group off the end of it. A filter can only sort on something a record stores, which makes preferred language a property you create rather than a segment somebody reconstructs after the first complaint.

W3Techs, which surveys the content language of the websites it tracks, puts Arabic at 0.6% of them, one of the widest gaps between speaker population and online content share of any major language. Our own reading of that gap, not something the survey measures, is that the Arabic-preferring half of a regional database tends to arrive from somewhere other than the website: events, resellers and spreadsheets. It arrives with no language value unless someone decides on one.

So the order is: create the property, populate it on the records you already hold, then build the list. A list cannot filter on a property that is not there yet, and a bulk backfill run on the morning of a send is precisely the case HubSpot says can take up to an hour to reach an active list. Storing the value correctly, in custom properties and objects that hold Arabic text as it was typed, is one component of Arabic-first HubSpot delivery.

How to Build Lists in HubSpot

1. Navigate to the Lists section under Contacts in your HubSpot account.
2. Click Create List in the upper right corner.
3. In the left panel, select Contact-based, Company-based, or Deal-based, depending on the type of list you want to create.
4. Enter the name of the list and select whether you want the list to be an Active List or Static List.
5. Click Add Filter and select the criteria for categorizing your contacts. Click Apply Filter once complete.
6. Once you enter the criteria, HubSpot will generate a preview of your list. Make sure this list is correct and the criteria you've selected is accurate, and then hit Save.

Step 6 is where a regional list is usually lost, because the preview looks right.

Why Does an Arabic List Come Back Short?

Not because the filter is fussy. Because it is loose in the wrong direction.

HubSpot's text filters do not match the exact stored string. "Contains any of" is a case-insensitive substring test, and HubSpot's own worked example is that filtering Job title by contains any of CTO returns the records reading CTO and the records reading Director, because "cto" sits inside both. "Contains exactly" matches the exact entered tokenized text. That looseness is what makes the Arabic failure so easy to miss: a filter generous enough to pull Director out of CTO feels like it will forgive a spelling, and it will not, because none of that matching normalises Unicode.

A company or city name typed with a different alef form (أ, إ or آ against a bare ا), or with ta marbuta ة where another record has ه, is a different string, and a different string is a miss. The list saves, the preview is populated, and the membership is quietly short. Nothing flags a near miss, so the gap surfaces later as an underperforming campaign rather than as a data problem.

Two constraints decide what you can do about it inside the list tool, and both narrow the options:

• There is no wildcard to fall back on. HubSpot states that for most text criteria in segment filters, a wildcard is not supported. One pattern cannot cover the alef family, so the variants have to be enumerated as separate values inside a single "contains any of" condition, and that condition has to be revisited every time a new spelling enters the database.
• The one automatic repair cannot reach these fields. HubSpot's property formatting fixes require Marketing, Sales, Service, Data, Content or Smart CRM Professional or Enterprise, and they cover Email, First name and Last name only: capitalisation, combined fields, spacing and punctuation. Company and City sit outside them, and none of it addresses non-Latin script.

So the fix belongs at import, where the values can be normalized as they land. Enumerating the variants inside the filter is the repair you run on a database you have inherited, not the way to build one.

The Import Decides What Your Lists Can Find

Most unusable lists were made unusable before the list existed, by an import that resolved records against the wrong key.

Contact imports deduplicate on Record ID first, then email address. Company imports deduplicate on Record ID, then domain name, and the regional trap in that second rule is not the one people expect. Subdomains do not collapse: HubSpot creates a company record for each unique domain, including subdomains, so @example.com and @info.example.com land as two companies rather than one.

The damage is in the associations instead. Several companies can legitimately hold the same Company domain name, and where they do, contacts with emails at that domain are automatically associated with only one of them. HubSpot states plainly that it is not possible to select which, so the associations for the construction arm have to be corrected by hand after the contacts are created. Reaching for a merge to tidy that up is the door that does not open again: HubSpot does not unmerge records, the primary record's property values win, and the secondary record's email address or domain name survives only as a secondary value. Our step-by-step Mailchimp to HubSpot migration guide covers that sequencing in more detail.

The other import decision that reaches every future list is the name column. Arabic personal names do not split reliably on the first space: multi-part given names and the bin and bint elements mean a legacy full-name column mapped into First name and Last name mislabels a large share of a Gulf list, and the error is invisible to a reviewer working in English. The mapping gets signed off, and a personalization token later greets a senior buyer by half of a given name in a send that has already left.

How to Manage and Edit Lists in HubSpot

Once you've created a list, you can easily manage and edit it. You can add or remove filters, rename the list, or even delete it if it's no longer needed. HubSpot provides a user-friendly interface to make these adjustments.

To manage a list simply navigate to Contacts in the top-left corner of the screen and Lists in the drop-down menu. From here you can select any list you want to manage, with the More dropdown menu giving you options such as Clone, Export, Delete or Move to Folder.

One bulk action deserves more caution than the interface suggests, on the portals where it exists at all: marketing contacts are a Marketing Hub Starter, Professional or Enterprise concept, so a Sales-Hub-only or free portal has no such state to unwind. Where they do exist, a contact already set as marketing in a given month cannot be set back to non-marketing on the spot. The change waits for the portal's next update date, and the Marketing contact until next update property reads Yes in the meantime, which is how a pending downgrade tells itself apart from a failed one. An inherited list flagged during a migration therefore cannot be unflagged in the cycle you notice it, and the billing relief runs later still, because removing marketing contacts does not automatically downgrade the contact tier before renewal. Worth knowing before deciding how to make someone a marketing contact at scale.

5 Key Ways Lists Can be Used in HubSpot

1 - Build a List Based on a Form Submission

Create a list of contacts who submit a specific form, allowing for targeted follow-ups, nurture campaigns, and lead scoring based on form data.

2 - Build a List Based on Email Actions

Identify contacts who opened, clicked, or bounced specific emails to tailor future communications. Before building those lists across two languages, settle the subscription types underneath them. One subscription type shared by Arabic and English sends means an unsubscribe from either stops both, because each type creates exactly one opted-out property. Splitting by language is directly supported, since a subscription type carries its own Language field, and custom types need Marketing Hub Starter or above, so a portal on free tools cannot create them at all.

What decides the timing is what a new type does to the contacts you already hold. On an EU-hosted portal, which is how signups from the Middle East and Africa are provisioned, a newly created subscription type starts every existing contact at Not specified, and a contact in that state cannot be emailed without obtaining explicit consent first. Splitting a bilingual type after launch therefore does not divide an audience into two; it creates a second one nobody may be sent on until consent has been collected again. Types can be archived but not merged or deleted, so take the decision before the first bilingual send, because every engagement list you build afterwards inherits it.

3 - Build a List Based on Specific Contact Properties

Segment your audience based on specific contact properties like job title, industry, company size, or custom properties. In a regional portal the two properties that earn their place first are preferred language and market, because they change what a contact is sent as well as who reports on them.

4 - Build a Company-Based List for the Buying Group

Create lists based on deal stage, value, deal owner, or company-level criteria for targeted sales outreach. The room on a regional enterprise deal is five to twelve stakeholders across six roles, from economic buyer to compliance influencer, and Gartner's 2025 B2B buyer survey found technology buying groups now range from 5 to 16 people across as many as four functions globally. A contact list tells you who engaged; a company-based list tells you which accounts still have no named contact in a role that has to approve, which is the gap that stalls a six to nine month public sector cycle.

5 - Build a List Based on Workflow Actions

Use workflows to populate lists automatically based on specific actions or criteria. This can be used for lead scoring, lifecycle stage progression, or other automated list management tasks.

Where to Start

If your database already holds Arabic and English contacts, start with the property audit rather than the list: preferred language, market, and the spellings your text properties actually store. Everything above is recoverable at that stage and expensive afterwards.

Not sure where to start with your inbound marketing efforts and optimizing HubSpot? Get in touch with the Meticulosity Global team, a HubSpot Diamond Solutions Partner, a status held by fewer than 3% of HubSpot partners worldwide. We'd love to help you maximize your marketing efforts and optimize your HubSpot investment.