<?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/b1bcdf2933334393b28beb9df0c8a331&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b1bcdf2933334393b28beb9df0c8a331-ea1efa54e462c412.gif</thumbnail_url><duration>63.363</duration><title>Recreating Gated Content and Plans Manually</title><description>This Loom explains the approach for recreating gated content and plans when continuing in an app not tied to the original template ID. Because the new app is not associated with the template ID, you will need to manually recreate the gated content and plans rather than programmatically reference them. The speaker suggests referencing the same gated content and plans by using the same custom fields and keeping the same gated content plan names so those carry over. You will also need to swap out plan IDs in the template, which the speaker indicates is required anyway.</description></oembed>