#Marketing Cloud98 discussing

Good afternoon everyone, hope you’re all doing well. I would like to ask a question and better understand how I can enable PUSH notifications in my SDO Demo (Marketing Cloud Next). To be honest, I have not been able to find real use cases or documentation regarding Push usage in Marketing Cloud Next, which made me quite curious to know whether this capability is already available or if it is still planned for a future release.  

However, during one of the public meetings with Salesforce, it was mentioned that in order to have Push available in the SDO environment, a specific SKU would be required, and it may not currently be enabled in my environment. How can I resolve this or activate it so I can test it in my SDO environment?  

Thank you very much!  

*** 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

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.     

I am trying to track the open rate of Salesforce Marketing Cloud push notifications on Android

, but the open events are not being reflected. 

SDK 8.x

Below are the steps I have already implemented:

• The SFMC SDK is initialized with analytics enabled.
• In setNotificationCustomizationOptions, I wrapped my PendingIntent using the SDK’s analytics helper method   
   NotificationManager.redirectForAnalytics(), following the official documentation:   
   
  https://developer.salesforce.com/docs/marketing/mobile-messaging-sdks/guide/customize-push-notifications-android.html#full-control-customization

Below are the logs captured from the Android terminal when the push notification is received:

D/FLTFireMsgReceiver(14789): broadcast received for messageD/SessionLifecycleClient(14789): Sending lifecycle 2 to serviceD/SessionLifecycleService(14789): Activity backgrounding at 83267027D/com.llfbandit.app_links(14789): Intent { act=SELECT_NOTIFICATION cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=xxxx.co.xxx.xxx cmp=xxx.co.xxx.xxx/.MainActivity (has extras) }D/SessionLifecycleClient(14789): Sending lifecycle 1 to serviceD/SessionLifecycleService(14789): Activity foregrounding at 83267041.I/TrafficStats(14789): tagSocketFd(-1, 11122887, -1) failed with errno-9D/SessionLifecycleClient(14789): Sending lifecycle 2 to serviceD/SessionLifecycleService(14789): Activity backgrounding at 83311622D/VRI[MainActivity](14789): visibilityChanged oldVisibility=true newVisibility=falseD/BLASTBufferQueue(14789): [SurfaceView[jp.co.xxx.xxx/jp.co.xxx.xxx.MainActivity]#1](f:0,a:1) destructor()D/BufferQueueConsumer(14789): [SurfaceView[jp.co.xxx.xxx/jp.co.xxx.xxx.MainActivity]#1(BLAST Consumer)1](id:39c500000001,api:0,p:-1,c:14789) disconnectD/BLASTBufferQueue(14789): [VRI[MainActivity]#0](f:0,a:1) destructor()D/BufferQueueConsumer(14789): [VRI[MainActivity]#0(BLAST Consumer)0](id:39c500000000,api:0,p:-1,c:14789) disconnectW/DynamiteModule(14789): Local module descriptor class for com.google.android.gms.providerinstaller.dynamite not found.I/DynamiteModule(14789): Considering local module com.google.android.gms.providerinstaller.dynamite:0 and remote module com.google.android.gms.providerinstaller.dynamite:0W/ProviderInstaller(14789): Failed to load providerinstaller module: No acceptable module com.google.android.gms.providerinstaller.dynamite found. Local version is 0 and remote version is 0.W/ProviderInstaller(14789): Failed to report request stats: com.google.android.gms.common.security.ProviderInstallerImpl.reportRequestStats [class android.content.Context, long, long]I/FA      (14789): Application backgrounded at: timestamp_millis: 1768551560481D/SessionLifecycleClient(14789): Sending lifecycle 1 to serviceD/SessionLifecycleService(14789): Activity foregrounding at 83315818.

However, even after waiting for more than 30 minutes, the open rate has not been updated in Marketing Cloud.

Has anyone experienced a similar issue, or is there anything else I should check to ensure push open tracking works correctly on Android?

Any advice would be greatly appreciated. Thank you.