Static vs Dynamic Marketing Lists in Dynamics 365 CRM

A static marketing list in Dynamics 365 is a fixed, manually managed roster — members only change when you add or remove them. A dynamic marketing list stores a saved query and re-evaluates it against live CRM data every time the list is used, so membership updates automatically. Use static lists when the audience is known and finite (event attendees, approved VIP contacts); use dynamic lists when the audience is defined by criteria that evolve over time (contacts in a region, leads from the last 90 days).

A note on product context: marketing lists live in two places today. The Dynamics 365 Sales app (in-app marketing) retains the classic static/dynamic list model. Dynamics 365 Customer Insights – Journeys — formerly Dynamics 365 Marketing — uses the newer segments model, though marketing lists created in Sales can still be included inside Customer Insights – Journeys dynamic segments.

How do static marketing lists work?

A static list is a hand-curated snapshot. You add records one by one, through lookup, or in bulk via Advanced Find — and they stay on the list until you explicitly remove them. The membership does not change between now and the next time you open the list.

When I set up a list for a conference follow-up or a limited product announcement, I reach for static. The audience is known, it will not grow on its own, and I want full control over who receives the campaign. Static lists support contacts, leads, or accounts — but not a mix; you pick one record type per list and cannot change it after saving.

Practical limits per Microsoft Learn:

• Add operations under 30,000 members run synchronously. Above that threshold, Dynamics processes them asynchronously in batches of 1,000.
• A single Add operation supports up to 120,000 members. For larger lists, split into multiple operations — or consider switching to a dynamic list.
• Only active records can be added.

How do dynamic marketing lists work?

A dynamic list stores a query, not a roster. Each time you open the list, distribute a campaign activity, or create a quick campaign from it, Dynamics 365 re-runs the query against live CRM data and returns the current matching records.

This makes dynamic lists well-suited for criteria that change: customers in a specific region, contacts tagged with a particular industry, leads created in the last 90 days. You define the filter once using Advanced Find, select Use Query, and the list is always current without manual intervention.

The trade-off is less precision. Anyone who meets the criteria is included, including contacts you may not want in a particular campaign. When the audience definition matters more than strict control, dynamic lists are the practical choice.

Static vs dynamic: key differences at a glance

	Static list	Dynamic list
Membership	Manually added and removed	Auto-refreshed at each use
Query stored	No	Yes — re-evaluated on demand
Membership changes when CRM data changes	No	Yes
Best for	Fixed audiences, one-off campaigns	Criteria-based, ongoing targeting
Effort after setup	Higher (manual maintenance)	Lower (self-maintaining)
Audience predictability	Exact	Varies with data

How segments in Customer Insights – Journeys relate to this

If you are working in Dynamics 365 Customer Insights – Journeys — the current platform for marketing automation in the Dynamics 365 family — the equivalent of dynamic marketing lists is segments built in the segment builder.

Customer Insights – Journeys segments support demographic, firmographic, and behavioral conditions. Behavioral segments, for example, can target all contacts who opened a specific email in the last seven days or registered for an event. These are always dynamic in nature: the segment evaluates against real-time interaction data each time a journey runs.

Marketing lists created in the Dynamics 365 Sales in-app marketing area are not removed and can still be included inside Customer Insights – Journeys dynamic segments. However, the outbound marketing module — which previously hosted its own segment builder — was fully removed in May 2026. Any segments built there are no longer active. If you have not yet moved to the Customer Insights – Journeys segment builder, that transition is overdue.

When to use a static list

Static lists suit situations where the audience is fixed by definition:

• Event follow-up: attendees of a past webinar or conference — this group will not expand retroactively.
• VIP outreach: a named account list that sales has approved one contact at a time.
• Regulatory or consent-specific campaigns: where you need an auditable record of exactly who received a communication.
• Testing: a small, controlled group before a broader rollout.

In my experience, static lists also work well when you are inheriting a list from another system — an event registration export, for example — and you need to import it cleanly without query logic.

When to use a dynamic list

Dynamic lists suit criteria-defined audiences that evolve:

• Geographic targeting: all contacts in a city or region (as contacts are added to the CRM, they are automatically included).
• Lifecycle stage campaigns: leads created in the last 60 days, or customers who have not purchased in 12 months.
• Industry verticals: accounts tagged with a specific industry code.
• Ongoing nurture: any audience where the definition matters more than the specific individuals.

I reach for dynamic lists when a client's sales team is actively adding contacts to the CRM and the campaign should pick them up without weekly list refreshes. It removes a maintenance step that is easy to forget.

Managing list quality over time

Both list types require some upkeep. For static lists, the main risk is staleness — a contact leaves a company, an address bounces, but they remain on the list. I recommend reviewing static lists quarterly at minimum and removing records that are no longer active.

For dynamic lists, the risk is query drift: the criteria that were accurate six months ago may now include records you did not intend. Revisit the query logic whenever your CRM data model changes or when you notice unexpected contacts appearing in campaign reports.

Good list hygiene also supports your Dynamics 365 CRM customization practices — clean data in means clean lists out.

For teams running both in-app marketing (Sales) and Customer Insights – Journeys campaigns, it is worth establishing a naming convention that distinguishes Sales marketing lists from Journeys segments. Both can appear in the same interface, and the distinction matters for how they behave.

Connecting lists to campaigns

Marketing lists plug into campaigns through the Summary tab of any campaign record — select Add Existing Campaign inside the list, or add the list from inside the campaign. Quick campaigns can be launched directly from a list.

For teams using Customer Insights – Journeys, segments attach at the journey entry point. You define the audience once at the start of a journey and all branches inherit it. This is a cleaner model than the per-campaign list association in in-app marketing, and it is one of the reasons Microsoft moved the platform in that direction.

For more on how the broader D365 marketing toolset fits together, see our overview of Dynamics 365 AI and Copilot capabilities and our guide to the Dynamics 365 Customer Insights solution.