Gravity Forms
+ Content Personalization Premium

Most forms ask every visitor the same questions in the same words. The Gravity Forms Content Personalization Premium Add-on lets one form adapt to each visitor. On the form’s Personalization tab you write simple rules — if the visitor matches some signals, then show or hide a field or a whole section, or swap a label, a description, a default value, a choice set or an HTML block — and the add-on applies them before the form reaches the browser.

Rules can use the visitor’s country and region, the referrer domain, UTM tags or any URL parameter, whether this is a first visit or a return visit, whether the visitor is logged in and their WordPress role, and the device: mobile, tablet or desktop. Combine conditions with AND or OR, order rules to set their priority, and give the Default fallback its own content for everyone else. Two merge tags carry the matched rule into confirmations and notification emails, and the rule name is saved with each entry so you can compare audiences.

It is built to be safe and private. Hidden content is removed on the server, so it never reaches the page and a hidden required field never blocks a submission, and it keeps working through AJAX submissions, multi-page forms and validation errors. Only the rule name is stored with an entry, the first-visit cookie holds only “1”, and no outside calls are made by default. For pages behind a full-page cache, a cache-safe browser mode applies the rules in the visitor’s browser instead.

When a form is displayed, the add-on reads the visitor’s signals from the request: the country and region header your host or CDN adds (or a local database file), the referrer, the URL parameters, its own first-visit cookie, the logged-in user’s roles and the device from the browser’s user agent. It evaluates the form’s rules from top to bottom; for each field and each kind of change the highest matching rule wins, and the Default applies when nothing matches. Fields that end up hidden are removed from the form for that visitor before it is rendered, and the swaps are applied to the rest. The signals of the first view are signed and sent with the form, so page two of a multi-page form, an AJAX submission or a validation re-render use exactly the same rules, and the hidden fields are skipped by validation and not saved. On submission the matched rule name is stored with the entry and the merge tags print the rule text in confirmations and notifications. In the cache-safe browser mode the server sends one neutral form and the add-on’s small script applies the browser-readable rules before the form is shown.