Forms & Pages makes it simple to create beautiful and effective pages where you can request details from your visitors, and show relevant, exclusive information without the need of a developer.

As with all activities in APSIS One, Forms and Pages allows you to collect both browsing and personal data.

Where do Form responses go?

If you choose to save Form responses as Attributes, a Profile's Attribute values are updated when they fill out their Form (like when you ask for their First name, or email address).

This is achieved by ticking the Map to Attribute checkbox in the Input Field Elements in your Form. You pick an Attribute, and the visitors' responses are added as a value for that Attribute.

Other Elements allow you to set up which Attribute should be mapped to the Element and its desired values under Mapping in the Element's options.

However, you can choose to track as a form response only. Visitors who fill in your Form, and enter their information in a Collect Element that is set to Form response only, will gain a Form - Submit Event and their responses will be inside the Event as Event data. Read more about Forms and Pages Events...

While Pages only track browsing data, Forms collect a variety of Events. In the Form - Submit Event, you'll see all the Form responses from the visitors who submitted your Form.

In short, responses that aren't mapped to an Attribute are only found in the Form - Submit Event.

If you want to make the most out of the data you collect from your visitors, simply create a Segment to target those Profiles who submitted your Form and further personalize your communications!

Jump to Creating a Form or Creating a Page!

For you to make the most out of the data collected from your Form activity, Forms are required to have at least one Input Field Element mapped to an Email Attribute or a Mobile Attribute.

With these valuable pieces of data, each Form completed will result in Known Profiles in Audience, which are ultimately more accessible and actionable for your APSIS One activities.

Certain Known Profiles with an email address or phone number (with or without consent) may already exist in your account before you create a Form.

When a new Known Profile is created by a Form, we automatically merge this Profile with the Profile that already exists in your Audience if the email address or mobile number matches (Email or Mobile Attribute). The result is complete, enriched Profiles that contain all their corresponding data!

If you want to go into detail regarding Profile merge, take a look at this article.

Unless the Form is gathering consent, Profiles won't gain consent when submitting your Form. The same applies for Profiles that are merged based on matching email address or phone number (Email or Mobile Attribute). Consent is collected with a Terms and Conditions or Consent Element.

In that case, Profiles without consent will gain consent for Email or SMS communications to the Subscription mapped to your Terms and Conditions or Consent Element when they submit your Form.

If the Profile had consent prior to the merge, it will remain opted-in to those Subscriptions, and they will be opted-in to the ones mapped to your Form if they're not the same.

In the Form Action step of creating a Form, you'll see the Profile Check settings.

These settings prevent existing Profiles from being overwritten or modified by a Form. Sometimes, a visitor can try to fill in your Form more than once, or there simply is a Profile in your Audience that already matches the Email or Mobile Attribute they entered in your Form.

If you choose to Allow Profile overwriting, visitors who fill in your Form will get their Profiles updated with their responses. However, if you choose any of the first three options, the Profile will not.

So, while a Profile that is overwritten (merged) with an existing Profile in your

Audience gains the following Events and potential changes:

Those who are blocked by an existing Profile gain the following Events:

Those Profiles that are blocked to prevent overwriting simply get an Event that signals they have been blocked (Form - Reject and the reject Reason Event data corresponding with your Form's setup). Read more about Forms and Pages Events...