<?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/a060217f76504d52a89c46df007920b1&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a060217f76504d52a89c46df007920b1-472ef1ea75294482.gif</thumbnail_url><duration>119.82</duration><title>Troubleshooting CMS Filter Implementation 🔍</title><description>Hey there! In this video, I walk you through an issue I encountered with the CMS filter implementation on our residential proxy page. I discuss using custom attributes like item and filter text, highlighting a specific problem with the naming order of Google search and Amazon. Your input on resolving this naming priority would be greatly appreciated.</description></oembed>