Salesforce Marketing-Cloud-Intelligence - Salesforce Marketing Cloud Intelligence Accredited Professional Exam

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.

Parent-Child configurations in Marketing Cloud Intelligence are used to link different data tables based on shared key values, allowing for the relational organization of data across various streams. While this setup enhances data analysis and reporting by maintaining logical relationships between parent and child tables, it can also introduce performance issues. The complexity increases with the number of relationships and the volume of data, potentially slowing down query processing and data manipulation. Additionally, Parent-Child configurations facilitate the sharing of dimensions and measurements across linked tables, enhancing the data's usability without duplicating it.

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.

To create a linkage between Google Analytics and Salesforce Marketing Cloud data based on the "Message Send Key" and a portion of the "web_site_source_key," both values need to be harmonized into a common key. This is done by mapping the full Message Send Key from Salesforce Marketing Cloud and the extracted part of the web_site_source_key from Google Analytics to the same Custom Classification Key. This mapping will create a common identifier that can be used to combine the data from both sources for analysis and visualization.

With File A uploaded using the Ads data stream type, the client wishes to create a view incorporating data from Files B & C.

A false connection would occur if VLOOKUP in Data Stream B is used incorrectly to return “Day” and “Installs”. In this scenario, VLOOKUP might inaccurately link data based on MB Name between File B and File A or File C, which do not have a "Day" field to correctly join on. Moreover, "Installs" data in File B doesn't exist, so VLOOKUP cannot correctly return this information. The correct method would be to use the "Media Buy New Name" to link File B and File C since they both have this field, ensuring accurate connection and avoiding data mismatches or false connections.

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.

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.

For performance issues when loading a dashboard using CRM data stream type:

Pacing can create performance issues because daily rows for every lead and opportunity key can result in a very large number of rows, increasing load times.

Having only calculated measurements means there are no direct, mappable values to query against, which can increase the computational load and affect performance.

In Marketing Cloud Intelligence, discrepancies between the number of rows uploaded and the number of rows present in the source file can be caused by several factors. If all mapped measurements for a row are zero, that row may be excluded from the upload, as it does not contribute to the analytics. Additionally, if the main entity, which acts as the primary identifier for records, is not mapped, the system cannot correctly ingest the data as it lacks the necessary reference to organize and store the information.