Journey Builder Data Extension Entry Source in Salesforce Marketing Cloud

preview_player
Показать описание
Cameron Robert shows how to use the Data Extension Entry Source in Journey Builder to add subscribers to a Journey. Cameron then shows how to use the Automation Schedule to link the Journey to an Automation that can add subscribers to your Journey every time the Automation runs.

0:00 - Introduction
0:10 - Journey Builder Data Extension Entry Source Overview
1:48 - Journey Builder Data Extension Entry Schedule Overview
5:06 - Journey Builder Data Extension Entry using Automation Studio
9:23 - Journey Builder Create Automation Schedule
13:23 - Testing Journey Builder Automation Studio Entry
17:42 - Creating a daily SQL Automation to add subscribers to a Journey
20:53 - Summary

Salesforce Documentation:

Contact:

  1. Cameron Robert
  2. Salesforce Marketing Cloud
  3. Salesforce Training
  4. Marketing Cloud Training
  5. Marketing Cloud
  6. Journey Builder
Рекомендации по теме
Journey Builder Data 0:21:39

Journey Builder Data Extension Entry Source in Salesforce Marketing Cloud

Journey Builder Salesforce 0:10:48

Journey Builder Salesforce Data Entry on New Record in Salesforce Marketing Cloud

Marketing Cloud | 0:07:51

Marketing Cloud | Customer Journey for a promo campaign

Salesforce: Journey Builder 0:02:02

Salesforce: Journey Builder - Some questions about Data Extension Entry Source

Journey Builder API 0:14:42

Journey Builder API Entry Event in Salesforce Marketing Cloud

Introduction to Journey 0:15:31

Introduction to Journey Builder in Salesforce Marketing Cloud

Salesforce: Journey Builder 0:01:37

Salesforce: Journey Builder Entry Data Extension

Marketing Cloud | 0:07:31

Marketing Cloud | How to inject Contacts in a Journey using the REST API and Postman?

Journey Builder - 0:28:57

Journey Builder - Basics

Salesforce: Journey Builder 0:02:21

Salesforce: Journey Builder entry filtering using linked data extension

ClaimRow Function Does 0:02:53

ClaimRow Function Does Not Work as expected with Data Extension Entry in Journey Builder

Journey Builder: Entry 0:07:12

Journey Builder: Entry Events

Data extension entry 0:01:47

Data extension entry sources -Journey Builder Part3

Journey Builder Salesforce 0:01:40

Journey Builder Salesforce Data entry source - Task completed

Salesforce Marketing Cloud 0:06:18

Salesforce Marketing Cloud Data Extension Demo

Salesforce Marketing Cloud 0:04:18

Salesforce Marketing Cloud Journey Builder Welcome followup with API event

Exploring Journey Builder: 0:15:05

Exploring Journey Builder: Understanding Entry Sources and Activities in Salesforce Marketing Cloud

Salesforce: Triggered Send 0:01:44

Salesforce: Triggered Send Data Extension used for Journey Entry Data Extension

Journey Builder Entry 0:15:19

Journey Builder Entry Sources and Activities| Journey builder|Salesforce Marketing Cloud

Salesforce: Data extensions 0:01:26

Salesforce: Data extensions used in Journey builder - how to append data

Connect Journey With 0:04:28

Connect Journey With Automation | Salesforce Marketing Cloud | Journey Builder | Automation Studio

Salesforce Journey Builder 0:08:34

Salesforce Journey Builder Live Example 1

Salesforce: Accessing Data 0:02:19

Salesforce: Accessing Data Extension field values - Journey builder custom activity

Salesforce: How to 0:01:14

Salesforce: How to use Synchronized Data Extensions in journey builder?

Комментарии
Автор

Great 🎉work. Thanks you for good explanation.


Can you upload a video about


Automating the records in SFMC

rakeshejjigiri
Автор

Hello @cameronrobert. I REALLY appreciate your videos. I'd love a video that shows you how to pull in only X amount of people into a journey each day from a data extension of for example 10, 000 records. For some reason, I haven't found a way to do that, if there's not some natural field to separate them. I don't care which people enter the journey, but I don't want more than (for example 250 people) entering the journey each day.

Garmoe
Автор

Hi Cam, i need your assistance. I have created one data extension where it has email address and sfdc contact I'd are mandatory fields. I deployed one email as well to that data extension. Then I got the registrations from that deployed email. But in the registrants list, instead of sfdc contact I'd it has the same email address accordingly. So at the time of second deployment, i excluded that registrants and deployed the email. But the contacts didn't get excluded. May I know the system will match the sfdc contact I'd and exclude the contacts at the deployment time? That'sy mine was not excluded properly since in the data extension it has sfdc contact I'd and email address in registrants list?

Kindly confirm on these ..

santhoshm