Certified Marketing Cloud Consultant

The content of the forwarded email can include the body of the response email. To achieve this, we can use Personalization Strings:

* _RMM_ReplyBodyText* _RMM_ReplyBodyHTML

If the option to delay registration until the contact key is set (“Delay Registration Until ContactKey Is Set”) is selected, the user’s information will not be available in Contact Builder until the relationship to the Contact Key is established.

Mobile Push handles both unidentified and identified mobile contacts.
Before logging into the mobile application, a contact is still unidentified.
If we do not want the Contact Key to be an automatically generated GUID by the SDK and want to avoid duplicating contacts, we will need to delay the registration until a contact key is established.
In such cases, when this contact logs into the application, we need to retrieve the PersonContactId and register it using the SDK.

Within the delivery options of an email activity within a Journey, we can manage the recipients of the message using Publication Lists and Suppression Lists.

Marketing Cloud Intelligence (Datorama) extracts data from a variety of sources with different data types. It enables connecting, analyzing, and taking actions on all the data within a marketing dashboard to drive ROI, speed, and growth in a business.

If a contact clicks on the “View As Web Page” link but is no longer present in the Data Extension used for the send, the link will fail, and the email will not be viewable in the browser.
To overcome this, we will use SQL Query activities for segmentation, with the target Data Extension being the entry source of the journey. We will utilize a data update method instead of overwriting the existing data.

NTO needs to provide event attendees with the “short code” and keywords they need to send to subscribe to alerts and notifications. NTO will then send the alerts and notifications via SMS to the subscribed list of attendees.

In this case, we can leverage the default and custom relationships within the synchronized data extension attribute group defined by the system.
We only need to understand the data model and which person has entered the journey (Contact, Lead) to select the correct path when configuring the Decision Split in Journey Builder.

There is no issue with brand separation because NTO and, at the same time, email deliverability is one of the top concerns. However, Cloud Kicks will not have a high volume of sends that would require the use of a dedicated IP.
Therefore, the most suitable solution would be to use a private domain for the Cloud Kicks BU and continue using the IP of the NTO SAP, which already has an established reputation.

The question is about the entry source of the Journey, so answer B is more accurate as it indicates the use of a Data Extension as the entry source, which is pre-filtered to identify the contacts that should enter the Journey.

We do not want to store the information as an attribute of the contact but rather in a Data Extension, which is why we do not use an Info Capture template.
A “Text Response” is an automatic response when a contact replies with a specific keyword, and similar to an Outbound message, it cannot capture data.
For this use case, Mobile Connect offers a message type specifically designed for surveys (Vote/Survey message).

One of the most common use cases for using suppression lists is to exclude email addresses from certain sends that have opted out of commercial communications in other systems.
We can assign a suppression list to SendClassifications that are of commercial type, so that transactional sends would still be sent to those email addresses.

In Configuration, go to the Security section and Security Configuration. Within the Password Policy, we need to select the checkbox to exclude FTP users from password expiration.

Data Views do not store the recipient’s email address, and we cannot obtain that data by cross-referencing with the AllSubscribers list because that data is overwritten with each send.
The SendLog does not have a default field that captures the recipient’s email address; it must be included. Therefore, if that field does not exist, we cannot retrieve that data.
For this use case, we would use a Tracking Extract (an option within a Data Extract activity in Automation Studio):

* From the resulting CSV files of the Tracking Extract, the Sent.csv file provides information on which email addresses were received which were sent, identified by SendId.
* The SendJobs.csv file contains all the corresponding data for each send, identified by SendId. This includes the email name, subject, FromName, FromEmail, and send date.

Self-hosted DNS configuration is not included in standard support. If the client hosts the DNS records for a domain or subdomain, it requires expert technical resources. This option increases the time to secure a domain with SSL and requires work before securing the domains.
Another option is to delegate a domain or subdomain to Salesforce Marketing Cloud servers. This involves transferring only a portion of the existing custom domain to Marketing Cloud as part of the authenticated domain setup.
Both solutions require only four NS entries in the client’s DNS, but in the case of delegating the subdomain, Marketing Cloud is responsible for maintenance and updates.

The SMS send activities in Journey Builder allow sending to contacts that do not yet exist in Mobile Connect, provided that there is a field with a phone data type containing a number that includes the country code.
However, when using a Salesforce Entry Event, the default behavior in Salesforce is to normalize numbers starting with the country code 1 (United States and Canada).
This means that if a contact does not exist in Mobile Connect and reaches the SMS send activity, the SMS will not be sent to the contact.
To prevent the normalization process within Salesforce, we can format the phone number in Salesforce as +[country code][phone number].
The SMS send activity in Journey Builder will translate +[country code] to the contact’s regional settings, enabling the SMS message to be sent.

Marketing Cloud Connect is built on API calls, primarily REST and SOAP. One way to identify what is causing the issue is to enable detailed API call logging before running the failing process. Once activated, the log remains active for only 1 hour.

If we configure Reply Mail Management (RMM) to automatically forward an email to an email address, that email address becomes the From Address for the automated response.

The main factor that determines the strategy is email deliverability.
An email with AMPscript that performs multiple lookups to Data Extensions can significantly increase delivery time.
In such cases, it would be advisable to have the data more accessible, for example, in a single Data Extension where we can use a LookupRows function (which would be faster than multiple Lookups).
An even faster option would be to have the fields displayed directly in the Data Extension used for sending, allowing us to use Personalization Strings to display attributes from the same Data Extension.

The developer will be responsible for collecting data from the form and entering it into the Triggered Data Extension. They will also handle sending the opt-in confirmation email through a Triggered Send Definition.
The created Triggered Send Interaction will be associated with the desired email to be sent.
To change the email, you only need to pause the Triggered Send, modify the email, save the changes, publish the changes, and reactivate the Triggered Send. This sequence does not require the involvement of a developer.

To have all the abandoned cart products from each session in the second Data Extension, the “Session ID” field should be the primary key. Additionally, a unique identifier for each product (such as SKU) should also serve as a primary key. This way, there will be an entry in the Data Extension for each product within a session.
Therefore, we need to use the AMPscript function “LookupRows” to retrieve all rows from the second Data Extension for a given “Session ID” (a field that we have in the sending Data Extension). Each row will correspond to one product, allowing us to display a table with all the desired product information (name, quantity, price, and image).

It is not necessary for the Email Opt-Out field to be visible in the Contact/Lead view. However, it is important that the Sales/Service user performing the send through Marketing Cloud Connect has permissions for that field; otherwise, they will receive an error message.
In any case, if the previous email sent based on the file left in the FTP did not use the email as the SubscriberKey, the opt-out will not be reflected in Sales/Service.
The opt-out in AllSubscribers occurs at the SubscriberKey level, not the EmailAddress level.

Therefore, a subscriber may opt out in the AllSubscribers record that has their email address as the SubscriberKey but still opt in with the record that has the Contact/Lead ID as the SubscriberKey. As a result, it will not be reflected in Sales/Services.

To ensure that the opt-out in AllSubscribers updates the Email Opt-Out field in Sales/Service, the Contact/Lead ID should be used as the SubscriberKey.

When configuring Marketing Cloud Connect, we need to specify the desired level of tracking that we want to send to Sales/Service Cloud, as well as the frequency.
However, if we have not used the ID of a Contact or Lead but rather the email address as the SubscriberKey, the tracking will not be visible in Sales/Service Cloud because it does not identify the record.

The auto-reply messages that we can configure within the Reply Mail Management settings in the custom message section are simple texts. If we want to use HTML, we will need to have a pre-created Triggered Send with the desired email. Then, in the configuration of a Sender Profile, we will set up the “Custom Reply Mail Management Settings” section to use the Triggered Send we have created.

We need to consider whether it is truly necessary to have a 10-year purchase history in Marketing Cloud and determine alternative solutions if needed. Depending on the edition of Marketing Cloud, there may be a specific number of annual API calls available. It would be necessary to contact the Account Executive at Salesforce who manages the client’s account to confirm this information.

By querying the “_ListSubscribers” Data View, we can find the subscribers present in our lists. If we know the name of the Publication List where the desired subscribers are located, we can perform a query searching for the “ListName” field in the Data View.

Each MID (Business Unit) can only support one SAP for branding purposes. Multiple private domains can be set up within a BU, but the links for images and CloudPages will always point to the SAP.
Therefore, the first requirement is to have separate Business Units for each brand. Once the BU for the new brand is created, an SAP can be requested, which includes an SSL certificate and RMM (Reply Mail Management). This ensures complete customization without any reference to the other brand.

The only way to update the status of a subscriber, other than manually, is by importing a file into AllSubscribers with the SubscriberKey and current Email of each contact, taken from the existing records in AllSubscribers at that time to avoid overwriting data. Additionally, a status field will be included in which we indicate the new status to assign to those records.

The consultant must ensure that NTO does not have, and will not have, any use cases with the situations described in options C, D, and E.
If SQL segmentations are required because the information is in multiple Data Extensions or because it is necessary through this method, or if encrypted or compressed files are received, Automation Studio cannot be dispensed with because Journey Builder does not have those capabilities.

The two Data Extensions we need to join are Customer Data and Event Registration.
Having access to Event Registration, we can cross-reference with Venue Details using the venue ID, both through SQL and AMPscript. Similarly, we can cross-reference with Payment Details using the Event ID.

*File Transfer: The file is encrypted, and we use this activity to decrypt it.
* Import File: Once decrypted, we import the records into a Data Extension.
* SQL Query: We need to cross-reference with AllSubscribers to determine the SubscriberKey of each subscriber to be unsubscribed.
* Data Extract: The resulting subscribers from the previous query will be in a Data Extension with fields such as SubscriberKey, EmailAddress, and an unsubscribed Status. We extract these records with a Data Extract.
* File Transfer: We place the resulting CSV file from the previous step in the FTP import location.
* Import File: We perform an import to AllSubscribers with the subscribers to be unsubscribed, updating their status to unsubscribed.

Mulesoft enables the integration of Marketing Cloud with other systems to automate business processes.

Two fields are required: one for the phone number to which the SMS will be sent and another for the country’s local code.
The first field should have a data type of “phone,” and the second field should have a data type of “locale.”
Additionally, the Data Extension should have a field for the SubscriberKey, and it should be of type “sendable.”

The object on which the Triggered Send needs to be configured must have a lookup relationship to the Contact or Lead object, or to Account if it is a Person Account.
There must be an APEX-configured trigger on the desired object that sets the rules for when the send should be triggered.

Demographic data refers to factors such as age, gender, marital status, education level, and employment.
In fact, demographic data is used to group contacts into populations.
The relationship with a contact is one-to-one.

When we preview an email, we can check if our AMPscript code is correct, if the Personalization strings map the fields of the Data Extension, and verify the rules of the dynamic content blocks.

All the metrics that the client needs are included in the ‘Account Send Summary’ report. It contains data for the entire Marketing Cloud account organized by send.

It is a use case where, due to access security concerns from an IP for the first time, the client needs to ensure that the notification reaches the contact as soon as possible. Additionally, since it involves crucial information, we will use the transactional messaging API.

“All Subscribers” is the list belonging to Email Studio and can be accessed from there.
We can add contacts in Contact Builder either to an AllContacts list (Mobile, Push, or Group) or to a Data Extension.

We would assign the role of Marketing Cloud Channel Manager to handle campaigns across all required channels, and the role of Marketing Cloud Administrator to manage operations for the North America Business Units.

With a data model based on Data Extensions and Publication Lists, we can manage subscriber opt-outs at the level of communication type (newsletters, advertisements, alerts), avoiding global opt-outs that affect all marketing sends.

Users of Marketing Cloud Connect require both a Marketing Cloud user license and a Salesforce CRM license for most Marketing Cloud Connect functionalities, including email sending, and there must be an integration between the two.
By configuring “Deep Link” in Marketing Cloud Connect, a user can directly log in to Marketing Cloud from Sales Cloud (similar to SSO).

Indeed, the use of a SubscriberKey allows multiple subscribers to have the same email address. This way, each subscriber will have their unique identifier, enter campaign segmentations based on them, and receive communications that correspond to their preferences.

Knowing SQL is essential for segmentation.
SmartCapture does not require extensive technical knowledge, and an email can be built using blocks without requiring knowledge of HTML and CSS. It can display information from a data extension using Personalization Strings.

No need to develop any SmartCapture form because the client already has web resources for collecting communication preferences.
What is required is an integration with the client’s system via API so that we have the communication preferences in Marketing Cloud, stored in a Data Extension related to Contacts through Data Designer. API integration is essential to have real-time access in Marketing Cloud to all updated information about each contact.
This Data Extension would be accessible from Journey Builder due to its relationship with Contacts.

A suppression list contains email addresses.
The usual process is to create an automation that utilizes SQL to identify the email addresses to include in the list. This information is then extracted and deposited into the SFTP, followed by importing the resulting CSV file into the suppression list using an Import File activity.
If technical knowledge is limited and there is already a CSV file with the addresses to include, we would only need to perform the last step mentioned above. Simply leave the CSV file in the SFTP and import it using the Import File activity.

The Web Analytics Connector allows for expanding the web analytics service to track and analyze data from Marketing Cloud sends.
Through the connector, links in emails are tagged by automatically including specific variables in the destination URLs.
The analytics tool then tracks those URLs back to the email.
However, it does not have the ability to pass conversion information to Marketing Cloud.

“Multipart MIME” groups a simplified plain text version of the email along with the HTML version of the email. While the HTML version of an email message can include colors, graphics, specific fonts, and links, the plain text part is very simple.
Spam filters prefer to see an alternative plain text version: a lazy spammer wouldn’t bother creating a plain text alternative, so emails that are only in HTML raise a red flag for spam filters.

“In Reply Mail Management, we can configure dynamic From Name and From Email for the responses, but the actual response message remains the same. Therefore, if we want to display responses in multiple languages, we will need multiple Business Units, each with its own RMM.
The postal address data is collected from the account configuration, but we can choose the option of a customized footer. At the time of sending, it retrieves the MID of the Business Unit from which it is sent using Personalization Strings and through the use of AMPscript to query a Data Extension that contains the necessary data. This allows us to dynamically display a different address for each BU.
The language configuration is done at the user level, not the BU level.
To have a campaign differentiated by region, we could achieve it with a single Business Unit by simply segmenting based on region, without the need for a BU per region.

The ‘Transactional Journeys’ in Journey Builder allow non-technical users to configure a transactional API input source without the help of a developer. They enable monitoring of journey performance aspects such as error count or send queue from the journey control dashboard in the Journey Control Panel.
When hiring a developer, if they enable the event notification service, a notification will be received if the message is not delivered (implementation with the Event Notification Service API).

To request and store contact information, Mobile Connect provides us with the ‘Info Capture’ template, through which information is captured and stored as contact attributes. The use of an outbound SMS is required.
A ‘Text Response’ is the message we prepare to be sent as an automatic response when a contact responds to a sent SMS including a specific keyword.

The welcome email should be sent when the contact is added as a campaign member. Therefore, we will configure the Journey with a Salesforce Data Entry Event so that when a new record is created in the Campaign Member object for the specified campaign, the corresponding contact will enter the journey and receive the email.

The Contact Count report provides information about the total number of contacts in a Marketing Cloud account and runs on a weekly basis. We just need to schedule it to be delivered to the email address of NTO’s Chief Manager Officer.

To have all the data in one central place that we can keep updated, we will use a Data Extension that contains the name and email address of the manager for each region.
In Content Builder, we will have two Code Snippets, one for the From Name and another for the From Email, and in both, we will use the AMPscript Lookup function to retrieve data from the Data Extension.
In the configuration of the Dynamic Sender Profile, we will call the Code Snippets using AMPscript in the From Name and From Email fields, using the TreatAsContent and ContentBlockByKey functions.

We will schedule an automation to run sometime after 3 a.m. It will first execute an Import File activity to a target Data Extension. Then, through two SQL Query activities, we will separate the data into the two Data Extensions required by the client.
We will configure the automation to send a notification to the email address provided by the client if the automation does not find the file when it runs.

Connected App Authentication prevents API calls made by Marketing Cloud Connect via REST and SOAP from counting towards the daily limit of 24 hours.
Most calls made by Marketing Cloud Connect are SOAP and REST. The BULK API calls are only used for individual email results and individual link details for tracking.
Data Stream is the broad term for the connectivity between Salesforce (Sales & Service Clouds) and Marketing Cloud. Synchronized Data Extensions are part of this connectivity, allowing us to access data from Salesforce objects in Marketing Cloud.

The registration form for the raffle would be developed using Smart Capture on a Cloud Page, so that the participant registrations enter the chosen destination Data Extension.
The goal is to collect opt-ins for marketing campaigns in general, so we will send an email to the attendees with a link to a subscription center.

In Contact Builder, we can import data using an Import Definition or at the moment.
When creating an Import Definition in Contact Builder, we can choose a Data Extension or an AllContacts list (Mobile, Push, or Group) as the destination.
If we select ‘Map by header row’ during the import, the field names in the destination and the column names in the file must match exactly.
In Contact Builder, we can create an Import Definition without executing it, but we cannot execute it without saving it. This is different from the option to import without using an Import Definition, which can be executed without the need to save it.

The records in a Send Log are stored and remain in it based on the retention configuration set when it was created. If no specific retention was specified, they will be stored indefinitely.
A Send Log can be queried via SQL Query by joining it with Data Views to obtain information about a specific send.

The best solution to track the click activity and proceed with the second send is to include a confirmation CTA in the invitation email that redirects to a CloudPage designed to capture the person who clicked and the timestamp of that interaction, and update the Data Extension accordingly.
An engagement split in the Journey will only evaluate if a contact clicked at the moment the engagement split is executed, but it won’t capture the exact timing of the interaction.
We cannot schedule the CloudPage to trigger the second email immediately because it needs to be sent two days after that specific moment, not immediately.

Using a Smart Capture form as an entry event to a Journey, we will inject the visitors who register into it and send them an email requesting confirmation of their opt-in by clicking on a CTA (Call-to-Action). Later in the Journey, we use an Engagement Activity to check which visitors have clicked on that link, and through an Update Contact Activity, we will update a second field in the Smart Capture registration Data Extension. This field is specifically created to indicate those who have confirmed double opt-in.

The starting database is kept updated in real-time via API, so we only need to filter it with the three specified date conditions to obtain each segmentation and send the corresponding email to each of these groups.

In Enterprise 2.0, you can choose between instance-level or Business Unit-level subscriber opt-out management. In this case, we would configure the account with the second option.

In Email Studio Tracking, a user can view information related to a send, including metrics such as opens, clicks, undelivered messages, and unsubscribed subscribers.

Populations represent a master set of contacts within the Marketing Cloud account, united by a general theme, and help create audience segments.

With the Sender Profile, the contact’s email client will display the name and email address from which the message appears to originate. In the “Use Specified Information” section under the “Forward” settings, we will enter the name and email address of the person to whom the received responses should be forwarded, in this case, NTO’s CEO. This way, the CEO will receive the responses without the contacts seeing his actual email address when they reply to an email.

NTO wants to import the file as soon as it is generated, so we need a File Drop-triggered Automation rather than a scheduled one. It will include the following activities in this order:

* Import Activity: import the data from the file into a target Data Extension.
* The necessary SQL Query Activities to perform the different segmentations required for the sends.
* One Send Activity for each of the sends to the segmentations obtained in the SQL Query Activities.

With the Content Creator role, you will have access to all content, including shared folders, and also to tracking information in Email Studio. However, you won’t be able to manage subscribers, for example.
With the Data Manager role, you will have access to all of Email Studio except for the content section.
Both roles complement each other, and the user will have access to everything they need to work without being assigned the Administrator role. Therefore, it is the least privileged role assignment.

The Complaint Data View contains information about subscribers who have reported the email sent by Marketing Cloud as spam, so we will schedule an Automation with a SQL Query Activity to retrieve this information.

The Event Notification Service API will inform us in real-time if an email has failed to be delivered, allowing us to take actions such as delivering the communication through another channel to ensure the contact receives it.

The data from the Campaign and Contact objects will arrive in Marketing Cloud through the connector and will be available in the synchronized Data Extensions. In order to segment using the existing information in Marketing Cloud related to points of sale, SQL Query Activities will be needed in Automation Studio.

We will need SQL because we need to find customers who have clicked on specific products promoted in email campaigns, and those links may vary. Additionally, we also need to cross-reference the information from regional markets and create master data.
The emails can be created with dynamic content blocks based on the regional market using rules that utilize the fields from the subscriber master data we create.

With publication lists, we can track the sections to which each contact is subscribed. We would have a list for each section and use them for sending communications.
Working with publication lists requires a data model based on Data Extensions rather than lists.

We need to understand:

* How to identify subscribers, which is essential for the data model.
* Whether subscribers should be simultaneously enrolled in multiple journeys, which also affects segmentation if we need to consider exclusions.
* When they should enter each journey, which will indicate the entry method into the journey and the frequency of sends if it is scheduled.

In Data Designer in Contact Builder, cardinality refers to how Data Extensions relate to each other based on attribute links (one to one, one to many, many to many).
Once established, changing cardinality can drastically alter the behavior of different entities within Marketing Cloud.
For example, any filtered list that relies on information from a Data Extension linked to Contacts may no longer have access to that information. As a result, the contact will not be displayed in the filtered list or receive any communication using that list for sending. Therefore, we need to review all sends that originate from filtered lists based on that Data Extension.

The Web Analytics Connector serves to expand web analytics to track and analyze Marketing Cloud email data, as well as identify web traffic coming from Marketing Cloud. It helps in gaining a better understanding of the effectiveness of marketing campaigns.
The use case involves leveraging transactional data from the web store for journeys.
Therefore, we will need:

* The use of Data Designer to create attribute groups that connect web data with contact data, enabling us to query them within a Journey in a Decision Split or Goal.
* Content Builder to create the messages that we will send in the Customer Journeys.

We should create Subscriber attributes for the FromName and FromEmail fields and map them with the information from Sales Cloud.
Then, we would create a Sender Profile that displays the information from the attributes either through AMPscript or by using Substitution Strings.

Random Data Extensions are populated with records at the time of their creation and cannot be updated with a Filter Activity.
On the other hand, a Filtered Data Extension can only be manually refreshed.
When we execute a Filter Activity in an Automation, it calls a previously created Data Filter that updates the records in the target Standard Data Extension.

We can choose to apply data retention policies to Data Extensions within Marketing Cloud.
Depending on the configuration we set, either individual records or the entire Data Extensions may be deleted.

There can only be one parent Business Unit in a Marketing Cloud instance, and subscribers appear in all Business Units.
On the other hand, it is common to configure the Business Unit hierarchy in a Marketing Cloud instance to reflect the organizational structure of the company. Business Units can share information among themselves by using shared folders.

First, we need to have triggered sends enabled for the Lead object in Sales/Service Cloud.
Then, we need to create the Triggered Send Definition from Sales/Service in the Marketing Cloud tab.
Finally, we will configure the rule to trigger the email sent using APEX.

The solution for the use case is the implementation of a scheduled Automation that, with the necessary SQL Query Activities, retrieves the targeted customers and injects those records into the input Data Extension used in the Journey.
The Journey will be triggered by the automation and will impact the customers through the desired channels using message Activities (Email, In-App Message, Inbox, LINE Message, Push Notification, SMS, and WhatsApp).

Scheduled Automation to run every morning at the desired time with the following activities:

* SQL Query Activity to retrieve records from the previous day.
* Data Extract Activity to extract the data from the Data Extension where we stored the result of the query from the previous step.
* File Transfer to deposit the extracted CSV file in the Import location of Marketing Cloud’s FTP.
* Sending the email in which we will use the AMPscript function ‘AttachFile’.

The API will return a JSON response that needs to be parsed.
Currently, it is not possible to parse JSON using AMPscript alone. It requires combining it with SSJS (Server-Side JavaScript).
However, using SSJS in an email is not considered a best practice.
On the other hand, GTL (Guide Template Language) is a specific programming language for Marketing Cloud emails that allows us to parse JSON straightforwardly.

If the rate of collecting records is in the thousands per minute and it is not necessary for the data to be collected in real-time, it is better to deposit a daily file in an FTP location that contains all the records to be imported into Marketing Cloud. The FTP location can be within Marketing Cloud or an external one.

We need to have a scheduled Automation with the necessary frequency to keep the purchase data updated in the corresponding Data Extension. By creating an Attribute Group in Data Designer, this Data Extension can be queried in the Decision Split of the Journey to evaluate whether the contact made a purchase or not.

They should consolidate all contact information from various channels into a single record, so that in Marketing Cloud, a contact is identified by the unique Contact Key, which will be used to assign the relevant communication channel information to the contact.
Through the connector, Salesforce objects whose information needs to be available in Marketing Cloud should be synchronized.

Distributed Marketing allows for creating content following brand guidelines and unified styles, sharing that content, and customizing it for sending in Marketing Cloud from Sales Cloud.

We can configure the Automation to be triggered either by File Drop or scheduled to run after 11 pm once the file has been uploaded.
Regardless of how the execution is initiated, we will need the following steps:

* File Transfer: Since the file is encrypted, we will need to use the ‘Manage File’ option.
* Import File to inject the records into the target Data Extension.
* One (or multiple) SQL Query Activity to segment those who have interacted with previous sends.
* Send Email: To send the communications.

We would assign the “Content Creator” role to the Email Specialists users, granting permissions for Automation Studio. Subsequently, we would assign each Email Specialist the Business Units they need to access.

To increase the purchase frequency, we can analyze our data and perform a series of simple calculations to obtain ratios and indices. In this regard, it is important to know the last purchase date.

Furthermore, we must reach as many of our customers as possible and encourage them to interact/react to the content we send them, which will result in increased purchases. For that, we need to know the preferred communication channel for each of our customers and establish a multichannel strategy.

Within Events as an entry source for a journey, you can choose between ‘Contact Data’ and ‘Date Based Event.’
The use of a Sales/Service event is very common when there is integration between any of these clouds and Marketing Cloud.
Lastly, we can configure a journey to be triggered by a form developed with Smart Capture on a CloudPage.

Synchronized Data Sources cannot be used as sendable Data Extensions.
After synchronizing objects in Data Stream within Contact Builder, we will need to use Data Filters or SQL Query Activities in Automation Studio to produce a Salesforce Sendable Data Extension that can be used for sending and to return tracking data to Sales/Service Cloud.

When configuring the Marketing Cloud connector, it includes the account setup for accessing integration user data. If we check the “Scope By User” box, the reports and campaigns visible to the user are the ones available for selection as the target audience for sends. The returned subscriber list is limited to what the user initiating the send has access to view.

Connected App Authentication prevents REST and SOAP API calls made by Marketing Cloud Connect from counting towards the daily 24-hour limit, but only for these types of calls. Bulk API calls and login calls still count towards the 24-hour limit. The limits for simultaneous API requests still apply as well.
The majority of calls made by Marketing Cloud Connect are SOAP and REST. Bulk API calls are only used for individual email results and individual link details for tracking.

Both suppression list management, data relationships, and subscriber profile attribute management are available in the Subscribers tab in Email Studio.
The Data Manager role provides access to all of Email Studio, except for email content. Therefore, this is the role that needs to be assigned as it is more restrictive than the Administrator role while still providing IT teams with access to everything they need.

Data table relationships in Contact Builder are created through Attribute Groups. In an Attribute Group, Data Extensions are linked to Contacts or other Data Extensions, but not Lists.

When it comes to a one-to-one relationship, we can use Profile Attributes or Lists: each subscriber has a unique value for Last Name, for example.
When there is a one-to-many relationship, Data Extensions should be used.
If a subscriber has more than one value for an attribute, we have a one-to-many relationship.

The Not Sent contacts can be obtained using a Data Extract activity in Automation Studio with the Tracking Extract option.
However, if the purpose is a report, within Analytics Builder, we have the standard ‘Subscribers Not Sent to’ report in Marketing Cloud.

It is necessary to use a value that is a unique customer identifier, so we discard email since there can be multiple customer records associated with the same email address (family members).
The Contact Key must be a unique, persistent value independent of the sending channel.
A safe bet is to use the unique identifier (ID) already being used in the CRM.
If we do not have a CRM ID, using the Mobile Device ID, which is a unique customer identifier that distinguishes by mobile device, is a better option than using the email address as the SubscriberKey.

The distribution of the Marketing Cloud instance in Business Units must reflect NTO’s organizational model, so it is necessary to know the geographical or brand-based separation. If a sandbox environment is available for Sales Cloud, it must be synchronized with a different BU, and sometimes a separate testing BU is required from those used in production.

The audience can be refreshed through an SQL query that queries the synchronized Data Extension of the SF Object where the appointment information is located and injects the records into the Data Extension used as the entry to the Journey. The Journey must be configured to be triggered by the automation’s execution and should have a “re-entry anytime” setting. It should include sending the appointment reminder and an Object Activity to update the record in Salesforce.

When there is a performance issue with a journey due to a large volume database, we need to explore options to limit the number of contacts entering the journey and only evaluate the necessary ones.
Therefore, we will not use the contact entry filter when configuring a Data Extension as the entry mode to the journey, nor cross-references with Attribute Groups in Decision Splits.
Instead, we will perform segmentations using SQL in an Automation to select the records that are injected into the entry Data Extensions for each journey or use filtered Data Extensions.

The information received from Web Analytics is stored in a Data Extension. In Data Designer, we will create an attribute group where we will relate the Web Analytics Data Extension with the Marketing Cloud Contact.

To properly configure Reply Mail Management (RMM), it is necessary to provide an email address for messages received that RMM is unable to identify using any of the response rules.
Additionally, if we want to unsubscribe requests that come in response to the emails we send and contain any of the unsubscribe terms, we need to have “Yes” selected in the Manual Unsubscribe Requests section.

You can assign a role to an individual user per Business Unit or to an entire Business Unit (where each user in that Business Unit inherits the role). Therefore, you can either assign user administration permissions to the Channel Manager role or to each of the Business Units.

The client wants to test different strategies, which may include sending different emails or subjects, or testing different journey designs. Therefore, we will use the option to create random Data Extensions in Email Studio, a utility that allows us to create up to 12 Data Extensions when the client needs 11.

Using the LookupOrderedRows function in AMPscript, we can retrieve all rows associated with a contact in the Data Extension. We will use LookupOrderedRows instead of LookupRows because it allows us to sort the records based on a specific field in the Data Extension and select the one we are interested in (for example, the most recent date by sorting on a date field).

The best solution is to identify the customers who had an active session at the time of the outage and notify them specifically about the service restoration, without mixing them with, for example, abandoned cart customers or any other journey.

The requirements clearly state to import records from the Salesforce Case object that are marked as “Contact Me.” Therefore, we will synchronize the object from Contact Builder Data Sources and filter for those that have the field set to true (a checked box translates to true in boolean values).

Since there is no specific time and name for the file, we need to configure a File Drop-triggered Automation. In the Import File activity, we will use the Substitution String %%BASEFILENAME_FROM_TRIGGER%% to indicate the filename.

To access data from a Data Extension that is not used as the audience for the send, we need to use AMPscript.
We could also use GTL, but in this use case, we need to display the send date in the email, and typically, the date needs to be formatted, which requires AMPscript.

For transactional sends, Internet Service Providers (ISPs) consider the delivery as high priority, so IP warming is not necessary.

The information is stored in multiple Data Extensions, and it is necessary to query them and cross-reference the data to determine the audience that should receive the follow-up email. Therefore, SQL is required.
The email can be constructed using a template with blocks, so it is not necessary to have knowledge of HTML or CSS. If the personalization is based on attributes contained in the Data Extension used for the send, AMPscript is not required, as we can use Personalization Strings (if any data formatting is required, it can be done using SQL).
We can even create a dynamic email without using AMPscript by utilizing dynamic content blocks and dynamic subjects.

Marketing Cloud cannot use synchronized Data Sources as sendable Data Extensions.
We will import the Salesforce report containing the data we need for both the send and personalization into a Data Extension.
We can use Personalization Strings within the email if the information we want to display is directly available in the Data Extension. If we need to process them (e.g., format a date) or require additional information about the person entering the journey beyond what is captured in the report (and Data Extension), we will use AMPscript

Publication lists help control which subscribers receive which categories of Emails and SMS (newsletters, alerts, etc.).
They assist in managing unsubscribes and opt-outs, and by using publication lists, you can provide subscribers with the option to unsubscribe from a particular category of communications without affecting other categories to which they are subscribed.

The Data Extension used for importing records should only contain the records that come in each file, as these records change with each execution (there may be new records, updates to existing records, and records that are currently in the Data Extension but need to be deleted). Therefore, an “overwrite” is required.

If we want to send from a new Business Unit using a new domain and ensure that it does not impact the deliveries of the existing functioning Business Unit, we need a Sender Authentication Package (SAP).

To use Journey Builder to request customers to provide a rating for a purchased item or a rendered service, we need to integrate the Marketing Cloud account with Google Analytics 360.

The standard Marketing Cloud preference center directly updates the information in the mapped fields of the corresponding objects in Sales/Service Cloud. However, for multi-org accounts, the standard preference center cannot be used, and a custom one is required.
On the other hand, a “Person Account” is still an Account, and from the standard preference center, there is no permission to edit this object. Only the related fields of the Contact are accessible, not those belonging to the Account.

The personalization string used to enable the web view is %%view_email_url%%. If you are using a standard template from Content Builder, it is included by default.

Setting up a transactional triggered email that is triggered by an API when a customer makes a purchase.

* Using a Data Extract activity (specifically Tracking Extract option), we identify the contacts we want to target.

* The resulting file is deposited in the Enhance FTP, so we need to use a File Transfer activity (specifically Move a File option) to move it to the desired FTP location, usually the Import folder.
* Through an Import activity, we will inject the data into the Data Extension that serves as the entry point for the Journey through which the SMS will be sent.

The communication with the appointment needs to be sent at the moment it is scheduled, so we need a Journey triggered based on an event rather than a scheduled Automation.
The Appointment object does not have a direct relationship with the Contact object in Salesforce, so we cannot configure the Journey with a Salesforce Data entry because we cannot select the Contact to enter the Journey.
If we configure a Journey with an event triggered by API, from Process Builder in the CRM, we can make an API call to the EventDefinitionKey of the Journey, sending the Contact who needs to receive the communication at the time the appointment is scheduled. The communication will be sent from an Email activity in the Journey, and if the API call includes the Appointment record ID to update, we can use an SF Object activity to update the “Confirmation sent” field as checked.

For Enterprise 2.0 edition, you can choose how to handle unsubscribes in Email Studio, either at the account level or at the Business Unit level.
For this use case, if each brand is a Business Unit, we can apply the second option. Otherwise, if everything is within the same BU, unsubscribes cannot be managed separately with this out-of-the-box solution.
Furthermore, the SAP configuration is at the BU level, so each brand would have its own customized domain that would appear not only in the sender of the emails but also in image URLs and landing pages.

One data point to determine the best customers is precisely the LTV (Lifetime Value), which provides an estimation of the average revenue a customer will generate over their lifetime.
This can be complemented by looking at the dates of the last purchase to understand the customer’s recent activity.
And by adding the conversion rate, we can obtain an audience of the highest-value customers for the company.

Of the described options, the two ways in which we can affect the data stored in a Data Extension from Contact Builder (whether it has a primary key or not) are either by adding a record or by deleting the data from it.

Delivery Profile and Send Classification are configurations within Marketing Cloud, not Sales/Service Cloud.
When sending from Sales Cloud through the connector, you can choose the sender’s email address as the user’s own email address (or select the Record Owner option), or you can use organization-wide addresses that apply to your user profile.

We will create a “Salesforce Send Definition” in Email Studio, adding the Sales report as the recipient list from the “Salesforce Data Extensions” folder.
Next, we will select the created “Salesforce Send Definition” and configure the send.

Automation configured by File Drop that will start every Monday at 1 am when the payments.csv file is placed in the FTP.

* The first step is a File Transfer activity because the file is encrypted.
* Import File to store the data in a Data Extension.
* Filter Activity where we will run a Data Filter on the Data Extension from the previous step and obtain the segmentation for the send.
* Wait Activity until 12 pm.
* Send Email.
* Wait Activity for 5 days.
* Data Extract to retrieve tracking data (Tracking Extract).
* File Transfer of the file obtained through the Tracking Extract to the specified FTP location.

If the data has been collected from the registration landing page and is stored in the Data Extension used as the audience for the email sent, the simplest way is to display the information using “Personalization Strings,” which directly render the content of the attributes from the Data Extension used for the send.
In this way, if we have a field in the Data Extension called Name, we can include a greeting in the email like “Hello %%Name%%,” which will be rendered as “Hello María,” displaying the value that field has for that specific contact.

There is no possibility to migrate to a pre-warmed IP, and you cannot inherit the history because when configuring SAP, you will have a different IP.
For a database of 3 million, it will most likely require 6 weeks of warming up, and proper planning and execution are essential because IP warming is crucial to establishing a good IP reputation, ensuring that email clients do not block the deliveries from a Marketing Cloud account.

The “alias” tag is the name of a parameter that we can assign to links within Marketing Cloud.
This allows us to differentiate when we have links with the same URL and track which specific link generates the activity.
To track conversions effectively, it is essential to configure emails to include a conversion tracking link and use the “alias” in the href.

We should understand that the question is referring to standard roles, not custom roles. In the latter case, they would specify the functionalities and permissions of each role, or there would be a specific mention in the question that they can be standard or custom.

The “Marketing Cloud Channel Manager” role allows the creation and execution of interactive multichannel marketing campaigns, as well as the management of specific channels.

The “Marketing Cloud Administrator” role allows the control of channels, applications, and tools and applies to all functionalities except Email Studio.

The roles of “Regional or Local Administrator” and “Email Marketing Manager” are not standard roles.

The differences between triggered emails and transactional emails are as follows:

*Transactional emails provide crucial information such as order confirmations, account notifications, shipping notifications, password resets, and emails with a call-to-action for activation.
*Transactional emails do not require an unsubscribe link.
*Triggered emails are commercial emails that are triggered by specific actions or events, such as product suggestions, abandoned cart reminders, or recommendations.

Both an Automation and a Journey can be scheduled to run indefinitely (end date = never) according to the specified frequency.
In both cases, we can use Wait Activities based on a specific time duration or a precise date.
Finally, in both cases, we can configure parameters for sending an email.

With the Approvals feature in Marketing Cloud, we prevent unsanctioned emails from being scheduled for delivery or sent.
Similarly, once an email has been approved, it cannot be edited without removing the approval first.
There are three sets of permissions in Approvals (Workflow Teams, Approval Items, and Comments):

Workflow Teams: Controls the creation of review teams (users)
Approval Items: Controls which users can initiate the approval process
Comments: Controls who can delete comments

The activities we need in the Journey are Send Email, Wait, and Update Contact.
After each Email Send, we need to configure a Wait activity for a period of one week to complete the series of 5 emails.
At the end of the series, we will set up an Update Contact activity to mark the flag in the input Data Extension, updating the corresponding boolean field.
Apart from these activities, we need to configure the Goal so that if a customer achieves it, they exit the Journey.
To do this, we will configure the Goal by filtering the Data Extension where the indicative data of the customer’s purchase is located, which will be accessible through Data Designer.

Auto-reply emails are configured in the Reply Mail Management (RMM) section. RMM is one of the utilities that come with SAP (Sender Package Authentication) when acquired for a Business Unit, although it can be purchased and configured even if SAP is not available.

Publication lists help control which subscribers receive which categories of Emails and SMS (newsletter, alerts, etc.).
They assist in managing unsubscribes and opt-outs, and by using publication lists, you can provide subscribers with the option to unsubscribe from a particular category of communications without affecting other categories to which they are subscribed.

When the file with the data is left around 4 PM, the Automation will be triggered, importing the data into the Notice Data Extension.
Next, we will execute a Filter activity to segment the audience that should receive the purchase notification email.
By configuring a 17-hour Wait activity, we will then execute another Filter activity to retrieve the records that should receive the survey on that day, and we will send the corresponding email to the obtained audience.

Emails are built using HTML language, and with CSS, we can modify and add styles such as color, font, size, etc.
Server-Side JavaScript (SSJS) is used in CloudPages and Script Activities in Automation Studio.
AMPscript is the native language of Marketing Cloud that we can use to create dynamic and personalized content in both Emails and CloudPages.

Among the proposed options, the simplest way for each BU to continue having their separate Data Extensions while allowing a Marketing Cloud user to access all the data is to assign the users the Administrator role. This way, they will have read, edit, create, and delete permissions in all Data Extensions and their records.

The “Marketing Cloud for AppExchange User” permission set in CRM allows the Marketing Cloud user to view and send to any Contact, Lead, Campaign, or Report in Salesforce. Therefore, what we need to do is assign this permission set to the integration user (the user through which the connection to Salesforce is made).

Naturally, in the Customers database, we have our contacts, which is why it is linked to Contact.
Similarly, a customer can have multiple orders, so we link Orders to Customers.
Lastly, each order includes the products within it, so we link Products to Orders.

The _MobilePushDemographics data view does not exist.
On the other hand, to create a filtered Data Extension, we need to do it from Email Studio because that option is not available from Contact Builder (in Contact Builder, we can only create Standard Data Extensions, neither Random nor Filtered).
The best solution would be to create a filtered MobilePush list in Contact Builder, although we can also filter within Journey Builder using the MobilePush Demographics Attribute Group.

In Marketing Cloud, a “database of records” is the single source of truth that contains the updated subscription status of a contact, as well as general information about the contact.

Suppression lists serve as a “do not contact” list for email deliveries. Auto-suppression lists typically include addresses with a history of spam complaints, unsubscribe lists from previous providers or advertisers, addresses of competitors, and cancelled customers.

There will be sends from Marketing Cloud and from the other external system. If there is no synchronized flow of unsubscribes between both systems, it could impact contacts who have requested to unsubscribe.

Marketing Cloud does not merge and deduplicate contacts. In order to correlate the records of the Case object in Salesforce with the customer they belong to, it will be necessary to synchronize the Contact object as well. The Contact object will store the relationship to the ERP system’s database, and Contact records will be automatically added to Marketing Cloud Contacts when the synchronization occurs.
Therefore, if you want to start using Salesforce objects as a data source in Marketing Cloud, a migration is required to use the Salesforce data model IDs.
Using the email address as the Contact Key is not recommended because a database can have multiple customers sharing the same email address (for example, multiple family members). The Contact Key should be a unique, persistent value that is independent of the sending channel.

We need to import the data with an Overwrite.
The data changes every day, and there may be records that don’t change and records that get updated. But there are also records that no longer appear in the file and need to disappear, so if we update without overwriting the Data Extension, those records would still appear.

The Journey Builder API is only accessible for REST, not for SOAP, so the form hosted on the company’s website will trigger the Journey through a REST call.
On the other hand, a Smart Capture form hosted on a Cloud Page can be used as an entry event in a Journey.

We would create an Automation where we would use SQL to query the data views of _sent, _open, and _click.
All the information would be saved in a single Data Extension, and we would extract the records using a Data Extract activity, placing them in the corresponding File Location of the data warehouse through a File Transfer activity

We need both the Customer Data Extension and the New Accounts Data Extension to be up to date, so the cross-referencing between the two tables should occur after these updates are completed.
We could have a process triggered by File Drop when the New Accounts file is deposited in the FTP, but it cannot be answered B because it does not include a Wait Activity before the Query Activity. This means that the SQL cross-referencing would occur at 10pm, before the Customer Data Extension is updated (which happens at 1am).
It should be an Automation scheduled after 1am.
Of the two Automation answers at 2am, the correct one is answer C because the file deposited in the FTP is encrypted and requires a File Transfer Activity to decrypt it.

“Web-safe fonts” are font families that can be found in most browsers and have a higher likelihood of being supported in email clients.
By using a safe font that closely resembles our brand’s font, we ensure that it will display well in most email clients and avoid displaying a default font that looks completely different.

Since this is a post-purchase communication, we need to consider that a contact may make multiple purchases and will need to enter the Journey each time they do so. Therefore, we will configure it with a “re-entry anytime” setting.

Solution A is the one we are looking for:

– By configuring the Automation with a File Drop, its execution will be triggered every time a file is deposited in the SFTP, even if it happens multiple times a day.
– The data in the file needs to be stored in a target Data Extension using an Import File Activity.
– To segment the data, we will use Query Activities as needed, depending on the complexity of the segmentation and the audiences we want to obtain.
– Finally, we will send the necessary emails.

It’s not about increasing the audience, but rather increasing the conversion rate.
One of the recommendations for this is to make the checkout process easier for users, so option D is the opposite.
By using dynamic content, we can better capture users’ attention, and a cart abandonment campaign is always a good strategy to increase the conversion rate.

The brand style guide can be applied to both emails and landing pages without the need to separate into two BUs.
A BU can have multiple IPs and domains.
We can have multiple From Names and From Email Addresses within the same BU, and we can even configure them dynamically.
However, we do need to have two separate BUs if the company wants email unsubscribes to be managed separately. For Enterprise 2.0, the account can be configured so that the unsubscribe applies to all BUs or only the BU from which the unsubscribe is requested.

Answer A cannot be correct because: The IP of the new BU does not inherit the reputation of the other BU, and if necessary due to the volume of sends, an IP warm-up process will be required.
Answers B and E cannot be correct because: There can only be one SAP per BU, and an SAP cannot be inherited from the parent BU.
Answers C and D are precisely the features that the SAP brings.

* Journey A with Data Extension A as input: After sending the email, a waiting period, and the Engagement Split, there will be an Update Contact Activity that will inject records into Data Extension B, which serves as the input for Journey B.
* Automation, scheduled to run daily, for example, with a Query Activity that joins Data Extension B with A to obtain the additional field information for each contact in order to personalize an email. Journey B will be configured to only allow new records from the input Data Extension B.

We are not being consulted about the data model for the use case but rather just the configuration of Activities within the Journey that sends the reminders.
In that case, and since we need to send emails 24 hours and 48 hours after registration if activation has not occurred:

At the 24-hour mark after the contact enters the journey, we will evaluate if they have activated their account. If they have, they will exit the journey, and if they have not, they will receive the first reminder.
24 hours after receiving the first reminder (48 hours after entering the Journey, i.e., the registration date), the same evaluation will be conducted with the same logic for sending and exiting the Journey.

Data retention policies can be applied to a Data Extension at any time or can be modified. However, once activated, it cannot be deleted.
That being said, we can delete records older than 12 months and then configure the retention period, or simply leave it configured so that records older than a certain period will be automatically deleted by Marketing Cloud in accordance with the retention policy.

The first thing is to know which offer is desired to be presented to the customers because that will determine what other criteria need to be considered when defining the audience, apart from them being customers who have interacted. Factors such as availability by regions or the type of products to which it will be applicable can modify the audience.

Assuming that we are going to connect the ‘Orders’ Data Extension with Contacts in a 1:1 relationship (Contacts.ContactKey = Orders.CustomerId), the next step would be:
Connect ‘Orders’ with ‘Order_Details’ in a 1:1 relationship (Orders.OrderId = Order_Details.OrderId)
Connect ‘Order_Details’ with ‘Products’ in a 1:1 relationship (Order_Details.ProductId = Products.ProductId)
This way, we connect all the Data Extensions in a 1:1 relationship, always in the following order:
Contacts
Orders
Order_Details
Products

The Attribute Groups in Contact builder can contain one or more Data Extensions related within each other or related to Marketing Cloud Contacts. It can be created from scratch or using templates.

The intention of communications should always be identified in order to separate commercial communications from transactional sends. Translated into Send Classifications, we will have two, one for each type of communication. Both Send Classifications can share the Sender Profile (email and sender’s name), and even the Delivery Profile (IP for sending), but the nature of the communication (commercial/transactional) should be specified in the Send Classification. Similarly, to avoid confusion when configuring sends, we should indicate in the Name of the Send Classification whether it is commercial or transactional.

The order ID field is conducive because it places all of the items that the customers want under one order. You can imagine how problematic it would be if the rules were set in different areas. It will be harder for the company to track the orders of each customer. This may lead to people receiving items that they did not order or not getting any of the things that they ordered at all. The order ID field will make everything more organized and correct.

The fewer mistakes that the company makes in processing orders, the happier the customers will be with their shopping experience.

In Data Designer, within Contact Builder, we would create an Attribute Group where we would join different tables to replicate the customer’s relational data model.

Send Logs are Data Extensions that store sending data and can be configured with a data retention policy to store records for a specific period of time. They can be included in Measures and Filters for analysis and segmentation purposes.

The solution would be to add a filter based on the boolean field of consent so that only contacts who have given their consent (checked checkbox) are synchronized. The synchronization between clouds that refreshes the synchronized Data Sources is done every 15 minutes. Then, it is just a matter of segmenting it through an SQL in Automation Studio or filtering it to obtain a sendable Data Extension with the desired audience for each Journey.

Considering that technical resources are limited, the simplest solution is to add a Dynamic Content Block where we can display one image or another based on the value of the field that captures the gender.

Among the strategies to increase the CTR (Click-Through Rate) of the sends are testing different subject lines as well as experimenting with different hours/days to evaluate the open rates.

We need to determine how we will display the From Name for both regions (USA and Canada) and which Send Classification (commercial or transactional) should be used for the sends.

A Journey sending, for example, an email with two different CTAs for positive/negative response, followed by a Wait Activity, and after that, an Engagement Split that evaluates whether the contact has clicked on the negative response CTA, adding a Case Creation Activity in the YES branch of the split to create a case in Salesforce.

Configure a transactional triggered email that is triggered via API when an order is received. The emails can be personalized based on the information provided in each API call related to each contact.

We will use Personalization Strings related to the MobileConnect Demographics table.

Since we want to compare 3 creatives, the first thing we need to do is separate the audience into 3 random blocks (Random Split).
Once the audience is separated, we will send the creatives (Send email) and define the wait time (Wait) we give to the contacts to interact with the email they have received.
We evaluate the interaction (Engagement Split), merge all those who have interacted into a single branch (Join), and send the second email (Send email).

We can create templates for each language or customize the templates based on the subscriber’s language either through dynamic content blocks based on rules or using the Enhance Dynamic Content tool.
In any case, the language field must be captured as an attribute in the Data Extension or in the subscriber’s attributes.

A Data Extension can have more than 50 fields (attributes), and an Attribute Group can contain multiple Data Extensions.
Lists are used when the data model requires a limited number of subscriber attributes. Additionally, an Attribute Group does not contain Lists, but rather Data Extensions.

When SAP is configured in the Business Unit, both the links in the emails and the images uploaded in Content Builder will have the domain configured for SAP.

There is no data view that captures tracking for Push sends.
On the other hand, a Tracking Extract is only for email sends, and using other configurations of a Data Extract Activity different from Tracking Extract in Automation Studio, we could obtain information about Push but not about SMS.
The sending history of a contact is not queryable.
Therefore, the solution would be to consult the Send Logs that have been created for each of the three types of sends. If we cannot combine methods (which would be quite common in reality), it is the only option we can use for all three types.