My team is currently attempting to integrate FullStory Analytics with our NextJS application. In production there are no issues, but we need to support preview deployment e2e testing, where we have deployment protection enabled via password / auth.

The issue is that FullStoryBot, their method of fetching CSS and asset resources from sites, is unable to bypass deployment protection and thus cannot retrieve CSS or images during session recording playbacks (viewing user sessions on preview deployments looks like unstyled HTML pages).

FullStory’s recommend solution is to “allowlist traffic based on the existence of “FullStoryBot” in the User-Agent string”, but Vercel doesn’t seem to support this behavior through the UI. We understand and have used “protection bypass for automation” and “OPTIONS allowlist” before, but FullStoryBot isn’t customizable enough to leverage these methods.

TLDR: We’re at a middle ground of sorts where neither platform is customizable enough to allow each other to communicate, but we’re curious whether the Vercel support team could help us find a workaround. We’re on Vercel’s enterprise plan.