<?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/43209d35a5a94b07aace50e35b500a34&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/43209d35a5a94b07aace50e35b500a34-85da742688416fb9.jpg</thumbnail_url><duration>53.161</duration><title>[18.0][ADD] project_prevent_analytic_rename</title><description>This Loom demonstrates testing for the ProjectPreventAnalyticRename module and its impact on analytic account naming. The speaker describes a project linked only to a single analytic account where changing the project name normally updates the analytic account name. They then test the module and report that after installing ProjectPreventAnalyticRename, changing the project name leaves the analytic account name unchanged. The video concludes with confirmation of this behavior.</description></oembed>