For a successful migration from a legacy solution to Salesforce Media Cloud, it's important to first identify the relevant legacy data objects and then map them to the corresponding objects within the Media Cloud data model. This mapping may involve both standard objects provided by Media Cloud and custom objects that may need to be created to accommodate specific data or functionality not covered by the standard model. This approach ensures a seamless transition of data, preserving its integrity and maintaining continuity of operations. It's also crucial to consider the relationships between objects and any specific business logic that needs to be replicated or adapted in the new environment.
References:
Salesforce Data Migration Guide: https://developer.salesforce.com/docs/atlas.en-us.dat.meta/dat/ Salesforce Media Cloud documentation: https://www.salesforce.com/products/media-cloud/overview/

To meet the customer's requirements for an ad placement of a vertical banner with specific size and content attributes, the fields that need to be configured in theAd Creative Size Typeobject areWidth and Height.
These fields allow for the specification of the banner's dimensions (120x600), which is crucial for ensuring that the ad creative conforms to the required size for effective display. The position (left or right) and content type (animatedGIF) would typically be managed within the ad serving platform or specified in additional fields or instructions associated with the ad creative but are not standard fields in the Ad Creative Size Type object.
References:
Salesforce Media Cloud documentation: https://www.salesforce.com/products/media-cloud/overview/ Salesforce Ad Creative Management Guide: Information available in Salesforce Media Cloud resources

During a Google Ad Manager (GAM) order orchestration, a media planner needs to complete some steps manually in the GAM server, including associating the creatives to a line item in GAM (A) and checking if creatives are loaded in GAM (D). These manual steps are necessary because they involve specific actions within the GAM interface that require human intervention, such as verifying creative assets and ensuring they are correctly linked to the appropriate ad campaign line items.References:
https://support.google.com/admanager/answer/179039?hl=en
https://www.salesforce.com/products/media-cloud/overview/

To represent the relationship between clients and their advertising agencies in Media Cloud, creating both advertisers and agencies as separate accounts, with contacts under each, is the most structured approach.
Utilizing the party model within this configuration allows for the explicit definition of each agency's role, including the designation of an agency of record. This setup enables clear identification and management of relationships between advertisers, their agencies, and individual contacts within those agencies, providing a comprehensive view of all parties involved.References:https://help.salesforce.com/

In mapping legacy system data models to the Media Cloud data model, the IDX Build Tool and IDX Workbench are the recommended tools. The IDX Build Tool helps in constructing and customizing data integrations, facilitating the alignment of legacy data structures with Salesforce's data model. IDX Workbench, on the other hand, provides a more interactive environment for managing and testing data mappings and transformations, ensuring seamless integration between legacy systems and Media Cloud. These tools are designed to streamline the integration process, making it easier for IT managers to transition their existing data into the Salesforce ecosystem.References:https://developer.salesforce.com/