u/Film-Frosty

Hi everyone,

Today, we trigger transactional appointment-booking emails from Marketing Cloud Engagement using API Events / extensions.
We’re now planning to move to Marketing Cloud Advanced / Marketing Cloud Next, and we want to build and manage the transactional emails directly in Marketing Cloud Core.

Our use case is:

● An external booking application creates or updates an appointment.
● This needs to trigger a transactional email immediately.
● The email template/content should be built and managed in Marketing Cloud Core.
● The booking application needs to pass dynamic appointment/customer data to the email.
● We don’t want to continue relying on Marketing Cloud Engagement API Events/extensions.

What is the recommended architecture for this in Marketing Cloud Core / Marketing Cloud Next?
Specifically:

What is the best replacement for API Events when the email itself is built in Marketing Cloud Core?

Is the recommended approach something like:
External system → Salesforce API / Platform Event → Flow → transactional email
Or is there a specific transactional messaging capability in Marketing Cloud Core / Next that we should be using instead?

If anyone has implemented appointment confirmations/reminders this way, I’d especially appreciate real-world feedback on the architecture, API capabilities, latency, and limitations.
Thanks!

With the new CNIL recommendation on email tracking pixels, we’re looking at disabling open tracking for some recipients in Salesforce Marketing Cloud.

Has anyone implemented this in SFMC?

Specifically, I’m trying to understand the best technical approach to disable the open tracking pixel while still sending the email normally.

Is there an officially supported way to disable the open tracking pixel?

Does anyone have experience with the <custom name="opencounter" type="tracking" /> tag? Can it be used to disable open tracking?

I’d appreciate any feedback from anyone who has already tackled this, especially in the context of the new CNIL requirements.

Thanks!

Hi everyone,

I’m currently working as a Salesforce Marketing Cloud Administrator, and my company wants me to expand my role by taking on Salesforce Marketing Cloud Engagement.

I’m looking to build my skills and become confident with the platform, especially Journey Builder, Automation Studio, Email Studio, Contact Builder, SQL, AMPscript, Data Extensions, and best practices.

For those who work with Marketing Cloud Engagement:
Which Trailhead modules or Trailmixes would you recommend?

Are there any blogs, YouTube channels, documentation, or courses that were particularly helpful?

If you had to learn Marketing Cloud Engagement from scratch today, what learning path would you follow?

I’d love to hear your recommendations and any tips that helped you become proficient.

Thanks in advance!

We currently use Business Accounts in Salesforce, and there are ongoing discussions internally about enabling Person Accounts as we consider future requirements involving individual customers.
At the moment, we’re not particularly enthusiastic about introducing Person Accounts, mainly because our existing data model is stable and well-established.
For those who have gone through a similar discussion, what arguments did you use either for or against Person Accounts?

More specifically:

What drawbacks or limitations have you encountered with Person Accounts?

Have they introduced complexity in integrations, reporting, automation, or data management?

If you decided not to adopt Person Accounts, what were your main reasons?

I’d be interested in hearing real-world experiences, especially from teams that were using standard Business Accounts and later had to decide whether or not to adopt Person Accounts.

What business problem did Person Accounts actually solve for you that couldn’t reasonably be solved with Accounts + Contacts?

Thanks!

Hi everyone,

I have a question regarding Person Accounts.

If I enable Person Accounts in a Salesforce Development environment (sandbox/dev org), could this have any impact on other environments?

My understanding is that Person Accounts are enabled at the org level, but I would like to confirm whether activating them in a development environment is completely isolated or if there are any downstream impacts I should be aware of.

Has anyone gone through this process before? Any caveats or best practices?

Thanks!

Hi everyone,

I’m looking for clarification regarding Salesforce’s upcoming Phishing-Resistant MFA Enforcement.

We have a Salesforce Marketing Cloud Connect integration user in Salesforce. The user currently has a System Administrator profile along with the permissions required for Marketing Cloud Connect.

My question is: will this user be impacted by the Phishing-Resistant MFA Enforcement update?

The account is primarily used by the integration, but it is not configured as a dedicated API-only Integration User (it still has UI access through the System Administrator profile).

Has anyone received guidance from Salesforce on whether Marketing Cloud Connect users with UI access must comply with the new phishing-resistant MFA requirements, or if they are treated differently because they’re used for integration purposes?

Thanks in advance for any insights.