FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 4 of 6

Forms, tracking and sign-in across two systems

Search engines are not the only ones crossing between systems. How to keep leads, data, consent and logins working when a visitor moves between two platforms on one domain.

6 min readUpdated 2026-11-07
All chaptersChapter 4 of 6
  1. 01When a full cutover is wrong
  2. 02Reverse proxy setup in plain words
  3. 03SEO parity for each page
  4. 04Forms, tracking and sign-in across two systems
  5. 05Moving platforms in phases
  6. 06Retiring the old site

The short answer

To the browser, two systems behind one proxy look like one website. That helps: same-domain cookies and browser storage carry across, and analytics usually needs no special setup. But it also means each system can read, overwrite or lose what the other set. So keep one tag setup and one consent tool on both sides, send forms to one destination, and test a real journey that crosses from one system to the other.

What the browser actually sees

Almost everything in this chapter follows from three points:

  • Same host, shared cookies. A cookie set on www.example.com is sent for every matching path, whichever system answers. As MDN's Set-Cookie reference notes, Path is not a security boundary.
  • Same origin, shared storage. Local storage and session storage belong to the scheme, host and port. So values saved on an old page are readable on a new one.
  • A cookie for the wrong domain is ignored. If an origin sets Domain=wf.example.com while the browser is on www.example.com, the browser drops it. That is one reason a login or form "works on the origin, but not on the live site."

Forms

List every form on the site, with what it does after submit. Then decide this for each one.

QuestionWhat to check
Where do the messages go?The same inbox, CRM or sheet, whichever system holds the form
Does it post to its own path?That path needs a route to the right system
Does the server check where the request came from?It now arrives through the proxy, so origin and CSRF checks may fail
Is spam protection tied to a list of domains?Make sure the public domain is on it
Does it redirect to a thank-you page?Confirm the path, and any conversion tied to it
Does a security policy limit where forms can post?Add the new destination before you switch the route

Move a page's form with the page, and test it in the same batch. Test by sending a real message and seeing it arrive, because a thank-you message only proves the page worked.

Run these tests with any CDN script deferral off. Webflow's checklist warns that features such as Rocket Loader can break forms.

Tracking

Google's cross-domain measurement help is for measuring across more than one domain, so pages on the same domain do not need it. On a proxy setup, both systems are on your public domain. So what matters is keeping the two sides identical.

  • The same Tag Manager container or measurement ID on both systems, once each. A tag loaded twice, or a page with none, spoils the data.
  • The same event names on both. Check the event a form sends on each side, and rename nothing during the move.
  • Cookie domain the same on both, if you use subdomains as well. Google's help warns that different cookie domains can cause self-referrals.
  • Conversions tied to a URL still fire. A thank-you path that moved systems should stay the same.
  • Hits from origin hostnames are visible. Add a filter or check the hostname report, and look into any you find.
  • Campaign tags survive. If hidden form fields read UTMs from the landing page, confirm the value carries over from a page on one system to a form on the other.

Add a platform value to page views, such as webflow or old. It lets you compare moved and unmoved pages in your reports without a separate list. Our tracking setup post has the base setup, and the analytics service page covers what we do.

Consent

Consent has to hold across the join. A visitor who rejects cookies on a new page should not be asked again, or tracked, on an old one.

  • Use one consent tool, loaded the same way on both systems.
  • Store the choice in a cookie with Path=/, so both sides can read it.
  • Make sure tags wait for consent on both sides. Check the network panel before and after accepting, on a page from each system.
  • Keep the same wording and categories, and one cookie list that covers both systems.

This is practical advice, not legal advice. Check what your rules require. There is more on the Webflow side in our post on cookie consent on Webflow.

Sign-in and private areas

If your site has any signed-in area, plan it as its own workstream. The safest setup is to keep it out of the move: leave the app where it is, on its own subdomain if it has one, and link to it.

If it has to stay on the shared domain, check these:

  • Session cookies. The proxy would normally forward them to both systems. Only send cookies to the system that needs them, so an app session is never sent to your marketing platform.
  • Cookie scope. MDN says a cookie with no Domain goes only to the exact host, while a cookie with Domain=example.com is sent to all subdomains, including your origins. Keep session cookies host-only where you can.
  • Name clashes. Two systems may use the same cookie name. Look at what each one sets.
  • Login redirects. After login, an app may send people to its own hostname. Rewrite or configure this to use the public domain.
  • Caching. Signed-in pages should bypass the proxy cache. Test as two different users.
  • Webflow password pages. The checklist says password protection does not work on pages served from a subdirectory through a proxy. It works only on root domains or the origin URL, so plan an alternative if you need it.

Site search is a related catch. Webflow's checklist says native site search does not work across multiple web properties, so a search box on one system will miss the other's pages. You may need custom code or a dedicated search tool for as long as the two systems run.

Test one crossing journey

Run this in a clean browser profile at each batch. Between them, these steps cover most of what goes wrong.

  1. Land on an old page with a utm_source tag in the URL.
  2. Accept or reject cookies, and note the choice.
  3. Click through to a moved page. The banner should stay away, and tags should match your choice.
  4. Send the form on the moved page.
  5. Confirm the message arrived, with the campaign value on it.
  6. Confirm the event shows in your analytics debug view, in one session.
  7. Repeat the other way, from a moved page to an old one.
  8. Sign in, if you have an area for that, and sign out.

Done when All eight steps pass in both directions on the public domain, with a real message received. Keep the result beside the batch in your route table.

Takeaways

What to remember from chapter 4.

  • Behind one proxy, the browser sees one site, so cookies and storage are shared between systems.
  • A cookie set for an origin hostname is ignored on the public domain, which breaks logins and forms.
  • Prove each form by receiving a real message, and check origin rules and spam protection lists.
  • Same domain needs no cross-domain tracking, but tags, events and consent must match on both sides.
  • Keep sign-in areas out of the move if you can, and test a journey that crosses both ways.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.