Contents
What does the API mean for Journey Builder?
The API allows you to programmatically access and interact with Journey Builder functionality. See Marketing Cloud Help to learn how to use Journey Builder to create advanced, enterprise-scale, marketing automations.
How is Journey Builder used in Marketing Cloud?
With Marketing Cloud we can track interactions using the powerful data capabilities of Journey Builder, also known as a live activity tracker of all the flows included within the Journey. Salesforce Journey Builder can be used if we want to build further flow based on instant response to any of the past activities.
When to use event option in SFMC Journey Builder?
Event options can be used if we want our Journey to get a trigger from Automation Builder. This option will be used if we want our Journey to start after few activities of Automation like refresh Filter Data Extension, update the tracking of subscribers. There are chances of having raw data from Marketing Cloud Pages or 3rd Party API calls.
Which is the best workaround for Journey Builder?
Cloud Pages are considered as the best workaround if we are planning to use API calls to start our Journey; Cloud pages considered as Landing Pages can be created within Marketing Cloud, and we can use that Smart Capture Form to insert our Subscribers into the Data Extension and Journey in real-time. 7.
When to use join activity in Journey Builder?
Join Activity and Path Optimizer are also Journey Builder’s flow control activities. Use Join Activity when you bring contacts from two or more paths into a single path. It redirects contacts flowing down one or more branches to an alternative journey branch.
Where are the contacts stored in SFMC Journey Builder?
When the API fires an event, the contacts entering the journey are stored in a SFMC data extension of your choice. Numerous API calls to the same system objects can impact performance, so be careful if your journeys have “update contact” activities reaching out to large, shared data extensions.