A client has integrated the following files:
File A:

File B:

The client would like to link the two files in order to view the two KPIs ('Tasks Completed' and 'Tasks Assigned) alongside 'Employee Name' and/or
'Squad'.
The client set the following properties:
+ File A is set as the Parent data stream
* Both files were uploaded to a generic data stream type.
* Override Media Buy Hierarchies is checked for file A.
* The 'Data Updates Permissions' set for file B is 'Update Attributes and Hierarchy'.
When filtering on the entire date range (1-30/8), and querying employee ID, Name and Squad with the two measurements - what will the result look like?
A)

B)

C)

D)

In Marketing Cloud Intelligence, when linking two data streams, the parent data stream (File A) provides the main structure. Since 'Override Media Buy Hierarchies' is checked for File A, the hierarchies from File B will be aligned with File A. Given 'Data Updates Permissions' set for file B as 'Update Attributes and Hierarchy', this means that attributes and hierarchy will be updated in the parent file based on the child file (File B), but the child file's metrics won't be associated with the parent file's date.
Hence, when filtering on the entire date range (1-30/8), the resulting view will align with the structure of the parent data stream, showing the KPIs ('Tasks Completed' from File A and 'Tasks Assigned' from File B) alongside the employee names and squads from the respective files. Since the employee IDs align, the data can be linked properly. However, since the dates do not align (File A data is from 01/08/2019 and File B from 15/08/2019), only attributes from File B will be updated without date association.
The result will look like Option C, where the employee names are corrected based on File B's data, the squads are added from File B, and the tasks_completed and tasks_assigned are displayed from their respective files. The tasks_assigned from File B are shown without date association as File B's date doesn't match with File A's.
An implementation engineer is requested to integrate the following files:
File A:

File B:

The client would like to link the two files in order to view the two KPIS (Tasks Completed' and 'tasks Assignmed') alongside'Employee Name' and/or 'Squard'.
A Parent-Child configuration was set between the two.
Which two statements are correct?
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.
Client has provided sample flies of their data from the following data sources:
Google Campaign Manager

Below are the requirements from the client and additional information:
* The sources are linked to each other by shared Media Buy names.
* In addition-to the mutual Media Buys, the sources contain campaign and site values. However, the client would like to see the campaign/site values coming from Google CM and not from Google DV360.
* The source of truth for cost is Google DV360.
As a first step, a Parent-Child relationship was created between the two files, and the following mapping was performed, within both data streams:

Please note:
* All other measurements were mapped as well to the appropriate fields.
* No other mapping manipulations or formulas were implemented.
How many records will the merged table hold?
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.
A client has provided you with sample files of their data from the following data sources:
1.Google Analytics
2.Salesforce Marketing Cloud
The link between these sources is on the following two fields:
Message Send Key
A portion of: web_site_source_key
Below is the logic the client would like to have implemented in Datorama:
For 'web site medium' values containing the word ''email'' (in all of its forms), the section after the ''_'' delimiter in 'web_site_source_key' is a 4 digit
number, which matches the 'Message Send Key' values from the Salesforce Marketing Cloud file. Possible examples of this can be seen in the
following table:
Google Analytics:

Salesforce Marketing Cloud:

The client's objective is to visualize the mutual key values alongside measurements from both files in a table.

In order to achieve this, what steps should be taken?
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.
What is the relationship between "Media Buy Key" and "Creative Key?
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.
Lynelle
4 days agoTheola
12 days agoEdwin
20 days agoLennie
27 days agoTresa
1 month agoLavonna
2 months agoVan
2 months agoVirgina
2 months agoRamonita
2 months agoNovella
3 months agoKristine
3 months agoRodrigo
3 months agoSusy
3 months agoDelbert
4 months agoBurma
4 months agoTeddy
4 months agoAdela
4 months agoEva
5 months agoDalene
5 months agoStephanie
5 months agoAliza
5 months agoJanella
6 months agoSommer
6 months agoYuette
6 months agoAnnalee
6 months agoAdela
7 months agoGerald
7 months agoAlline
9 months agoJoaquin
10 months agoJenelle
11 months agoGaston
12 months agoLeota
1 year agoVincent
1 year agoDewitt
1 year agoSimona
1 year agoSang
1 year agoNana
1 year agoStanford
1 year agoClare
1 year agoMaira
1 year agoJuliana
1 year agoTimothy
1 year agoYvonne
1 year agoTrina
1 year agoMarla
1 year agoPeggie
1 year agoYuki
1 year agoDerrick
1 year agoVincenza
1 year agoAmie
1 year agoAmber
1 year agoRosenda
1 year agoCarol
1 year agoThurman
1 year agoLino
1 year agoDerick
1 year agoJules
2 years agoCherri
2 years agoHillary
2 years agoIluminada
2 years agoAngelyn
2 years agoGlen
2 years agoQuinn
2 years agoRuby
2 years agoShonda
2 years agoWilliam
2 years agoLudivina
2 years agoTiera
2 years agoLore
2 years agoVal
2 years agoEva
2 years ago