* Marketing Cloud Engagement *

Hi Hello  

In addition to our current contract for Marketing Cloud Engagement, we have decided to add Marketing Cloud Engagement+ to our contract. 

The main purpose of this additional contract is to utilize AI to build segments using natural language, such as specifying conditions with generative AI. 

In order to establish this operation, we would like to organize the future data design and processing flow. From an architectural perspective, could you please advise us on the following three points regarding what preparations and tasks will be required based on our current configuration? 

Questions

1. Data management location  
   Currently, the customer data used for message delivery is managed on the Marketing Cloud (MC) side. In order to use AI-powered natural language segmentation, is it necessary to migrate or consolidate this data into Data Cloud (DC)? Or is it acceptable to continue managing the data in MC as it is now?

2. Environment for creating AI segments  
   Specifically, in which environment or screen will AI-powered natural language segment creation be performed: MC or DC?

3. Environment for executing message delivery  
   When using the extracted and segmented data, will the actual message delivery, such as email or LINE, be executed from MC? Or will it be triggered directly from DC?

Thank you for your support.

Hi Team,   I’m currently working on a BU migration from One SFMC Org Source BU to Targeted SFMC Org BU  both are different Orgs and running into an issue with Managed Package deployment. I’d appreciate any guidance or insights.

Current Setup:

The Source BU contains Synchronized Data Extensions, which are inherited from the parent BU .When I create a Managed Package from the Source BU, these synchronized Data Extensions are automatically included.   In the package, they appear as Shared Data Extensions.  "In the Journeys , I used goals that tied to contact data"

Issue:

The package creation is successful.   However, during deployment to the Targeted BU, I encounter an error (likely related to these synchronized/shared DEs being included in the package).

Question:

Is it expected behavior for synchronized DEs to be included in Managed Packages as shared DEs?   What is the recommended approach to exclude or handle synchronized Data Extensions during packaging?   Has anyone successfully migrated a child BU with synchronized DEs to a different Org target BU? If so, what approach did you follow?   Is there a best practice for handling Synchronized Data Extensions when consolidating BUs into a new structure?

My Initial Thoughts:

Since synchronized DEs are system-generated and tied to the parent BU's data source, I believe they should not be part of the package.   I suspect I may need to exclude them manually or rebuild them in the target BU, but I’m not sure of the correct approach.

Any recommendations, best practices, or similar experiences would be very helpful.   Thanks in advance!

If you want, I can also give you the actual fix/approach (not just the forum question), since this is a known limitation with synchronized DEs in Marketing Cloud.     

📣 T-minus Connections. The moment we have been waiting for is almost here 📣

The sessions are locked 🔐 

The speakers are ready 👊  

The content is fire 🔥  

The surprise & delights are chef's kiss 🤌 

Start building your agenda and get ready for an unforgettable time. 🌟 

📍Day 1 — Community Theater

9:00 AM Ramatu Kandakai, MBA — Prompt Like a Marketer: Stop Sounding Like Everyone Else

9:30 AM Matt Brulet, MBA & Tim Ziter — Design RCS Messaging: Visuals & Carousels in Journey Builder

11:30 AM Jacob Hayes — What Actually Powers Next Best Action

12:00 PM Anne Tomlin — Fragile to Flexible: Easy-to-Edit Emails, No Custom Modules

12:30 PM Cole Fisher & Julie Marques — How to Master Data 360 — Free Up 8 Hours Per Week

1:00 PM Alec Perea-Martinez — Great Campaigns Are Felt, Not Just Seen

1:30 PM Logan Sandrock Baird — Design Principles That Drive Effective Email

2:00 PM Karmel N. James & Najee Henderson — Everything for Everyone: Accessible Marketing at Scale

2:30 PM Kenny Van Beeck — Stop Blasting and Start Personalizing

3:00 PM Abby McCune & Hannah Jones — Tips and Tricks About Agentforce Marketing

3:30 PM Anna K. & Timothy Kauble — What AI Is Doing to the Email Inbox

4:00 PM Rodrigo Santander — Accessible Template for Every Inbox Client

4:30 PM Whitney Stout — Build a Foundation That Makes AI Work for You

📍Day 1 — Networking Space 

9:00 AM Najee Henderson — Meetup: New to Connections? First time here? This is your starting point. Get oriented, meet your people, and leave with a game plan.

11:30 AM Myra Wilson, MBA — Steal Their Playbook: Strategy, Story, Scale

12:30 PM Christina Garnett & Goldie Chan — Personal Branding: Using Trust to Future-Proof Your Career

1:30 PM Alexandra Danahy, Ali Saeed, Ben LaMothe & Margaux Malyshev — The Best Career Move They Ever Made

2:30 PM Amanda Turner, Genna Matson, Gregory Gifford & Mounir Nejjai — Unfiltered: Developers on the Future of Email

3:30 PM Tasha Rucker, MBA, PSM™ — Ace Your Agentforce Marketing Exams

📍Day 2 — Community Theater

9:30 AM Claudia Hoops ☁️ & François Perret — Master Segmentations in Agentforce Marketing

10:00 AM Kyle Montgomery & Shane Smyth — Beyond the Prototype: Agents Engineered for Human Needs 

10:30 AM Laurel Cummings & Sonia Hildner — Make 'Em Laugh: How Humor Drives Revenue 

11:00 AM Erin Duncan & François Perret — Agentforce Marketing Flow Fundamentals

11:30 AM Pato Sapir ☁️ & Rahmaan Lodhia — The Future of AMPscript

12:00 PM Amanda Turner & Genna Matson — The Science Behind Email

12:30 PM Jay Oram — Accessible by Design: Email for Every Inbox, Everyone

1:00 PM Anne Tomlin — Yes, You Can Do That in Email

1:30 PM Eli Hougland — Two-Way Marketing Is Here. Now What?

2:00 PM Justin Piehowski — Great Metrics Don't Speak for Themselves

2:30 PM Anne Tomlin, Jay Oram & Logan Sandrock Baird — Fix My Email: Live Optimization (The first ever live email optimization session at Connections. Bring your campaigns. Get real feedback. Walk away with real fixes.)

📍Day 2 — Networking Space

9:30 AM Leia S. — How Women in Tech Are Using AI to Work Smarter

10:30 AM Angelia Sterling, Kyle Montgomery, Shane Smyth & Rebecca Simmons, Jenny MacDonald — Meetup: Commerce Community

11:30 AM Salesforce Product Leaders — Fireside Chat: Agentforce Marketing Roadmap Fresh off the Marketing Keynote, get your questions answered directly by the product team.

12:30 PM Ali Saeed, Chris Zullo & Pato Sapir ☁️ — Your Move: Real Marketing Decisions

1:30 PM Anne Tomlin, Jay Oram & Logan Sandrock Baird — Meetup: Email Geeks Whether you live in code, design, or strategy, this one is for you.

@* Marketing Cloud Engagement * @* MC Account Engagement (fka Pardot) * @Marketer Group, Indianapolis, US, @Marketer Group, Philadelphia, US, @Marketer Group, Twin Cities, US, @Marketer Group, Madrid, ES, @Marketer Group, Denver, US, @Marketer Group, Toronto, CA, @Marketer Group, Cleveland, US, @Marketer Group, Atlanta, US, @Marketer Group, Austin, US, @Marketer Group, Boston, US @Commerce Trailblazers @* B2C Commerce * @B2C Commerce Developers

*** Important change for:  Update Permissions for TriggeredSend SOAP API by June 19, 2026 ***On June 19, 2026, Salesforce is changing the permission requirements for executing TriggeredSend SOAP API calls within Marketing Cloud Engagement.  

Required Actions

Beginning on June 19, only API users and installed packages that have the required permissions can make TriggeredSend calls via the SOAP API. Depending on your authentication method, update your permissions using these steps.

Installed Package

1. From Setup, in the Quick Find box,enter Installed Packages, and then select Installed Packages.
2. Select the package to modify.
3. In the Components section, click Edit for your integration.
4. In the Channels section, under Email, select Read, Write, and Send.
5. Save your changes.

Username and Password

This step applies only to users with the API User setting enabled. If a user doesn’t have this setting enabled or doesn’t perform triggered email sends, no action is required.

1. From Setup, in the Quick Find box, enter Users, and then select Users.
2. Select a user, and then click Manage Roles.
3. Select Edit Permissions.
4. In the Email | Interactions | Messages | Email section, next to Triggered, select Allow.
5. Save your changes.

Follow the step-by-step instructions in the Knowledge Article to update permissions for packages and API users.

Impact of Noncompliance

If you don't update the permissions by June 19, 2026, your TriggeredSend SOAP API calls will not send emails and return an API Permission Failed error.

Why Are We Making This Change?

To provide a more predictable and streamlined operational environment, Salesforce is aligning the permission requirements for TriggeredSend SOAP API calls used throughout Marketing Cloud Engagement. This change extends the same access controls from our other messaging features to your integrations.

What to Expect

After you update your permissions, your TriggeredSend SOAP API calls continue to function with no impact on the email delivery experience for your recipients.

To ensure uninterrupted service, update your integration permissions by June 19, 2026.

Need help?

Connect with Agentforce on Salesforce Help.

#Marketing Cloud