Marketing Objects in Salesforce Marketing Cloud Next: A Summer 26 Guide

With the Summer '26 release, Marketing Cloud Next finally ships a data building block that many teams have been waiting for: Marketing Objects. Think of them as the Marketing Cloud Next answer to Data Extensions in Marketing Cloud Engagement. They give you structured containers to store marketing data, load it from CSV files, and then use it directly inside your emails with AMPscript. If you're planning a move to Marketing Cloud Next or spinning up a fresh tenant, this is a component you need to understand. This guide walks you through creating a Marketing Object, defining primary keys, and personalizing messages with the Lookup function.

What is a Marketing Object?

A Marketing Object is a data store built to hold the information behind your marketing initiatives: loyalty programs, product catalogs, customer preferences, or any external reference data. Introduced in the Growth and Advanced editions of Marketing Cloud Next, they fill the role that Data Extensions played in the Engagement world, but inside the platform's next-generation architecture.

A familiar concept from Data Extensions

If you're coming from Marketing Cloud Engagement, the mental model carries over cleanly. You define a schema of typed fields, you designate one or more primary keys, and you load rows of data. The main difference is where you do it: Marketing Objects live in a new Data Management tab added to the Marketing app starting in Summer '26. That tab is now the home for all of your local data modeling.

Configuring a Marketing Object in Data Management

To create your first container, open the Data Management tab, choose to create a new Marketing Object, and give it a clear, descriptive name such as Loyalty_Members. From there you add fields one at a time, specifying the type of each. Consistent naming without spaces will make your AMPscript calls much easier down the line.

Supported data types

At this stage, Marketing Objects support three core types: text strings (up to 255 characters), whole numbers (positive or negative integers up to 18 digits), and decimals (positive or negative decimal numbers up to 18 digits). Pick the type that matches the true nature of the data: a postal code stays a string, a points balance is an integer, and a monetary amount is usually a decimal.

Defining the primary key

The primary key is the single most important decision in your model. It uniquely identifies each row and, crucially, it drives your future Lookup calls: every field configured as a primary key must be supplied as a lookup parameter. An email address or a member ID is usually a solid candidate. If you expect multi-criteria lookups, you can declare a composite key.

Importing data with a CSV file

For now, only manual CSV import is available. From Data Management, select your Marketing Object, upload your file, and map each CSV column to the matching field. Make sure your header row is clean and the file is encoded in UTF-8 to avoid character issues. A well-prepared file, with consistent values in the primary-key column, will save you a lot of back-and-forth.

member_email,member_id,tier_level,points_balance
alice.smith@example.com,10023,Gold,4820
brian.jones@example.com,10024,Silver,1540
chloe.walker@example.com,10025,Platinum,9210

Personalizing emails with AMPscript Lookup

This is where your modeling work pays off. Now that AMPscript is available in Marketing Cloud Next, you can query your Marketing Objects directly in the message body. The Lookup function returns a field value based on a search criterion, and that criterion has to line up with your primary key.

%%[
  SET @email = AttributeValue("email")
  SET @tier = Lookup("Loyalty_Members", "tier_level", "member_email", @email)
  SET @points = Lookup("Loyalty_Members", "points_balance", "member_email", @email)
]%%
<p>Hi there — your current status is %%=v(@tier)=%% with
%%=FormatNumber(@points, "N0", "en-US")=%% points on your account.</p>

To pull back multiple rows — say, a customer's three most recent purchases — use LookupRows and iterate over the result set:

%%[
  SET @rows = LookupRows("Purchase_History", "member_id", @memberId)
  SET @count = RowCount(@rows)
  IF @count > 0 THEN
    FOR @i = 1 TO @count DO
      SET @row = Row(@rows, @i)
      SET @product = Field(@row, "product_name")
    ]%%
      <li>%%=v(@product)=%%</li>
    %%[
    NEXT @i
  ENDIF
]%%

Your primary key isn't a technical afterthought — it's the contract between your data and your content. A Marketing Object without a reliable primary key makes every Lookup unpredictable and undermines your entire personalization strategy.

Modeling best practices

Treat your Marketing Objects like a lightweight relational database. Keep one object per business entity (members, purchases, products) rather than one catch-all table. Standardize your key formats up front — lowercase emails, IDs without spaces — so the value you pass into Lookup always matches the stored data exactly. Finally, validate your code inside the message editor every time: Summer '26 adds syntax validation that lets you combine HTML, Handlebars, and AMPscript freely, highlights errors, and suggests fixes. That means fewer surprises at send time and less reliance on test sends just to catch typos.

Plan around today's limits

Remember that automated import isn't available yet, so plan a manual refresh process for your files, with clear governance around who updates what and how often. Document each object, its fields, and its key, so your CRM and martech teams share a single source of truth.

Key takeaways

A Data Extension equivalent. Marketing Objects are the data containers of Marketing Cloud Next, managed from the new Data Management tab starting in Summer '26.

The primary key is central. It identifies each row and must be passed as a parameter in your Lookup calls, so design it carefully from the start.

Three data types. Strings (255 characters), integers, and decimals up to 18 digits: choose the tightest fit for every field.

Manual CSV import only. Prepare clean UTF-8 files and set up refresh governance while automation is still on the roadmap.

Personalization through AMPscript. Lookup and LookupRows tap your objects directly in the email, and syntax validation in the editor keeps quality high.

Planning your move to Marketing Cloud Next, or want to structure your marketing data the right way? Get in touch with CGC-Agency for expert guidance on Salesforce Marketing Cloud.