<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/41ba4258479b44188640588e6692138c&quot; frameborder=&quot;0&quot; width=&quot;1860&quot; height=&quot;1395&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1395</height><width>1860</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1395</thumbnail_height><thumbnail_width>1860</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/41ba4258479b44188640588e6692138c-1e3d771c5515e05e.gif</thumbnail_url><duration>276.936</duration><title>Enhancing Engagement Data Management</title><description>Hi Aditya, I appreciate your patience as we discuss the engagement consolidated table. The main issue is the presence of duplicate entries due to users interacting with multiple posts. I suggest we create a new table that captures unique users and the posts they&apos;ve engaged with, which will help us avoid duplicates. Please review this approach and let me know if you have any thoughts or additional ideas.</description></oembed>