Transactional Email Solution Kit
DOWNLOAD
First things first !
To download this implementation guide, click the download button below.
If you need more information about the implementation guide, you can read the Table of Contents below.
Keep Customers in the Loop
with Transactional Email
Salesforce Spring
salesforcedocs
Last updated November
Copyright Salesforce Inc All rights reserved Salesforce is a registered trademark of Salesforce Inc as are other
names and marks Other marks appearing herein may be trademarks of their respective owners
CONTENTS
Keep Customers in the Loop with Transactional Email
Transactional Email Solution Workflow
Design Considerations
Integration Reference Implementation
Configurations
KEEP CUSTOMERS IN THE LOOP WITH TRANSACTIONAL
Inform customers on the status of their orders through email while reducing call volume to your service centers Increase storefront
visits
Get Started
Explore system architecture related to this solution
BC Industry Blueprint
BC Reference Architecture
BC Solution Architectures
Take Trailhead modules related to this solution
Salesforce Solution Kits Quick Look
Customer Guide for Retail Quick Look
Customer Guides Quick Look
This solution kit helps you
Build trust with your shoppers
Keep shoppers informed and reassured
Inform shoppers when their orders are in process and complete
Let shoppers track their purchase from order to delivery
Increase storefront visits
Give your shoppers a personalized experience when you connect Commerce Cloud and Marketing Cloud
Required Products
Commerce Cloud SFRA or SiteGenesis
Marketing Cloud Journey Builder and Email Studio
Keep Customers in the Loop with Transactional Email
Transactional Email Solution Workflow
Implement This Solution
Transactional Email Solution Workflow
Learn how data flows through the configurations to keep customers in the loop with transactional email
Design Considerations
Keep these design considerations in mind when you keep customers in the loop with transactional email
Integration Reference Implementation
Implementation reference implementations are developer enablement frameworks that accelerate crosscloud integration by
providing code configuration and implementation patterns Use the Marketing Cloud reference implementation for BC Commerce
to keep customers in the loop with transactional email
Configurations
Use these configurations to keep customers in the loop with transactional email
Transactional Email Solution Workflow
Learn how data flows through the configurations to keep customers in the loop with transactional email
Workflow
The shopper places an order on the site
Commerce Cloud triggers an API to Marketing Cloud that contains the order data in XML format
Keep Customers in the Loop with Transactional Email
Transactional Email Solution Workflow
Marketing Cloud generates the order confirmation email using the transactional email template while parsing the XML data and
supplementary data from custom data extensions
Understand the Flow of Data
Collect the catalog product order and customer data feeds from the BC Commerce staging and production environments
Move the data to the Marketing Cloud SFTP server and create import activities so that Marketing Cloud consumes it on a schedule
via Automation Studio
Use BC Commerce data in Marketing Cloud via data extensions during the authoring of email templates creation of journeys and
development of personalized product recommendations
Extend the BC Commerce storefront by replacing its email functions with the Marketing Clouds triggersend features
Use the Marketing Cloud reference implementation customizations to trigger transactional email for common scenarios These
scenarios include Welcome Email Order Confirmation and Order Status Update Email
Functionality Considerations
The reference implementation enables email authoring using Marketing Clouds Email Studio rather than the developer storefront
template model supported by BC Commerce Enterprise
The reference implementation enables BC Commerce to trigger Marketing Cloud to generate transactional email delivery
The reference implementation supports delivery of BC Commercedriven data feeds to Marketing Cloud through SFTP customers
catalogs and orders
Use data feeds that Marketing Cloud consumes to shape email content including storefront product recommendations
Performance Considerations
Plan your Commerce Cloud data feed consumption to support expected volume and Marketing Cloud use cases
Keep Customers in the Loop with Transactional Email
Design Considerations
Limit data imported via the connector feed framework to million rows per import If your data volume exceeds million rows
consider multiple imports
Use data extensions to import data into Marketing Cloud for personalization or segmentation
Avoid importing data into Marketing Cloud for preprocessing or datalake activities
Related Content
Review this solutions use case and purpose
Keep Customers in the Loop with Transactional Email on page
Take the next steps in this implementation
Design Considerations
Integration Reference Implementation
Configurations
Design Considerations
Keep these design considerations in mind when you keep customers in the loop with transactional email
Catalogs
Streaming updates isnt efficient for large numbers of product SKUs
Language currency multibrand support and inventory affect the catalog feed model
Extend the catalog feed model to support multiple languages brands and currencies
Data Extensions
Follow best practices for creating data extensions To ensure that your data is efficiently stored and quickly retrieved choose the
correct data field types Set appropriate field lengths When no other option is available use unbounded columns whose field lengths
arent set Limit the total number of field lengths in a data extension to less than total characters
The order confirmation email template uses the supplemental data extension ShippingMethods to retrieve labels and descriptions
for shipping methods Seed this data extension with all supported Commerce Cloud storefront shipping methods
Triggers for Order Confirmation
Replace your legacy email delivery logic for order confirmation with the Marketing Cloud Connector reference implementation
Include the order details for the confirmation email in the hook message used to invoke the Marketing Cloud trigger
Related Content
Review earlier steps in this solution
Transactional Email Solution Workflow
Take the next steps in this implementation
Integration Reference Implementation
Keep Customers in the Loop with Transactional Email
Integration Reference Implementation
Configurations
See Also
Configuration BC Marketing
BC Custom Hooks Overview
BC Orderxsd Salesforce XML Schema
BC Marketing Cloud Reference Implementation Documentation
BC Marketing Cloud Reference Implementation Overview
Email Marketing and Streaming
Einstein Email Recommendations
Marketing Cloud SFTP Guide
Stream Catalog Updates Through Collect Tracking Code
Integration Reference Implementation
Implementation reference implementations are developer enablement frameworks that accelerate crosscloud integration by providing
code configuration and implementation patterns Use the Marketing Cloud reference implementation for BC Commerce to keep
customers in the loop with transactional email
After you sign in to GitHub the Marketing Cloud reference implementation for BC Commerce facilitates the platform customizations
necessary to integrate Commerce Cloud and Marketing Cloud
Before implementing consider conducting an environmental audit with a Marketing Cloud representative to confirm that you meet the
prerequisites for the use case
Before implementing the configurations sign in to GitHub and set up the Marketing Cloud reference implementation using the GitHub
repository wiki instructions Get started with Commerce API
General Information About Reference Implementations
Reference implementations are developerenablement frameworks that accelerate crosscloud integration by providing code
configuration and implementation patterns
Reference implementations support a core set of use cases that you can extend to support other customerdriven use cases
Reference implementations require customization and configuration in Marketing Cloud and BC Commerce Cloud The Commerce
Cloud storefront requires customization as part of the integration
Implementation and validation require operational and administrative experience with Marketing Cloud
Plan your implementation as you would any other BC Commerce Cloud feature by collecting requirements capturing work tasks
and making task estimates
What Your Company Can Do with This Reference Implementation
Accelerate integration time to market for Commerce Cloud and Marketing Cloud
Simplify and centralize email authoring and content management
Trigger transactional email from Marketing Cloud through Commerce Cloud
Track email performance using Marketing Cloud Analytics
Improve marketing agility efficiency and campaign performance
Keep Customers in the Loop with Transactional Email
Configurations
Personalize engagement based on past purchases and shopper interactions
Connect Commerce Cloud and Marketing Cloud using REST APIs
Enable oneway sharing of customer catalog and order data from BC Commerce Cloud to Marketing Cloud
Related Content
Review earlier steps in this solution
Transactional Email Solution Workflow
Design Considerations
Take the next steps in this implementation
Configurations
Configurations
Use these configurations to keep customers in the loop with transactional email
Set Up SFTP in Marketing Cloud
SFTP integrates the customer catalog content and order data feeds from Commerce Cloud
Set up multiple export processes to support these and other Commerce Cloud data sets
Commerce Cloud data sets persist in Marketing Cloud through data extensions
For retailers configure the data feeds in Commerce Cloud to deliver data to Marketing Cloud during periods of low traffic
Configure Product Catalog Import in Marketing Cloud
To ensure that the products represented in marketing communications align with your catalog definitions regularly import the
storefront catalog
Generate product recommendations from your catalogs
Configure Email Templates in Marketing Cloud
Configure email templates to use Commerce Cloud data for each supported template type
The Marketing Cloud reference implementation supports multiple transactional email templates beyond the order confirmation
and status usecases
Extend email templates to use product recommendations that Marketing Cloud Einstein generates
For more information on setting up personalized recommendations in email templates review the Personalized Marketing
Recommendation Solution Kit
Set Up Triggers in Commerce Cloud
Customize the storefront and replace BC Commerce Cloud generated order confirmation logic with the triggered Send API call to
Marketing Cloud Follow the reference implementation standards
Implement SFRA
Implement SiteGenesis
Keep Customers in the Loop with Transactional Email
Configurations
Related Content
Review earlier steps in this solution
Transactional Email Solution Workflow
Design Considerations
Integration Reference Implementation
