Automation using Cloud Pages and Journey Builder in SFMC
Restaurant Reservation Automation using Cloud Pages and Journey Builder in SFMC
In this task, we will build a complete automation flow using Cloud Pages, Data Extensions, Journey Builder, and Email Studio.
The objective is to learn how Cloud Pages capture user data, store it inside Data Extensions, and trigger automated emails using Journey Builder.
Learning Objective
This task helps understand:
- Creating forms using Cloud Pages
-
Storing form submissions using AMPscript (
InsertDE) - Using Data Extensions as Journey Entry Source
- Sending automated confirmation emails
-
Difference between:
- Main Data Extension
- Cloud Page Data Extension
Method 1 — Using Main Data Extension
Step 1: Create Data Extension
Create:
Restaurant_Reservation_DE
Fields:
| Field | Type |
|---|---|
| SubscriberKey | Text |
| FirstName | Text |
| EmailAddress | EmailAddress |
| ReservationDate | Date |
| Guests | Number |
Screenshot: Data Extension Structure
Step 2: Create Email Template
Create reservation confirmation email.
Example:
Hello %%FirstName%%,
Your reservation is confirmed.
Date:
%%ReservationDate%%
Time:
%%ReservationTime%%
Guests:
%%Guests%%
Screenshot: Email Template Preview
Step 3: Create Cloud Page Form
Create reservation form with fields:
Name
Reservation Date
Reservation Time
Guests
Store records inside:
Restaurant_Reservation_DE
Screenshot: Cloud Page Form
Step 4: Build Journey
Use:
Restaurant_Reservation_DE
as Journey Entry Source.
Journey Flow:
Restaurant_Reservation_DE
↓
Reservation Confirmation Email
↓
Exit
Screenshot: Journey Canvas
Result: Every reservation submission automatically triggers an email.
Method 2 — Using Cloud Page Data Extension
Instead of storing records directly inside the main DE, create another DE.
Create:
CloudPage_Reservation_DE
Fields:
| Field | Type |
|---|---|
| SubscriberKey | Text |
| FirstName | Text |
| EmailAddress | EmailAddress |
| ReservationDate | Date |
| ReservationTime | Text |
| Guests | Number |
Screenshot: Cloud Page DE Structure
Step 2: Update Cloud Page
Change storage target from:
Restaurant_Reservation_DE
to:
CloudPage_Reservation_DE
Now form submissions will store records in the Cloud Page DE.
Screenshot: Cloud Page Code
Step 3: Create Journey
Journey Entry Source:
CloudPage_Reservation_DE
Journey:
CloudPage_Reservation_DE
↓
Reservation Confirmation Email
↓
Exit
Screenshot: Journey Builder Canvas
Result: Every form submission triggers automated email confirmation.
Final Architecture
Key Learning Outcome
Through this task we learned:
- Cloud Pages can collect customer information.
- Form submissions can be stored using Data Extensions.
- Data Extensions can trigger Journey Builder automations.
- Automated emails can be sent after every submission.
-
Cloud Pages can work with both:
- Main Data Extensions
- Dedicated Cloud Page Data Extensions
End-to-End Flow
Customer fills form
↓
Cloud Page
↓
Store data in DE
↓
Journey Entry Source
↓
Confirmation Email
This flow is commonly used in restaurant bookings, webinar registrations, event forms, reservations, and lead capture systems in Salesforce Marketing Cloud.
Comments
Post a Comment