How Education Cloud Works With Data 360, Commerce, and Marketing on Core

When Education Cloud, Data 360, Commerce on Core, and Marketing Cloud Next run in one Salesforce org, a learner exists once. The storefront order becomes an enrollment through Flow, Data 360 joins the marketing, commerce, and academic records into one profile, and marketing uses those segments where they sit. ElevateActual builds this pattern for continuing and executive education.

What Does a Connected Learner Mean on Salesforce?

A connected learner is one person who appears once across marketing, registration, and the academic record. The email they open, the program they buy, the cohort they attend, and the certificate they earn all point at the same profile. Staff stop reconciling three versions of the same person.

Four Salesforce products do the work. Education Cloud (Agentforce Education) holds programs, enrollments, and completion. Commerce on Core sells the program. Data 360, the product Salesforce called Data Cloud until October 2025, joins every source into one profile and builds segments. Marketing Cloud Next talks to the learner. The difference this article is about is where those four run: in one org, on one data layer.

If you would rather click through it than read it, the Connected Learner walkthrough follows one fictional learner through all ten steps, with the data that moves at each one.

Why Did Four Products Used to Mean Four Integrations?

The symptom is familiar to anyone who has run a continuing education unit. Marketing has a subscriber list that is a few days behind. The registration system has its own customer table with the learner's work email. The CRM has the personal email from an inquiry form. Someone exports a spreadsheet every week to find people who finished one program and might buy the next.

The root cause was architectural. Marketing ran in a separate Marketing Cloud Engagement account, connected to the core org with Marketing Cloud Connect, so contacts were copied and kept in step by synchronization. Registration often ran on a different stack entirely. Each copy drifted, and every audience that needed academic and purchase data at once became a manual export.

The fix is not a better sync. It is removing the copies. On core, the storefront, the learner record, the unified profile, and the marketing flows read the same records in the same org.

What Changes When All Four Run on Core?

Each connection between products either disappears or becomes a feature of the platform. The table below lists the hops we design for on continuing and professional education storefronts.

How Does Education Cloud Feed Data 360?

Education Cloud holds the academic side on standard objects: LearningProgram for the program, CourseOffering for a specific cohort or section, LearnerProgram for a person in a program, and CourseOfferingParticipant for a seat in an offering. Status and completion live on those records. Continuing education programs and certificates use the same objects as degree programs.

Those records reach Data 360 through the CRM data stream from the same org and map to the Data 360 data model. Salesforce documents the setup as Data 360 for Education. Once they are there, completion becomes something a segment can use: "completed this program and has not bought the next one" is a query, not a spreadsheet.

The general rule: the quality of every segment you build later depends on whether enrollment and completion were recorded on standard Education Cloud objects in the first place. We keep custom objects out of this path for that reason, and write down the reason for any we add.

What Does Commerce on Core Add?

Commerce on Core is our term for B2B or D2C Salesforce Commerce running on the Salesforce Platform, with an LWR Experience Cloud storefront, in the same org as Education Cloud. Salesforce sells it in Growth and Advanced editions. According to Salesforce's published edition comparison, the Advanced edition includes full Order Management and adds Data 360 personalization for commerce.

The architectural point is that a purchase is an ordinary Salesforce record. Checkout creates an Order and an Order Summary. The buyer is an Account or a Person Account the rest of the institution already shares. A record-triggered Flow on the order can create the LearnerProgram and CourseOfferingParticipant records the moment the order is saved, with no integration and no import job. Team purchases work the same way: an employer buys three seats in one cart, and three enrollments appear under the employer's account.

That is the core of our Commerce Accelerator: storefront, checkout, and learner-record automation, live in about two months.

What Does Marketing Cloud Next Do With the Profile?

Marketing Cloud Next is Salesforce's marketing product on core, built on Data 360, and sold in Growth and Advanced editions. It does not keep a separate subscriber database. It reads segments and profile attributes from Data 360 and writes engagement back to it.

Two kinds of flow matter for learner marketing, as described in Salesforce's Marketing Cloud Next Trailhead module:

• Segment-triggered flows run for the members of a published Data 360 segment, when the segment is activated or on a schedule. This is how a "completed Business Fundamentals, no AI course yet" audience gets the next-best offer.
• Event-triggered flows start when a person does something, such as clicking an email or a CRM record changing. This is how a click on a program email branches to a team offer.

Flows can pull attributes from the Data 360 data graph, such as the program a learner completed, to personalize the message. The Advanced edition adds Path Experiments, which test up to ten variations inside a flow and pick a winner from engagement.

The rule that keeps this honest: when a segment refreshes, people who stop qualifying stop receiving the flow. A learner who buys the AI course leaves the "no AI course yet" segment, so the offer stops. On separate systems that exit usually depends on someone remembering to suppress a list.

What Happens to One Learner End to End?

1. A segment-triggered flow sends an engineer a program email. The audience comes from contacts the university already holds.
2. He clicks, browses the program page and an AI certificate page, and the flow branches to a team offer.
3. He registers himself and two colleagues in one cart. A promotion makes the third seat free, and the employer is the buyer account.
4. Checkout creates the order, and a Flow creates three LearnerProgram and three CourseOfferingParticipant records.
5. He completes the program, and the status is recorded on his learner record.
6. Data 360 matches his personal email, work email, web visits, and Education Cloud contact into one profile.
7. A segment finds completers with no AI course who viewed an AI page. He qualifies.
8. A next-best-offer flow sends the AI certificate. He buys it, a new enrollment is created, and he leaves the segment.

The interactive version shows each step with the records involved and the direction the data moves. For a working storefront, see it live on ElevateActual University, our demonstration institution.

What Should You Decide Before Building?

Most of the effort in a connected learner build is decisions, not configuration. These are the ones we ask institutions to settle first.

• Which identity wins. Learners use personal and work emails. Decide which identifiers the Data 360 match rules use and which email marketing should send to.
• Who the buyer is. Individual learners as Person Accounts, employers as business accounts, or both. This drives cart, checkout, and reporting.
• Where enrollment is created. On the order, at payment, or after an approval step. The Flow trigger follows from it.
• Which segments matter. Write the three audiences you wish you had today. They tell you which fields must be on standard objects from day one.
• Consent. Agree what a purchase does to marketing preferences before the first email goes out.

The same pattern applies beyond continuing education: admissions uses it for inquiry to enrollment, and advancement uses it for giving. The products change slightly. The rule does not: keep one record, and let each product read it where it is.

Questions We Hear