))
#296 - The Architecture Pitfalls of Single Vendor Solutions
Manage episode 402171443 series 3237629
เนื้อหาจัดทำโดย 33 Sticks เนื้อหาพอดแคสต์ทั้งหมด รวมถึงตอน กราฟิก และคำอธิบายพอดแคสต์ได้รับการอัปโหลดและจัดหาให้โดยตรงจาก 33 Sticks หรือพันธมิตรแพลตฟอร์มพอดแคสต์ของพวกเขา หากคุณเชื่อว่ามีบุคคลอื่นใช้งานที่มีลิขสิทธิ์ของคุณโดยไม่ได้รับอนุญาต คุณสามารถปฏิบัติตามขั้นตอนที่แสดงไว้ที่นี่ https://th.player.fm/legal
Architecting data collection for multiple tools within a single vendor solution can be appear to be beneficial from the stand-point of reduced logic and streamlined integrations. It can seem simplified and streamlined resulting in a solution that can be managed with greater ease.
Are there pitfalls when it comes to single-vendor solutions? What problems with the data collection can present themselves?
On this week’s episode of the 33 Tangents podcast, Jim and Jason are joined by Jenn Kunz to discuss what organizations need to consider when working with a single vendor analytics & marketing technology solution (or even a martech stack that mostly, though not completely, consists of tools from a single vendor). They talk through the various risks, such as assumptions that are often made, and how teams can be set up for failure with a single-vendor solution.
THANK YOU
We know your time is limited, so it means a lot to us that you would spend some of your time with us. If you have found this episode to be valuable, we would appreciate if you would share it.
And if we are getting you hooked, don’t forget to subscribe, like, and recommend on your favorite podcast platform.
WHERE TO LISTEN
The 33 Tangents video simulcast is now available on YouTube
WHERE TO FIND US
Website: www.33sticks.com
Email: Podcast@33sticks.com
Twitter: https://twitter.com/33Sticks
Facebook: https://www.facebook.com/33sticks/
YouTube: https://www.youtube.com/channel/UC8KUpp_LygXotCrKgR9ZoBg
225 ตอน
แบ่งปัน
