This record is generated by AI from the cited source. How AI is used
Account Engagement-hosted forms pre-fill eligible fields only when a visitor returns on the same device that last submitted them, instead of pre-filling across any device.
- Capability
- Landing pages & forms · Channels also: Privacy & data residency
- Vendor's name
- Protect Form Visitor Privacy
- First recorded
- Record last updated
Record dates describe acquisition and updates, not human review. About corrections.
Lifecycle history 1 state
- GAFeb 2026First recorded 2 Oct 2026 · recorded from the source history · vendor release notes · help.salesforce.com ↗
Record corrections 1
Changes made to this record after it was published, separate from the vendor's lifecycle states above. All corrections.
- Date
Date: GA · Jan 2026 → GA · Feb 2026
Dated to the Spring '26 release. Its section page says "This change is available on a rolling basis in February 2026"; a rollout to all editions is GA. Evidence: help.salesforce.com ↗
Something wrong or out of date in this record? , ideally with a link to better evidence. How corrections work
Landing pages & forms on other platforms latest first
- KlaviyoSign-up form creation and editing via ComposerGA6 Nov 2026
- Adobe AJOPublic landing pages for anonymous visitorsPreview28 Oct 2026
- KlaviyoEmail tracking consent in sign-up formsGA14 Oct 2026
- Treasure AILanding Pages in Engage StudioGA1 Oct 2026
- KlaviyoForms as a flow actionGA23 Sep 2026
- KlaviyoAnimated form elementsGA18 Sep 2026
- BrazeMulti-channel Manage Subscriptions blockGA17 Sep 2026
- KlaviyoCustom HTML block for in-app formsGA8 Sep 2026
- Adobe AJOMandatory landing page consent checkboxGA4 Sep 2026
- SFMC NextLanding page republish release updateGASep 2026