There is no standard approach/activity to do so. Standard functionality only allows you to do it the opposite way and trigger a journey from an automation.
However there is the possibility to create custom journey builder activities. Furthermore Marketing Cloud provides APIs that let you interact with automations and also start one immediately. If you ...
Yes, the most simple way is to use a Random Split.
After you randomly split the contacts, you can define the Email Activity and use the same email with different subject lines, or add a Wait activity to send it at different times.
The downside of this is that you will have to figure out a way to create reporting, which won't be as easily displayed as the ...
Here’s an example of a very generic query, that will pull all the tracking data from Data Views into one table. All you need to do is create a Data Extension with the following fields:
info@ and mail@ are called "Role-based emails".
Because role-based and reserved email addresses often represent multiple recipients, they generate many spam complaints. To prevent unnecessary spam complaints, List Detective restricts these email addresses on imports and doesn’t send email to reserved email addresses.
You can use Custom List Detective to ...
Salesforce Marketing Cloud has a default setting that prevents the sending of emails to "generic addresses", such as admin@, info@ and so on.
This is likely the reason why these addresses have failed to enter the Journey.
Reference: List Detective
This is expected behavior. When you inject a contact into a journey they are established within the contact model (All Contacts) even though they are not yet been sent an email and added to All Subscribers. When you then use the create lead activity, the Marketing Cloud then stores the lookup between the contactkey and the LeadID within the alternate key ...
As I've suggested in the comments, sometimes Journey Builder shows this error randomly. In most cases, I had to remove and select back the entry source, save and then refresh the page. That solved the problem for me in most cases.
,max(DATEADD(hh,1,[Task:SMS_Scheduled_at__c])) AS 'Task:SMS_Scheduled_at__c'
FROM [SMS Campaigns JB]
GROUP BY [Task:Id], [Task:Who:Contact:Id]
If you need to add 1 hour to the schedule time, then try nesting the query before grouping, as below:
It's possible, you have to use marketing cloud API you can use REST API or SOAP API it depends on you, ie REST API: https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/postDataExtensionRowsetByKey.htm
The same applies to SOAP API, you can find many examples in this page.
If I get it right what you are missing might be the following information:
JourneyActivityObjectID corresponds to TriggererSendDefinitionObjectID in the _Sent, _Open, _Click, and _Bounce, data views.
With that information you can query data regarding opens, clicks and so on. I hope this helps :)
You can use the Update Contact Activity in order to update a data extension based on a customer's pathway through your journey. You could use this method, for example, to identify exactly who is in a journey, where they are at and what date/time they entered/exited, etc...
If you wanted more granular data around whether they have been sent/opened/clicked an ...
Removed previous information.
In case the use of JB API Entry DE isn't possible, then this use case isn't possible in real-time with standard DE.
Maybe it would be an idea to build a new external service that constantly monitors the target DE and would populate API Entry DE for the Journey entry. It's a heavy workaround and probably isn't worth it for ...
The deletion process scans all sendable data extensions in an account
to remove the specified contact records.
Journey Builder entry source is a sendable DE, so I would say yes, contact's will be removed from the journey.
Based on our conversation so far, I believe the issue you're having is the difference between Journey and Contact data.
You can read more here: Journey vs Contact Data
Demo use case here: Journey and Contact Data in Decision Splits
I believe you could solve your issues by changing your custom activities to lookup Contact Data, rather than the Journey data. ...