Marketing-Cloud-Intelligence Marketing Cloud Intelligence Accredited Professional Exam Questions and Answers

Since the pivot table is filtered on January 11th and the provided Opportunity file does not show any records dated January 11th, there are zero opportunities in the Interest stage for that date. Salesforce Marketing Cloud Intelligence allows users to create pivot tables and filter data basedon specific criteria, such as dates. In this case, the filter would exclude all rows that do not match the specified date, resulting in a count of zero for the Interest stage. This would apply to any stage since there are no records for January 11th. Reference can be made to Salesforce Marketing Cloud Intelligence documentation on filtering and pivot tables.

Based on the Opportunity file and considering the filter dates from January 7th to 10th, the different stages presented are 'Interest', 'Confirmed Interest', and 'Registered'. This makes a total of 3 different stages that would be presented in the pivot table. Salesforce Marketing CloudIntelligence allows for the creation of pivot tables that can display counts of entities across different dimensions, in this case, Opportunity Stages. Reference to Salesforce Marketing Cloud Intelligence documentation that covers data mapping and pivot table creation would support this conclusion.

Unstable measurements refer to metrics that are not aggregated in a standard manner across different grains of data, which can result in inconsistent or unpredictable results when reporting across different dimensions or time frames.

• Option C describes a scenario where measurements have manual (Not Auto) aggregation settings, meaning they do not automatically adjust to theaggregation level of the report. Combined with a Granularity setting of 'None', this can lead to instability because the metric isn't bound to a specific granularity, which can cause data inconsistencies or misinterpretations when analyzed at varying levels of detail.

By harmonizing the Objective field within data stream mapping, an organization can benefit from:

• Ease of Maintenance: Harmonization allows for consistent naming conventions across different data sources and streams. This means when business logic or naming conventions change, updates can be made in one place and consistently applied across all data streams. It also reduces the complexity of managing multiple streams and ensures data consistency, which is vital for accurate reporting and analysis.

The correct table would be Option B. The harmonization process would identify the 'Market' from the campaign or media buy name based on the delimiter and position rules specified in the naming conventions. The harmonized 'Market' would then be matched against the classification file and validation list. If a value does not match the validation list, it would return 'Not Valid', and if it's not present in the classification file, it would return 'Unclassified'. Option B is the only table showing the 'Not Valid' category which aligns with the logic specification provided.

In Marketing Cloud Intelligence, when a file is uploaded as a generic dataset type and mapped accordingly, each unique combination of the mapped fields results in a separate row in the database. The file in question has been mapped with 'Day' to 'Day', 'Web_site_source' to 'Main Generic Entity Attribute 01', and 'Page Views' to 'Generic Metric 1'. The 'web_site_key' and 'web_site_name' are not mapped and thus, won't affect the row count.

Since there are 4 unique combinations of the mapped fields in the uploaded file (each day and source combination is unique), Marketing Cloud Intelligence will store 4 rows after ingestion, corresponding to each unique combination of 'Day' and 'Web_site_source'.

For the given use case, where the Twitter Ads data stream needs to be enriched with classifications from three other sources, the correct implementation would involve creating links between the various fields across these files.

Option A is correct because it shows the correct usage of the fields from the classification files:

• "Creative ID" in the Creative Classification file is linked to the "Creative Key" in the Twitter Ads data, allowing for enrichment with creative details.
• "Placement ID" in the Placement Classification file is linked to a corresponding field in the Twitter Ads data, allowing for placement details to be added.
• "Category" in the Campaign Category Classification file is linked back to "Campaign Category" in the Twitter Ads data, thus enriching the campaign data with the correct categories.

This configuration correctly uses VLOOKUP to enrich the Twitter Ads data stream with additional details from the classification files, aligning with best practices for data integration and enrichment in Marketing Cloud Intelligence.

In Marketing Cloud Intelligence, attributes refer to characteristics of the data that describe the environment or context but do not change within the scope of the data being analyzed. 'Device Category' is typically an attribute as it describes a characteristic of the device used and doesn't vary within a given session or user interaction. In contrast, variables are typically metrics or dimensions that can change value or be measured.

Overarching Entities in Salesforce Marketing Cloud Intelligence are designed to provide a high level of data organization that spans across multiple data streams. The key points about Overarching Entities are:

• B. Relationship Types: Overarching entities can have either a Many-to-Many or One-to-Many relationship with the main entity, which allows for flexible data modeling and relationship definitions based on the nature of the data and how it should be analyzed and reported.
• C. Acting as Main Entity: They can serve as a main entity in certain situations, enabling a shift in perspective for data analysis. This can be particularly useful when there is a need to view data from a different dimension that is more aligned with business requirements.
• E. Storage Level: The values of these entities are not tied to any single data stream but are maintained at a workspace level, ensuring that they can be applied consistently across different datasets, which is critical for maintaining data integrity and ensuring that classifications are applied uniformly.

To avoid data loss and ensure each meeting is uniquely identified and its details are preserved, two mappings are recommended:

Option A:

• ‘Meeting Code’ should be mapped to the 'Main Generic Entity Key' to uniquely identify each meeting.
• ‘Meeting Name’ should be mapped to a 'Main Generic Entity custom attribute' to store additional information about the meeting.

Option E:

• Concatenation of ‘Meeting Code’ and ‘Meeting Name’ should be mapped to ‘Main Generic Entity Key’. This ensures a unique identifier for each meeting is created combining both pieces of information, preventing any mix-ups between meetings with similar codes or names.
• Additionally, mapping ‘Meeting Code’ and ‘Meeting Name’ to their respective 'Main Generic Entity Attribute' fields will allow for more detailed filtering and reporting capabilities within Marketing Cloud Intelligence.

LiteConnect is a feature in Salesforce Marketing Cloud Intelligence that allows users to bring external data into the platform quickly and easily. Here are the correct statements regarding LiteConnect:

• A.LiteConnect allows for a quick setup by not requiring detailed identification of entities, keys, or categorization. Users can upload files without having to conform to the standard data model, which speeds up the process of data integration.
• B.With LiteConnect, datasets are uploaded in their native format and do not conform to the standard data model of Marketing Cloud Intelligence. This means that the original structure of the dataset is maintained, and there is no need for extensive transformation or mapping upon the initial data import.

For C and D: While LiteConnect datasets might not conform to the standard data model initially, there are capabilities within Marketing Cloud Intelligence to further categorize and harmonize this data if needed. Therefore, C is not entirely correct, and D is incorrect because harmonization can indeed occur at a later step.

The EXTRACT function is used to split a string based on a delimiter and return the segment at the specified position. The campaign names are structured with the segment of interest followed by an '@' sign. Therefore, the formula needs to extract the segment before the '@'.

• The correct formula is: EXTRACT(csv['campaign_name']; '@', 1). This will take the 'campaign_name' field, split it at the '@' sign, and return the first segment (position 1), which is the three-letter code that is required. The other options are incorrect because they do not properly specify the delimiter and the segment position in the way needed to achieve the desired outcome.

For the field 'Magician', the engineer is required to follow a logic that extracts a value from 'Campaign Name' and checks against a validation list for specific values ('Messi' or 'Ronaldo'). If those values are not found, it should instead extract from 'Media Buy Name'. To accomplish this, the engineer should:

• Use the created Pattern for 'Campaign Name'.
• Create a second Pattern for 'Media Buy Name' to capture the fallback values.
• Apply two Classification Rules to the Harmonized Dimension: one for the value 'Messi' and another for 'Ronaldo'. This is to check the extracted 'Campaign Name' against these specific values.

These steps ensure that the 'Magician' field will be populated with the correct values from the respective data streams following the specified logic.

CPC (Cost per Click) is a calculated metric that should be created using a custom measurement based on the formula provided (Cost / Clicks). This calculation does not require a change in the aggregation setting because it is derived from other base metrics that are already aggregated appropriately. In Salesforce Marketing Cloud Intelligence, custom measurements are used to create new metrics from existing data points, and the system will use the underlying data's aggregation to perform the calculation. References: Salesforce Marketing Cloud Intelligence documentation on creating custom measurements and calculated metrics.

To calculate Cost per Campaign Advertiser using a VLOOKUP formula, the client needs to look up the 'Cost' from Data Stream 2 based on a matching 'Media Buy Name' in Data Stream 1. Option A shows that 'Media Buy Name' is the lookup value, which is correct. The 'Campaign Advertiser' is then linked to the 'Cost' from Data Stream 2 through the VLOOKUP formula applied to the 'Media Buy Custom Attribute 01' in Data Stream 2. This setup will correctly associate the cost with the campaign advertiser.