Enhanced Technical Case Study (Mercedes Benz Integration)
Introduction
This case study aims to provide an in-depth look at the technical architecture and data flow involved in the integration of Blings.io SDK into Mercedes-Benz's customer engagement strategy. It emphasizes the creation of personalized video experiences while maintaining high standards of information security and data privacy.
Project Overview
Mercedes-Benz embarked on an innovative project to enhance customer engagement through a specialized web platform. This platform is designed to provide dealers with the ability to create highly personalized, interactive video experiences for their customers, leveraging Blings.io's advanced SDK.
Mercedes's inspiration story about this project and collaboration with Widmann vehicle dealer - Widmann impresses car buyers with a digital preview
Creation Page: Retailer Dashboard
The heart of this initiative is the Retailer Dashboard, accessible at Retailer Dashboard Download. This dashboard serves as the primary interface where dealers can input specific details, such as the Vehicle Identification Number (VIN) and various customization options. These options include selecting video content, textual elements, and visual settings like day/night views, roof presence, and language preferences.
Example Implementations
Video Playlist Example: An example of how the integration can be implemented to create a video playlist is showcased at this link. This implementation demonstrates the versatility of the Blings.io SDK in creating a series of personalized videos, each tailored to specific vehicle details.
Retailer Dashboard Implementation: A practical example of the Retailer Dashboard in action is seen at Retailer Dashboard. This implementation provides a glimpse into the seamless integration of the SDK, offering a user-friendly interface for dealers to create custom videos for different Mercedes-Benz models, like the SL-AMG
“ Mercedes-Benz single goal is to put our customers first. By adding MP5 videos to our portfolio, we were able to introduce an entirely new opportunity for dealerships to include video in their promotions delivering higher conversion rates and engagement. “
Olaf Stelter, Product Manager Vehicle Specification at Mercedes-Benz /developers
System Architecture and Data Flow
Overview of Architecture
Front-End Integration: The Blings.io SDK is integrated into the Mercedes-Benz digital platform as a client-side module. This integration is handled through client-side JavaScript, allowing it to seamlessly interact with the front-end elements of the website.
Blings SDK : Blings SDK is a web-based JavaScript code that is designed to generate MP5 videos on the fly, on the user’s device using real-time data. The SDK is hosted on Blings.io's CDN (Content Delivery Network), which ensures efficient distribution and reduced latency. Specifically, a dedicated folder within the Blings.io SDK is reserved for Mercedes-Benz. This dedicated folder contains a copy of the Blings.io SDK that is exclusively used by Mercedes-Benz, isolating it from updates and upgrades made for other clients.
Mercedes API Interaction: Mercedes-Benz utilizes its Vehicle Videos and Vehicle Images APIs to retrieve vehicle data crucial for video personalization. API management and client-side application usage are entirely handled within Mercedes' platform.
Blings Video Template: Blings MP5 template, essential for creating videos with the desired design, is hosted on Blings’ CDN. This template is created in Adobe AfterEffects and then transferred to Blings' no-code solution. This allows for the addition of programming logic, setting dynamic layers, incorporating necessary variables in the video, and establishing interactivity logic.
Client-side rendering: The Blings SDK includes a client-side rendering engine. This engine processes data and implements customization logic according to the MP5 video format.
Data Flow
Initial Request: When a dealer accesses the customization interface, the front-end webpage initiates by loading the Blings.io SDK from the CDN.
Data Input and Transmission: The dealer inputs the VIN and customization preferences. Subsequently, the Mercedes API is called, fetching all necessary data into the page memory. This data includes text based on language and market preferences, video-scenes vehicle specifications, vehicle images, footage, and URL links for CTA buttons
Processing and Dynamic Content Creation: The webpage activates the Blings SDK with the Mercedes video template ID and the fetched data.
An example of the JavaScript call is:
window.BlingsPlayer.create({
project: { id: "mercedes-video", },
data: apiFetchResult,
settings: { container: $('#video-holder') , autoplay: true, },
scenes: ["intro", "vehicle-specification", "offered packages", "outro-CTA"]
})4. Client-Side Video Rendering: The client-side rendering engine dynamically generates the video content, merging the template with the data.
5. Display and Interaction: The personalized video is displayed on the dealer's interface, allowing for review and additional customizations if needed
6. Implementation on Dealer’s CRM and Websites: Once the SDK configuration is approved, dealers can integrate it into their platforms. This integration allows them to enrich their websites and incorporate personalized texts into their customer communications via CRM marketing automation.
The implementation was very easy because the interfaces are very well documented. If we had any questions or suggestions, our contacts always responded quickly and helpfully. Our IT team also found it easy to adapt and enrich the automated content
Marcel Weigert, Widmann's Head of Passenger Car Sales Division
Information Security and Privacy
Secure APIs: Data transmissions between the dealer interface and the Mercedes database are secured through API endpoints, developed and managed by Mercedes. This data is transmitted securely within Mercedes' platform (between the database and the web app), ensuring that there is no exposure to external systems
Client-Side Processing: Based on Blings’ patented technology, the video processing is executed client-side only, which significantly minimizes data exposure and enhances security.
Data Privacy Compliance: The architecture is meticulously designed to protect sensitive information. Blings does not have access and is never exposed to the video data, ensuring strict compliance with data privacy standards.
Conclusion
The integration of Blings.io SDK into Mercedes-Benz’s customer engagement strategy demonstrates a sophisticated use of technology with a robust architecture ensuring efficient data flow and high standards of information security. This setup exemplifies an innovative approach in the automotive industry, offering personalized customer experiences while maintaining data integrity and security.
The successful implementation leads to improvements in customer engagement and operational efficiency, setting a new benchmark in digital customer interaction within the automotive sector. Looking forward, the potential for further enhancements and wider applications of this technology is substantial, opening avenues for continued innovation and advancement.
For more detailed information and insights into the integration process, security considerations, and potential applications, please refer to the following resources:
MP5 Integration and Security GuideSolution Overview for IT and InformationDevelopersLast updated