Salesforce Marketing-Cloud-Consultant Dumps

By using Tracking Extract, File Transfer, and Import activities from Automation Studio, you can extract the data from the subscribers who have had emails fail due to held status within the last 60 days [1][2], and then transfer the data into a data extension that can be used as an Entry Source for Journey Builder. This will allow you to create an SMS message that can be sent to the subscribers to ask them to update their email address. Additionally, Automation Studio provides the ability to schedule and automate the process so that the data is regularly updated and the SMS message is sent on a regular basis. For further information, please refer to the following Salesforce documentation:

• Automation Studio Overview:  &type=5 • Automation Studio Activities:  &type=5 • Data Extensions Overview:  &type=5 • Journey Builder Overview:  &type=5

Two actions that would successfully write send time variables to their Send Log are:

• Match an AMPscript variable name to a Send Log field. This action will allow the customer to write the value of an AMPscript variable to a corresponding field in the Send Log data extension. For example, if the customer has a Send Log field named ProductName and an AMPscript variable named @ProductName, then the value of @ProductName will be written to the ProductName field in the Send Log.
• Use the WriteToLog() AMPscript function in the content. This action will allow the customer to write one or more values to a specified field in the Send Log data extension using an AMPscript function. For example, if the customer wants to write the value of @ProductName and @ProductPrice to the ProductInfo field in the Send Log, they can use WriteToLog(“ProductInfo”,@ProductName,@ProductPrice) in their content.

Ensuring the send log is linked in an attribute group is not necessary for writing send time variables to their Send Log, as it is only used for creating relationships between data sources in Contact Builder. Enabling send logging to a data extension during send process is not an action that would write send time variables to their Send Log, as it is only a setting that enables or disables send logging for a specific email send. References: &type=5 &type=5

To send emails to loyalty members based on recent activity, a contact data entry source can be used to segment the data based on attributes and filters configured in Contact Builder. This allows for more flexibility and scalability than using a data extension entry source with an applied filter. References: &type=5 &type=5

To send SMS and push notifications together with emails as part of a new customer onboarding journey, Northern Trail Outfitters should use a GUID or another generated ID for Contact Key. A Contact Key is a unique identifier for each contact in Marketing Cloud across different channels and platforms. A GUID or another generated ID is recommended as a Contact Key because it is persistent, consistent, and channel-agnostic. References: &type=5

To capture open-ended feedback from customers via SMS and write it to a data extension, Northern Trail Outfitters should use a text-response message template with embedded AMPscript to capture the response. A text-response message template is a template that allows marketers to send a text message to a mobile number and receive a reply. AMPscript is a scripting language that allows marketers to perform complex tasks within messages, such as inserting data into a data extension. References: &type=5 &type=5

Synchronized data extensions are data extensions that are automatically populated with data from Sales Cloud objects using Marketing Cloud Connect. They can be configured with filters to limit the records that are imported based on criteria such as field values or record types. By using synchronized data extensions with a filter on the consent checkbox field, NTO can import their Sales Cloud data into Marketing Cloud and leverage it within Journey Builder. Synchronized data extensions can be refreshed as frequently as every 15 minutes, which meets the requirement of having no more than 30 minutes delay. References: &type=5 &type=5

Using an import activity to import a file from the SFTP can be used to maintain an auto-suppression list. An import activity allows users to import data from a file on the Marketing Cloud FTP into a data extension or list. An auto-suppression list is a type of exclusion list that prevents subscribers from receiving certain types of messages based on criteria such as email address, subscriber key, or domain. References: &type=5 &type=5

To inform NTO’s marketing manager if more than 1,000 records are ever imported through this automation, and prevent the sendable data extension from being updated that day, the consultant should place a Verification Activity between the import and SQL Query activity. A Verification Activity is an activity that allows marketers to verify if certain conditions are met before proceeding with the next activity in an automation. For example, a Verification Activity can check if the number of records in a data extension is above or below a specified threshold, and send an email notification or stop the automation based on the result. References: &type=5

A Verification Activity can be used to prevent emails from being sent if they exceed a certain number of contacts. A Verification Activity checks the number of records in a data extension or list and stops the automation if the number is above or below a specified threshold. References: &type=5

To fulfill the requirement that the data in the sandbox should never be mixed with data in production during testing cycles, Northern Trail Outfitters should implement two separate Marketing Cloud instances. A Marketing Cloud instance is an independent environment that contains its own data, configuration, and functionality. Having two separate instances for sandbox and production will ensure data isolation and security during testing cycles. References: &type=5

To send a welcome email to contacts when a contact record is added as a campaign member to a ‘Loyalty Member’ campaign in Sales Cloud, Northern Trail Outfitters should create a journey with a Salesforce Data entry source and an email activity. A Salesforce Data entry source allows marketers to inject contacts into a journey based on changes or events in Sales Cloud objects, such as campaign members. An email activity allows marketers to send an email message to contacts in a journey. References: &type=5 &type=5

To import the data, segment the data, and execute the daily sends as soon as the file is generated by the data lake instance, Northern Trail Outfitters should use a triggered automation that contains an import activity, a series of query activities, and a series of sends. A triggered automation can start when a file is dropped in a specified location, such as an FTP folder. An import activity can import the file into a data extension. A series of query activities can segment the data based on the criteria for different campaigns. A series of sends can send the emails to the segmented data extensions. References: &type=5 &type=5 &type=5 &type=5

To unify the messaging and branding of communications while still allowing personalization and timing of campaigns, Northern Trail Outfitters and its subsidiaries should use Distributed Marketing. Distributed Marketing is a tool that allows marketers to create consistent and compliant messages in Marketing Cloud and distribute them to Sales Cloud or Service Cloud users for sending. Distributed Marketing allows Sales Cloud or Service Cloud users to personalize and schedule messages based on their customer interactions and preferences. References: &type=5

Two options that would prevent the customer from duplicating records when implementing a Sales Cloud instance are:

• Get existing records updated with new Keys sourced from Sales Cloud instance. This option will allow the customer to update their existing records in Marketing Cloud with new keys that match their Sales Cloud records, such as Contact ID or Lead ID. This will ensure data consistency and avoid duplication across both systems.
• Continue as normal, as Marketing Cloud Contact Models will dedupe keys by Email Address. This option will allow the customer to continue using Email Address as their primary key in Marketing Cloud, and rely on Marketing Cloud Contact Models to dedupe keys by Email Address when syncing data from Sales Cloud. This will ensure data accuracy and avoid duplication within Marketing Cloud.

Uploading CSV with Migrated Subscriber Keys to All Subscribers will not prevent duplication, as it will create new records in Marketing Cloud with different keys than the existing records. Purging the current records and carrying on with new keys sourced from Sales Cloud will result in data loss and potential compliance issues. References: &type=5 &type=5

To send an email confirming opt-in when someone signs up for their emails via a form on their website, a triggered send data extension can be used to capture the form data and deploy the email. The triggered send data extension can be linked to a triggered send definition that contains the email creative and settings. The developer can use the SOAP or REST API to trigger the email from the website form, and the marketing team can change the email creative without involving the developer. References: &type=5 &type=5

Two considerations that should be made when using a File Drop Automation are:

• They may utilize an external FTP site. A File Drop Automation can be configured to use an external SFTP location as well as an Enhanced FTP location for file triggers.
• The directory is unable to be used by another File Drop Automation. A File Drop Automation can only use one directory for file triggers, and that directory cannot be used by another File Drop Automation.

The directory used by the file trigger can be inside or outside the import directory, as long as it is not used by another File Drop Automation. The directory can contain more than five file triggers, but only one file trigger can start an automation at any given time. References: &type=5

To initiate sends when contacts for select accounts are created, Northern Trail Outfitters should use a Salesforce Data Entry Source on the Contact Object. A Salesforce Data Entry Source is a feature that allows marketers to inject contacts into a journey based on changes or events in Sales Cloud objects, such as contacts or accounts. Using a Salesforce Data Entry Source on the Contact Object will allow Northern Trail Outfitters to trigger sends when a contact record is created for a specific account. References: &type=5

To send an email with personalized fields from multiple data extensions without coding experience, Northern Trail Outfitters should combine the data outside of Marketing Cloud and upload it into a sendable data extension. This will allow them to have all the required fields for personalization in one data source and avoid using complex scripting or queries to join and filter data from multiple data extensions.

Establishing data relationships and creating data filters would not help with personalization, as they are used for segmentation purposes. Creating SQL query activities would require coding skills and experience with SQL syntax. References: &type=5

• How many API calls are expected to be made at peak hourly rate? This question will help determine if they have enough API limits and bandwidth for importing large volumes of data via REST API into Marketing Cloud. The REST API has limits on how many requests can be made per hour per account based on license type and edition.
• Why do they require 10 years’ historical data in Marketing Cloud? This question will help determine if they have a valid business case and use case for importing large volumes of historical data into Marketing Cloud. Depending on their marketing objectives and strategies, they may not need 10 years’ historical data in Marketing Cloud, which could reduce their storage needs and costs.

What time of day are the API calls made is not relevant to determining a solution for importing large volumes of data via REST API into Marketing Cloud, as it does not affect how data is imported or processed. Whether someone needs to be notified if an error happens on import is not relevant to determining a solution for importing large volumes of data via REST API into Marketing Cloud, as it does not affect how data is imported or processed. References: &type=5

A SQL query is an automation studio activity that allows querying data from data extensions or data views using SQL statements. A data view is a system-generated table that stores information about subscriber actions, such as clicks, opens, bounces, etc. The _Click data view contains information about each click event for each subscriber in the last six months. By creating and executing a SQL query against the _Click data view, the customer can identify all subscribers who clicked on a link within any email sent within the last six months. References: &type=5 id=sf.mc_as_data_view_click.htm&type=5

The Transactional Messaging API can be used to send email to customers who log in for the first time on a new IP. The Transactional Messaging API allows for fast and reliable delivery of transactional messages, such as password resets, order confirmations, or account alerts. The message can include information related to the login IP by using personalization strings or AMPscript variables. References:

To use a simple segmentation strategy for identifying subscribers for their emails, Northern Trail Outfitters should use list model and groups in Single Send Journeys. List model is a method of storing subscriber information in lists rather than data extensions. Groups are segments of subscribers based on list attributes or behaviors. Single Send Journeys are journeys that allow marketers to send one-time messages to lists or groups using Journey Builder features. References: &type=5 &type=5 &type=5

To refresh the sandbox in their integrated account, Northern Trail Outfitters should perform the steps in the following order:

• Disconnect. This step will disconnect Marketing Cloud Connect from Sales Cloud and prevent data loss or errors during the refresh process.
• Refresh. This step will refresh the sandbox in Sales Cloud with new data and configuration.
• Reconnect. This step will reconnect Marketing Cloud Connect to Sales Cloud using the new sandbox credentials and settings.
• Synchronize. This step will synchronize data between Marketing Cloud and Sales Cloud using Synchronized Data Sources or Salesforce Data Entry Sources.
• Authenticate. This step will authenticate Marketing Cloud Connect users in both systems and enable full functionality of Marketing Cloud Connect.

References: &type=5

Supporting inbound messages in each country would require additional long code implementation for MobileConnect. A long code is a standard phone number that can send and receive SMS messages. Each country has its own regulations and requirements for long codes, so a single long code cannot be used for all markets. The other functionalities do not tie to additional long code implementation. References: &type=5

To choose a subscriber key for Marketing Cloud, Northern Trail Outfitters should use a value that is unique, persistent, and channel-agnostic. A CRM ID or a loyalty program number are both good options, as they meet these criteria and can be used to identify and track subscribers across different channels and platforms. Email and mobile device ID are not good options, as they are not unique or persistent (subscribers can change their email or device) and they are specific to one channel (email or mobile). References: &type=5

To utilize a Retention Policy for a data extension that stores web behavior data, two methods are possible. One is to delete data from the data extension prior to twelve months ago, then configure a Retention Period via Contact Builder. This will allow the data extension to keep only the data from the previous twelve months and delete any older data automatically. The other method is to replace the current data extension with a new data extension configured with a Retention Period. This will create a new data extension with the same fields and settings as the old one, but with a Retention Period enabled. References: &type=5 &type=5

The Contact ID field name should be included in the report in addition to email address when using a Send Flow in Content Builder. The Contact ID is a unique identifier for each contact in Sales Cloud and Marketing Cloud. It is required for sending emails to contacts using a Send Flow. The other field names are not required for this purpose. References: &type=5 &type=5

A contact is a person who interacts with a brand across one or more channels, such as email, mobile, web, etc. A contact is identified by a contact key, which is usually the same as the subscriber key in Marketing Cloud or the contact or lead ID in Sales Cloud. When users register with the mobile app, they will create new contacts in Marketing Cloud with their device IDs as contact keys. However, these contacts will not be associated with their contact keys in Sales Cloud until they are synchronized through Marketing Cloud Connect, which can take up to 24 hours. Therefore, newly registered users will create additional contacts in Marketing Cloud until they are matched with their existing contacts in Sales Cloud. References: &type=5 &type=5

The Deployment Manager extension product can be used to speed up the migration of data extensions and Journey Builder configurations between each environment. The Deployment Manager allows users to create packages of Marketing Cloud assets and deploy them across different business units or accounts. The Deployment Manager supports data extensions and journeys as well as other assets such as emails, templates, automations, and content blocks. References: &type=5

To send a special discount offer to engaged customers on their email list, Northern Trail Outfitters should resolve how to determine engagement prior to generating the audience. Engagement is a measure of how customers interact with emails, such as opens, clicks, or conversions. Different criteria and thresholds can be used to define engagement, such as recency, frequency, or duration of interactions. Determining engagement will help Northern Trail Outfitters segment their audience and target their offer more effectively.

What the offer will be, when to send the email, and who the offer come from are important factors for designing and delivering the email, but they are not relevant for generating the audience based on engagement. References: &type=5

To inject customers into journey B based on email engagement in journey A, Northern Trail Outfitters should use an engagement split followed by a contact activity in journey A. The engagement split can evaluate if customers opened or clicked the email in journey A. The contact activity can update a boolean field on an engagement data extension that indicates if customers are eligible for journey B. Then, an automation can run a query activity to select the customers who have the boolean field set to true and inject them into journey B. References: &type=5 &type=5

To select an audience of subscribers who have made purchases in the last 6 months, but are yet to be loyalty members, Northern Trail Outfitters should use Contact Builder Attribute Groups. Attribute Groups are collections of data extensions and data sources that are linked by common fields or attributes. Attribute Groups allow marketers to create segments and filters based on data from multiple sources, such as purchase data and loyalty data. References: &type=5

To encourage customers who made a purchase on their website without leaving a review to come back and review their purchase, Northern Trail Outfitters should use Google Analytics 360. Google Analytics 360 is a tool that allows marketers to measure website activity and behavior, such as purchases and reviews, and create audiences based on those metrics. These audiences can then be used as entry sources for journeys in Marketing Cloud that send targeted messages to customers. References: &type=5

To set up a real-time, API-driven way to be alerted when transactional messages fail to send out of Marketing Cloud, Northern Trail Outfitters should have an external system to receive and confirm callback and subscriptions. Callbacks are notifications that Marketing Cloud sends to an external system when certain events occur, such as message failures or bounces. Subscriptions are requests that specify which events and messages an external system wants to receive callbacks for. References:

A verification activity is an automation studio activity that allows checking the record count or field value of a data extension and sending a notification email if it meets certain criteria. A filter activity is an automation studio activity that allows filtering records from a source data extension into a target data extension based on filter criteria. By using these two activities in an automation, NTO can monitor available coupon codes in their coupon data extension and send a notification email to their email specialist if the available coupon count falls below 500. An import activity is used to import data from an external file or data source into a data extension, which is not relevant for this use case. A data extract activity is used to extract data from a data extension or data view into a file, which is also not relevant for this use case. References: &type=5 &type=5

Three considerations that should be made before implementing MobileConnect are:

• Long and Short Codes are not available for all countries. Long codes are local phone numbers that can be used for sending SMS messages in some countries, while short codes are special numbers that can be used for sending SMS messages in other countries. However, not all countries have long codes or short codes available or supported by MobileConnect.
• Inbound messaging only works with local Long or Short Codes. Inbound messaging is the ability to receive SMS messages from subscribers in response to outbound messages or keywords. This feature only works with local long codes or short codes that match the country of the subscriber’s mobile number.
• Not all countries are supported by MobileConnect. MobileConnect relies on mobile operators and aggregators to deliver SMS messages to different countries, but not all countries have these services available or supported by MobileConnect.

NTO would not be charged by mobile operators directly for messages, as they would pay for message credits or bundles through Marketing Cloud billing. Opting in for messages can be done via inbound message or other methods, such as web forms or APIs. References: &type=5

To send notifications to customers when their orders are ready for in-store pickup via SMS or email depending on their communications preference, Northern Trail Outfitters should use a Journey Builder multi-step journey with an API entry event and a decision split. A Journey Builder multi-step journey allows marketers to create personalized customer experiences across different channels and platforms. An API entry event allows marketers to inject contacts into a journey based on real-time events or data from external systems, such as order status updates. A decision split allows marketers to route contacts to different paths or activities based on their attributes or behaviors, such as communications preference. References: &type=5 &type=5 &type=5

 To simplify the sending process using Marketing Cloud with as little additional setup as possible, the customer should create a journey and use Salesforce Data and the Reports object as the entry source. This will allow them to use their existing complex reports in Sales Cloud as criteria for injecting contacts into the journey and sending them emails. References: &type=5

Two potential reasons for SMS responses getting the default keyword response rather than the appropriate next keyword response are:

• Responses are not sent within the Conversation Window. The Conversation Window is a setting that defines how long MobileConnect waits for a response from a subscriber after sending an outbound message. If a subscriber responds after the Conversation Window expires, MobileConnect treats their response as a new inbound message rather than part of an ongoing conversation.
• Next keyword was not specified on the outbound message. The Next Keyword is a setting that defines what keyword MobileConnect expects from a subscriber after sending an outbound message. If a subscriber responds with a different keyword than what MobileConnect expects, MobileConnect treats their response as a new inbound message rather than part of an ongoing conversation.

Responses containing “stop” in the message content will not get the default keyword response, but rather an opt-out confirmation message. Responses sent with AMPscript in body will not affect how MobileConnect handles responses, as AMPscript is only evaluated at send time. References: &type=5 &type=5

Three tasks that a consultant would suggest for using Journey Builder instead of Automation Studio are:

• Building simple segmented campaigns without SQL queries. Journey Builder allows marketers to create simple segmented campaigns using filters and rules without writing SQL queries. Automation Studio requires SQL queries for creating complex segments using data extensions.
• Designing decision logic via an intuitive user interface. Journey Builder allows marketers to design decision logic using activities such as decision splits, engagement splits, or random splits via an intuitive user interface. Automation Studio requires scripting or coding for creating decision logic using activities such as script activities or verification activities.
• Setting behavior-based goals. Journey Builder allows marketers to set behavior-based goals using criteria such as email opens, clicks, conversions, or custom events. Automation Studio does not have a feature for setting behavior-based goals.

Processing zipped encrypted files containing subscriber data is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as file transfer activities or import file activities that can handle zipped encrypted files. Creating customer segments from multiple data extensions is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as query activities or filter activities that can create customer segments from multiple data extensions. References: &type=5 &type=5

The subscriber key is a unique identifier for each subscriber in Marketing Cloud. It is used to track subscriber preferences, behaviors, and attributes across channels and business units. If the previous send used email address as a subscriber key, it would not match the subscriber key in Sales Cloud, which is usually the contact or lead ID. Therefore, the email opt out status would not be synchronized between Marketing Cloud and Sales Cloud, and the customer could receive an email through MCC even after unsubscribing from the previous send. References: &type=5

To query Marketing Cloud for send data across SMS, Push, and email, Northern Trail Outfitters should use _Send Data Views. Data Views are system-generated tables that store tracking and system data for different channels and platforms in Marketing Cloud. _Send Data Views contain information about email sends, SMS sends, and push sends across different business units and accounts. References: &type=5

Datorama is a product that enables marketers to connect and unify their data sources, visualize and analyze their data, and optimize their marketing performance. Datorama can help NTO centralize their analytics data from Marketing Cloud, Sales Cloud, and other sources, and provide insights and recommendations to drive return on investment and growth via their marketing sends. References: &type=5

To maintain a good sender reputation, Northern Trail Outfitters should have one dedicated IP address for every 100,000 messages send per month. This will help them avoid IP throttling and blacklisting issues. A shared IP address is not recommended for their volume, and having multiple SAPs for different types of sends is not necessary. They should also send consistently and avoid large spikes or drops in their sending volume. References: &type=5 &type=5

To use a custom sending domain and maintain deliverability for Cloud Kicks, Northern Trail Outfitters should use a Sender Authentication Package (SAP) for Cloud Kicks. A SAP is a tool that allows marketers to authenticate their emails with their own domain name and branding elements, such as links and images. A SAP also helps improve deliverability by increasing sender reputation and avoiding spam filters.

A new SAP for NTO is not needed, as they already have one for their existing brand. A private domain is not recommended for Cloud Kicks, as it does not provide full authentication or branding benefits as a SAP does. References: &type=5