Journey Builder Data Extension Entry Source in Salesforce Marketing Cloud

Подписаться 8 тыс.

Просмотров 10 тыс.

50% 1

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:
• Data Extension Entry Source: Fire the Event: help.salesforce.com/s/article...
Contact:
/ camrobert
www.cameronrobert.com.au/
/ auscamrobert
Music: www.bensound.com

Опубликовано:

4 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 8

@yohannesdemile6309 3 месяца назад

Amazing tutorial

@santhoshm1617 Год назад

Very helpful video. Thanks Cam :)

@rakeshejjigiri8054 Год назад

Great 🎉work. Thanks you for good explanation. Can you upload a video about Automating the records in SFMC

@Garmoe 3 месяца назад

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.

@CameronRobert 3 месяца назад

You could use a Random Filter to select a specific amount of records. Alternatively you could use SQL functions like “SELECT TOP 250” to limit the number of records selected.

@santhoshm1617 Год назад

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 ..

@CameronRobert Год назад

Sorry to hear you are having issues with contact exclusions. The appropriate way to ensure contacts are excluded from future sends will be dependant on the way your data/objects are setup. Someone would need to review your data relationships to give meaningful assistance.

@santhoshm1617 Год назад

@@CameronRobert oh sure Cam.. i checked the data relationship where sfdc contact I'd have been mapped to subscriber key. So I am guessing its working based on sfdc contact I'd and excluding while deployment