Marketing-Cloud-Intelligence Sample Questions Answers

Typically, 'Campaign Key' is a unique identifier for a specific marketing campaign, while 'Media Buy Key' refers to the purchases of advertising space associated with that campaign. A campaign can have multiple media buys, so the relationship is many-to-one, with many media buys (Media Buy Keys) associated with a single campaign (Campaign Key).

Option 4 presents two calculated measurements for 'Group Min Cost' with 'MIN' and 'AVG' aggregations. This approach aligns with the client's need for the minimum and average media cost values. 'Group Min Cost 4 MIN' will calculate the minimum media cost across the 'Media Buy Key', while 'Group Min Cost 4 FINAL' will average these minimum costs at the 'Campaign Key' level. This will yield the desired result where minimum costs are calculated at the Media Buy Key level and then averaged at the Campaign Key level.

Since the data sources are linked by shared Media Buy names and all other measurements are mapped to appropriate fields without additional manipulations, each unique Media Buy Name from Google DV360 will pair with its corresponding Media Buy Name in Google Campaign Manager. The number of records in the merged table will equal the number of unique Media Buy Names in Google DV360, provided there is a matching name in Google Campaign Manager. The sample shows 4 unique Media Buy Names in Google DV360, thus resulting in 4 records.

Based on the Opportunity file, the Opportunity Stage of 'Interest' occurs 3 times across unique Opportunity Keys. Since the pivot table is filtered to present the entire month of January and the Opportunity Stage 'Interest' is listed three times with different Opportunity Keys, the count of opportunities in the 'Interest' stage would be 3.

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.

To extract specific elements from a string in Marketing Cloud Intelligence, such as the second position of a Campaign Name with multiple delimiters, several harmonization methods can be employed:

Calculated Dimensions: These allow for the creation of custom dimensions using expressions or formulas that manipulate existing data. A calculated dimension can be designed to parse and extract segments of a string based on delimiters.

Patterns: This method involves defining a pattern or regex (regular expression) that matches and isolates the desired portion of the string. Patterns are highly effective for strings with complex structures and varying delimiter types.

Mapping Formula: Similar to calculated dimensions, mapping formulas provide a way to apply a transformation or extraction rule to data fields directly within data streams, enabling targeted data extraction like the desired 'Delux' from the Campaign Name.

These methods enable the implementation engineer to accurately segment and extract the needed data from complex string fields efficiently.

To set Google DV360 as the source of truth for cost:

The cost data from Google DV360 should be prioritized, which means ensuring that the 'Cost' field in Google Campaign Manager is not mapped or is mapped with less priority compared to Google DV360.

Given that DV360 is to be the source of truth, you do not want competing cost data from Campaign Manager. Unmapping 'Cost' in Google Campaign Manager prevents conflicting data between the two sources and upholds the integrity of the cost data coming from Google DV360.

Scalability: Using Calculated Dimensions allows the client to apply the same harmonization logic to future data streams, ensuring consistency and reducing the need for individual adjustments.

Ease of Maintenance: With the logic centralized in Calculated Dimensions, any adjustments or updates are applied in one place, simplifying ongoing management.

Performance: Calculated Dimensions can improve dashboard performance because their values are pre-computed and stored, reducing the need for real-time calculations when loading dashboards.

In Marketing Cloud Intelligence, the "Media Buy Key" is typically associated with the purchase details of a media campaign, such as the platform, audience, and budget. The "Creative Key" relates to the specific creative asset used within a campaign, like an image, video, or text. A single media buy can have multiple creative variations to test performance or to target different audiences, leading to a one-to-many relationship.

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'.

pivot table is filtered on January 11th, we refer to the Opportunity file and see that there are no records for January 11th. Thus, there would be zero opportunities in the Confirmed Interest stage on that date. The Salesforce Marketing Cloud Intelligence's pivot table feature allows for the display of counts of entities based on the filtered criteria, which in this scenario would show zero since no records exist for the filtered date. Reference: Salesforce Marketing Cloud Intelligence documentation on pivot table functionalities.

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.

In Marketing Cloud Intelligence, joining two files requires a common field to be mapped as the same entity. If "employee_name" is consistently mapped across both data streams, it can serve as the basis for the join, regardless of whether "employee_id" is mapped. The choice of which file serves as the Parent stream depends on the use case and the desired reporting structure, but technically, either could serve as the Parent.

The source file shows data related to media buys, including a 'Media Buy Key', 'Media Buy Name', 'Campaign Key', and 'Site Key', among other fields. If only three rows were added, and the discrepancy is due to a missing field, it's likely that 'Campaign Key' is the field not mapped, because it is crucial for linking related records in the data stream. Without the 'Campaign Key', the system cannot associate the media buy data with specific campaigns, leading to a potential loss of data rows during ingestion.