<?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/3361d14754ab4916a7b6d14a3a1ff746&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/3361d14754ab4916a7b6d14a3a1ff746-fcc0e2398a5b31bb.gif</thumbnail_url><duration>80.6</duration><title>Blocking Bot Traffic in Full Story</title><description>I walked through how bot traffic affects full story sessions and can unnecessarily eat into your session quota. I explained that you can block bot traffic by blocking specific user agents in your FullStory settings under data capture and privacy. I showed how to block a list of common bot user agents, or add a specific user agent to the block list. I also referenced the web configuration guide dashboard to check for bot related user agent traffic, and in this case we saw none. No action is required beyond reviewing these settings if you want to block bots.</description></oembed>