![\"Por](\"https:\/\/www.marketinet.com\/wp-content\/uploads\/2024\/06\/blog\/marketing-cloud\/MarketiNet-registros-Salesforce-640x450.jpg\")
<\/span><\/p>\n\u00a0<\/p>\n
Possible circumstances that generate this problem<\/span><\/span><\/h2>\n\u00a0<\/p>\n
Below, we list them:<\/p>\n
\u00a0<\/p>\n
What version of Marketing Cloud Connect is being used?<\/h3>\n
\u00a0<\/p>\n
To connect both platforms, an official Salesforce<\/a> package from the appExchange is used. The most effective way to avoid known problems is to stay up to date with the most recent version of the Installed Package. To check your version, click on \u2018Setup\u2019 in Sales Cloud and then go to Installed Packages. The package is identified as \u2018Marketing Cloud\u2019. Check that you are using the latest version and, if not, update it.<\/p>\n\u00a0<\/p>\n
![\"Por](\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\")
<\/span><\/span><\/span><\/p>\nDoes my Marketing Cloud API user have access to the Object\/Records that are being updated\/created?<\/h3>\n
\u00a0<\/p>\n
Since the Marketing Cloud<\/a> API user is used to maintain the integration between Sales Cloud and Marketing Cloud, this user must have access to any record that is intended to be injected into Journey Builder through the integration.<\/p>\nThis is achieved by integrating the Marketing Cloud API user with a Salesforce User (usually, the dedicated Salesforce System User who has the appropriate permissions for each object).<\/p>\n
The easiest way to have widespread access and avoid this type of incident is to use a system administrator profile for this User.<\/p>\n
Make sure that the specific OAuth endpoints of the \u2018tenant\u2019 are enabled in your Salesforce organization<\/p>\n
For more details, see Enable specific O Auth endpoints for Marketing Cloud Connect<\/a>.<\/p>\nCan records be injected under the simplest Entry Criteria, without applying Related Object Criteria?<\/h3>\n
In some cases, the Entry Criteria may be too restrictive or include two filters that contradict each other. For example, if the Primary Object is set as Lead and the Entry Criteria is set to inject once \u2018Lead:Status\u2019 is updated to [\u2018Pending\u2019 AND \u2018Closed\u2019], these two criteria would not allow the injection of records. Since the \u2018Status\u2019 of a Lead can only be one or the other, if you replace the AND with an OR operator, you will increase the chances of a successful injection.<\/p>\n
If the Criteria required for your live deployment are robust and include many filters, but the injection has not been carried out after updating or creating a record, try to remove all Criteria except one. Once the injection is successful through the single filter, gradually work towards a more complex filter. This practice will explicitly identify problematic filters.<\/p>\n
If the volume of records to be generated is not very large, a simple option is to put very few filtering criteria, and then use a SQL QUERY to filter and re-inject into Journey Builder<\/a> the records for management, i.e., make a journey so that simply enter the data (you can put as action a simple random Split so that it accepts you to save the journey) and then inject into another journey through a SQL query that filters the data.<\/p>\n\u00a0<\/p>\n
Is the \u2018Update\/Create\u2019 action completed through a form submission or a separate process?<\/h3>\n
Verify that the \u2018Update\/Create\u2019 record contains the required data to satisfy the Entry Criteria after the process has been completed.<\/p>\n
In some cases, the separate process will update\/create a record with only a part of the requires data, and an additional process is needed to complete the record.<\/p>\n
\u00a0<\/p>\n
Example of setting up a Salesforce Data Entry and its possible issues:<\/h3>\n
\u00a0<\/p>\n
\n- \n
Object we are going to use:<\/strong> Opportunity<\/p>\n<\/li>\n<\/ul>\n\n- \n
Who:<\/strong> LeadID (Lead)<\/p>\n<\/li>\n<\/ul>\n\n- \n
Action: <\/strong>Updated<\/p>\n<\/li>\n<\/ul>\n\n- \n
Criteria:<\/strong> ‘Opportunity:Lead:Name’ equals ‘Thomas’ AND (‘Opportunity:Status’ equals ‘Won’ or ‘Opportunity:Status’ equals ‘Pending’)<\/p>\n<\/li>\n<\/ul>\n\u00a0<\/p>\n
The \u2018Update\u2019 action type only injects records that meet the Entry Criteria once evaluated.<\/p>\n
\u00a0<\/p>\n
We create an Opportunity linked to a Lead for Thomas Cook, with Status = \u2018Pending\u2019. This does not trigger the injection because the \u2018Action\u2019 is set to Update and created records are not evaluated.<\/p>\n
\u00a0<\/p>\n
Later, we update the Opportunity for Thomas Cook, setting the Status to \u2018Won\u2019. This also does not trigger the injection because the record already met the criteria before the update, and only records that meet the criteria in a new way are injected by the \u2018Update\u2019 action type.<\/p>\n
\u00a0<\/p>\n
Continuing with the same Entry Event configuration and our Lead, Thomas Cook.<\/p>\n
\u00a0<\/p>\n
In this scenario, we want Thomas to be injected into our Journey twice. Once when his Opportunity Status is \u2018Pending\u2019 and then, a second time, when it is updated to \u2018Won\u2019.<\/p>\n
\u00a0<\/p>\n
We create an Opportunity for Thomas and the status is \u2018On-hold\u2019. This does not trigger the injection. A few days pass and now the Opportunity record is updated to \u2018Pending\u2019. Thomas is now injected into the Journey. Our team continues working on winning the Opportunity and they eventually succeed.<\/p>\n
\u00a0<\/p>\n
The Opportunity Status now changes to \u2018Won\u2019. The injection does not take place. Our crucial requirement for \u2018Update\u2019 to trigger the injection is that the record did not have the entry criteria and then it does, and this did not happen. Our Opportunity had a ‘Status of \u2018Pending\u2019 and then it was updated to \u2018Won\u2019. Both are valid entry criteria, so the system does not register this as an update.<\/p>\n
\u00a0<\/p>\n
Within the Entry Criteria, each filter component can be considered grouped into a single filter. Sending a record against this filter returns a 1 (true) or 0 (false). If the record meets, a 1 is sent. If the record is updated so that it continues to meet, a 1 is sent. For the update to satisfy the Entry Criteria Action of \u2018Update\u2019, a 0 must be passed between each 1.<\/span><\/p>\n\u00a0<\/p>\n
If you need these updates to result in multiple injections, you could create two Journeys, one for the Opportunity Status \u2018Won\u2019 and a second for the Opportunity Status \u2018Pending\u2019.<\/p>\n
\u00a0<\/p>\n
Solve the problems of record entry in Journey Builder from Salesforce Cloud<\/h2>\n
\u00a0<\/p>\n
We hope all these clues help you identify any issues with including records in your Journey and get the most out of your Marketing Cloud<\/a>.<\/p>\n\u00a0<\/p>\n
\u00a0<\/p>\n
\u00a0<\/p>\n
\u00a0<\/p>\n Since the Marketing Cloud<\/a> API user is used to maintain the integration between Sales Cloud and Marketing Cloud, this user must have access to any record that is intended to be injected into Journey Builder through the integration.<\/p>\n This is achieved by integrating the Marketing Cloud API user with a Salesforce User (usually, the dedicated Salesforce System User who has the appropriate permissions for each object).<\/p>\n The easiest way to have widespread access and avoid this type of incident is to use a system administrator profile for this User.<\/p>\n Make sure that the specific OAuth endpoints of the \u2018tenant\u2019 are enabled in your Salesforce organization<\/p>\n For more details, see Enable specific O Auth endpoints for Marketing Cloud Connect<\/a>.<\/p>\n In some cases, the Entry Criteria may be too restrictive or include two filters that contradict each other. For example, if the Primary Object is set as Lead and the Entry Criteria is set to inject once \u2018Lead:Status\u2019 is updated to [\u2018Pending\u2019 AND \u2018Closed\u2019], these two criteria would not allow the injection of records. Since the \u2018Status\u2019 of a Lead can only be one or the other, if you replace the AND with an OR operator, you will increase the chances of a successful injection.<\/p>\n If the Criteria required for your live deployment are robust and include many filters, but the injection has not been carried out after updating or creating a record, try to remove all Criteria except one. Once the injection is successful through the single filter, gradually work towards a more complex filter. This practice will explicitly identify problematic filters.<\/p>\n If the volume of records to be generated is not very large, a simple option is to put very few filtering criteria, and then use a SQL QUERY to filter and re-inject into Journey Builder<\/a> the records for management, i.e., make a journey so that simply enter the data (you can put as action a simple random Split so that it accepts you to save the journey) and then inject into another journey through a SQL query that filters the data.<\/p>\n \u00a0<\/p>\n Verify that the \u2018Update\/Create\u2019 record contains the required data to satisfy the Entry Criteria after the process has been completed.<\/p>\n In some cases, the separate process will update\/create a record with only a part of the requires data, and an additional process is needed to complete the record.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n Object we are going to use:<\/strong> Opportunity<\/p>\n<\/li>\n<\/ul>\n Who:<\/strong> LeadID (Lead)<\/p>\n<\/li>\n<\/ul>\n Action: <\/strong>Updated<\/p>\n<\/li>\n<\/ul>\n Criteria:<\/strong> ‘Opportunity:Lead:Name’ equals ‘Thomas’ AND (‘Opportunity:Status’ equals ‘Won’ or ‘Opportunity:Status’ equals ‘Pending’)<\/p>\n<\/li>\n<\/ul>\n \u00a0<\/p>\n The \u2018Update\u2019 action type only injects records that meet the Entry Criteria once evaluated.<\/p>\n \u00a0<\/p>\n We create an Opportunity linked to a Lead for Thomas Cook, with Status = \u2018Pending\u2019. This does not trigger the injection because the \u2018Action\u2019 is set to Update and created records are not evaluated.<\/p>\n \u00a0<\/p>\n Later, we update the Opportunity for Thomas Cook, setting the Status to \u2018Won\u2019. This also does not trigger the injection because the record already met the criteria before the update, and only records that meet the criteria in a new way are injected by the \u2018Update\u2019 action type.<\/p>\n \u00a0<\/p>\n Continuing with the same Entry Event configuration and our Lead, Thomas Cook.<\/p>\n \u00a0<\/p>\n In this scenario, we want Thomas to be injected into our Journey twice. Once when his Opportunity Status is \u2018Pending\u2019 and then, a second time, when it is updated to \u2018Won\u2019.<\/p>\n \u00a0<\/p>\n We create an Opportunity for Thomas and the status is \u2018On-hold\u2019. This does not trigger the injection. A few days pass and now the Opportunity record is updated to \u2018Pending\u2019. Thomas is now injected into the Journey. Our team continues working on winning the Opportunity and they eventually succeed.<\/p>\n \u00a0<\/p>\n The Opportunity Status now changes to \u2018Won\u2019. The injection does not take place. Our crucial requirement for \u2018Update\u2019 to trigger the injection is that the record did not have the entry criteria and then it does, and this did not happen. Our Opportunity had a ‘Status of \u2018Pending\u2019 and then it was updated to \u2018Won\u2019. Both are valid entry criteria, so the system does not register this as an update.<\/p>\n \u00a0<\/p>\n Within the Entry Criteria, each filter component can be considered grouped into a single filter. Sending a record against this filter returns a 1 (true) or 0 (false). If the record meets, a 1 is sent. If the record is updated so that it continues to meet, a 1 is sent. For the update to satisfy the Entry Criteria Action of \u2018Update\u2019, a 0 must be passed between each 1.<\/span><\/p>\n \u00a0<\/p>\n If you need these updates to result in multiple injections, you could create two Journeys, one for the Opportunity Status \u2018Won\u2019 and a second for the Opportunity Status \u2018Pending\u2019.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n We hope all these clues help you identify any issues with including records in your Journey and get the most out of your Marketing Cloud<\/a>.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n![\"Por](\"https:\/\/www.marketinet.com\/wp-content\/uploads\/2024\/06\/undefined-May-06-2024-09-49-29-1046-AM.png\")
<\/span><\/span><\/span><\/p>\nDoes my Marketing Cloud API user have access to the Object\/Records that are being updated\/created?<\/h3>\n
Can records be injected under the simplest Entry Criteria, without applying Related Object Criteria?<\/h3>\n
Is the \u2018Update\/Create\u2019 action completed through a form submission or a separate process?<\/h3>\n
Example of setting up a Salesforce Data Entry and its possible issues:<\/h3>\n
\n
\n
\n
\n
Solve the problems of record entry in Journey Builder from Salesforce Cloud<\/h2>\n
![\"eBook](\"https:\/\/www.marketinet.com\/wp-content\/uploads\/2024\/01\/800x200_banner_ebook.jpg\")
<\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"