Known Issues · Marketing Cloud Integrations
Marketing Cloud Connect Triggered Sends and Journey Builder Sends that opt to send tracking to Sales Cloud create triggered sends within Sales Cloud. The current logic to push the Individual Email Results (IERs) related to these triggered sends to Sales Cloud is not always accurate. This can cause IERs...
In Review ·Reported By 148 ·Updated 2 days ago
When Journeys with email activities are activated in the Marketing Cloud that use your Salesforce Data, a corresponding Triggered Send is created in Salesforce. If your user's default Business Unit is different than that of the location of the Journey/Triggered Send, the Marketing Cloud Connect package...
In Review ·Reported By 19 ·Updated Yesterday
When using SalesforceObjectID output from a Sales Cloud Activity in a JourneyBuilder decision split, all the contacts get sent down the same path even though they should be split.
In Review ·Reported By 6 ·Updated Today
When using the Marketing Cloud Connector between Einstein Analytics and the Marketing Cloud, a time out can occur when you attempt to select your Connection to the Marketing Cloud.
In Review ·Reported By 3 ·Updated 2 days ago
When viewing tracking data for an integrated send in Salesforce, unique clicks or unique opens show a higher value than what is seen under tracking for the job in the Marketing Cloud.
In Review ·Reported By 5 ·Updated 8 days ago
Platform Events Apex Jobs run before update transactions are complete, causing records to come into the journey data extension with incorrect (pre-update) values. This is because the apex job created by the platform events is running before the transaction that triggered it is completed and the updates...
In Review ·Reported By 38 ·Updated 9 days ago
Customers may experience a condition in which their Salesforce Data Event will not fire if another process is updating the object that meets the condition to make the JB Process Builder trigger.
In Review ·Reported By 45 ·Updated 13 days ago
Sales Cloud Activities will currently use the shortest available path to an object within Contact Builder. If you have a Data Extension linked twice through two different sets of objects, it will always default to the shortest path. If there are multiple shortest paths, one will be arbitrarily chosen...
In Review ·Reported By 1 ·Updated 13 days ago
Salesforce Triggered Sends with subsequent rule can prevent evaluation of subsequent triggered sends.
In Review ·Reported By 0 ·Updated 25 days ago
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.