GHL Plan Ontology

What each plan includes and what gets provisioned when a customer signs up.

Question 1 — needs confirmation
Do all InMarket Audience plans include visitor resolution (Pixel)?
Currently all 3 InMarket Audience plans (VI InMarket Audience, Agency InMarket Local, Agency InMarket US) show Pixel = yes with a 25,000 visitor cap.

Is this correct? Or will some InMarket Audience customers get intent data without visitor identification? If so, those plans need pixel: false and visitorCap: null.
Question 2 — needs confirmation
What happens to existing GHL customers?
Current GHL customers were set up manually (not through the SaaS signup flow). Two options:

A) Migrate to SaaS — existing customers get moved into the new plan structure above, assigned a Stripe product ID, and provisioned through the standard LocationCreate webhook flow.

B) Remain as-is — existing customers stay on their current manual setup. Only new signups go through the SaaS plans. Existing accounts would need a separate "legacy" flag in the system.

Which path are we taking? This affects whether we need a migration script or a legacy compatibility layer.
What happens on signup (LocationCreate webhook)