<?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/cfbc071501c24437a697050748e995f6&quot; frameborder=&quot;0&quot; width=&quot;1660&quot; height=&quot;1245&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1245</height><width>1660</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1245</thumbnail_height><thumbnail_width>1660</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/cfbc071501c24437a697050748e995f6-22f3e11394371b03.gif</thumbnail_url><duration>191.081</duration><title>Understanding Marker.io Integrations and Ticket Content</title><description>In this video, I discuss the content that is sent to your integrations from Marker.io compared to what remains within the Marker.io ticket. I walk you through an example ticket that includes essential details like the title, screenshot, description, and environment info, while highlighting the importance of session replay videos, console logs, and network requests. I explain why we keep certain large files and lengthy data within Marker.io rather than sending them directly to integrations, emphasizing readability and organization. I encourage you to explore the links in your tickets for the full details and to utilize the filtering options available for easier navigation. Please let me know if you have any questions!</description></oembed>