<meta content="text/html; charset=utf-8" http-equiv="Content-Type"></meta></head><body><div class="small-8 large-9 columns" id="content"><meta content="width=device-width, initial-scale=1.0" name="viewport"></meta><nav class="contents local" id="contents"><nav class="widget-toc" id="contents">Table of contents will be added

</nav></nav><span id="create-form">To create a form:</span>

1. <span id="create-form">Log in to Campaign Studio.</span>
2. <span id="create-form">In the left navigation pane, click **Components**.</span>
3. <span id="create-form">Click **Forms**</span>
4. <span id="create-form">On the Forms page, click **+New**.</span>

<span id="create-form">Form types</span>
----------------------------------------

<span id="create-form">![Form types](https://acquia.widen.net/content/iuhzjd5k4x/jpeg/campaign-studio_form-types.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

- <span id="create-form">**Campaign Form**: Triggers a campaign on submission. Campaign forms have fewer directly associated form submit actions (which happen after a contact submits a form.) Most actions trigger as part of the campaign the form triggers.</span>
- <span id="create-form">**Standalone Form**: The more commonly used form type, used for more generic data collection. Use form submit actions to add contacts to a segment and use that segment as the contact source for a campaign, to trigger a campaign based on Standalone Form submissions.</span>

<span id="create-form">General options</span>
---------------------------------------------

- **Categories**: Group various resource types to different organizational classifications such as marketing strategies, topics, or departments. For more information, visit [<u data-prosemirror-content-type="mark" data-prosemirror-mark-name="underline">Categories</u>](https://docs.acquia.com/campaign-studio/settings/categories).
- **Projects**: Group and manage all related entities within a dedicated, centralized workspace. For more information, visit [Projects](https://docs.acquia.com/campaign-studio/projects).
- <span id="create-form">**Publish options**: Set the **Yes/No** toggle bar to publish or unpublish a form. Forms that are unpublished are not visible on pages if you added the form using JavaScript. If you copied the form manually to add the form to your page, the form is visible but not submittable. Contacts see an error message when they try to submit the form.</span>
- <span id="create-form">**Publish at**: Set the date and time you want the form to publish. This helps to control relevance, and does not require you to manually publish a form at the right time.</span>
    
    <span id="create-form">To schedule a form to publish at a specified date and time:</span>
    
    
    1. <span id="create-form">Click the **Publish at (date/time)** box and select your preferred date and time from the Date and Time picker.</span>
    2. <span id="create-form">Set **Published** to **Yes**.</span>
        
        <span id="create-form">Campaign Studio marks the form as **Pending** and publishes it at the scheduled date and time.</span>
- <span id="create-form">**Unpublish at**: Set the date and time you want a form to unpublish. This helps to control relevance, and does not require you to manually unpublish a form at the right time.</span>
    
    <span id="create-form">To schedule a published form to unpublish at a specified date and time:</span>
    
    
    1. <span id="create-form">Click the **Unpublish at (date/time)** box and select your preferred date and time from the Date and Time picker.</span>
        
        <span id="create-form">Campaign Studio unpublishes form at the scheduled date and time.</span>

<div class="admonition important"><span id="create-form">Important</span>

<span id="create-form">The Date and Time picker shows the date and time according to the default timezone set for your user’s profile in </span>[<span class="doc" id="create-form">System Settings</span>](/campaign-studio/settings/configurations)<span id="create-form">. Therefore, before scheduling a form to publish or unpublish, you must check the default timezone.</span>

</div>- <span id="create-form">**Disable search indexing**: Select **Yes** to prevent search engines from finding and displaying the form in search results for related topics.</span>
- <span id="create-form">**Kiosk Mode**: Select **Yes** to turn off tracking, and prevent Campaign Studio from generating new cookies or attaching the IP address to the contact record. This may also be referred to as data entry mode. Use this for instances where several contacts may enter their information using the same device, such as a conference. Kiosk mode prevents the activity on the device from being tied to one contact.</span>
- <span id="create-form">**Render Style**: When you select **Yes**, the form displays on your page or application with the styling from either the selected theme the **Attributes** tab of a field editor. When set to **No**, the form adopts the CSS of your page or application.</span>
- <span id="create-form">**Theme**: The selected theme dictates the styling of your form when it is added to an external page or application, if **Render Style** is set to **Yes**.</span>
    
    <div class="admonition note"><span id="create-form">Note</span>
    
    <span id="create-form">Not all themes include form styling. Check the **Features** column on your **Themes** page (in **Settings**) to see which available themes include CSS for forms.</span>
    
    </div>

<span id="create-form">Form details</span>
------------------------------------------

<span id="create-form">![Form details](https://acquia.widen.net/content/l4hp1n8cen/jpeg/campaign-studio_form-details.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

- <span id="create-form">**Name**: Title your form, including any terms you may want to use to search for the form.</span>
- <span id="create-form">**Description**: Add a description, so other users can see what the goal of the form is. It may help to include information like the creation date and any pages where the form appears.</span>
- <span id="create-form">**Successful Submit Action**: Options include</span>
    - <span id="create-form">**Remain at form**: nothing appears to happen</span>
    - <span id="create-form">**Redirect URL**: directs the contact to another page, such as a thank you page, after submission</span>
    - <span id="create-form">**Display message**: shows a message over the form once the contact has submitted the form).</span>
- <span id="create-form">**Redirect URL/Message**: If you decide to use the **Redirect URL** successful submit action, paste the URL where you want to direct submitters. If you use **Display message**, enter the message to display.</span>

<span id="create-form">Form fields</span>
-----------------------------------------

<span id="create-form">![Form fields](https://acquia.widen.net/content/riyfpulkjo/jpeg/campaign-studio_form-fields.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

### <span id="create-form">Field types</span>

<span id="create-form">Choosing the proper field type helps Campaign Studio users gather data appropriately on forms, and can optimize the end-user’s experience of completing the form. On some devices, certain form fields may display differently and the wrong field type may result in a more difficult submission, resulting in lost conversions.</span>

- <span id="create-form">**Maximum fields displayed at a time**: Applies progressive profiling across multiple forms. Select the maximum number of fields that must be displayed on a single form.</span>

<span id="create-form">To add a new field:</span>

1. <span id="create-form">Click the **Add a new field** menu.</span>
2. <span id="create-form">Select the field type you’d like to add. The available field types are listed </span>[<span class="std std-ref" id="create-form">below</span>](#id1)<span id="create-form">.</span>
3. <span id="create-form">Enter more information about the field. For more information, see </span>[<span class="std std-ref" id="create-form">Field editor</span>](#field-editor)<span id="create-form">.</span>

- <span id="create-form">**CAPTCHA**: A basic form of spam protection, requiring a human to submit an answer or identifying when spambots try to submit data in a hidden CAPTCHA field (honeypot). Acquia recommends using some form of CAPTCHA in every form. Campaign Studio also supports reCAPTCHA v2, which you see as a field type after setting up the reCAPTCHA plugin.</span>
- <span id="create-form">**Checkbox Group**: Enables a contact to select one or more options from a list, using checkboxes. Campaign Studio subscribers also use the **Checkbox Group** for a single option on opt-in forms to gain consent to use cookies and send marketing emails or other messages to the contact.</span>
    
    <div class="admonition note"><span id="create-form">Note</span>
    
    <span id="create-form">**Checkbox Group** works with </span>*<span id="create-form">Boolean</span>*<span id="create-form"> and </span>*<span id="create-form">Select - Multiple</span>*<span id="create-form"> field types but not </span>*<span id="create-form">Select</span>*<span id="create-form"> fields.</span>
    
    </div>
- <span id="create-form">**Company Lookup**: Displays all companies that exist in the instance as a **Select** field. Along with companies, it also displays the City and State data, if available.</span>
    
    <div class="admonition note"><span id="create-form">Note</span>
    
    <span id="create-form">To find a company, a person submitting the form must enter at least three characters. After one second with no additional characters entered in the search, the list displays the companies with names matching the characters entered in the field.</span>
    
    </div>
- <span id="create-form">**Date**: Validates date fields in your default date format, and improves the end-user experience when completing the form. In a web browser on a laptop or desktop, the field shows selectors for month, day, and year. On mobile devices, a calendar displays.</span>
- <span id="create-form">**Date/time**: Like the date field, but a selector is displayed for time.</span>
- <span id="create-form">**Description area**: A basic header field, most commonly used to give the form a visible title on the page. The Header field acts as the field name or label. The description area (in the **Properties** tab) is a free text editor where you can add a description of the form. You can also do this by adding text around the form on your page. However, if you use the same form in several places, adding the description on the form enables an efficient single change.</span>
- <span id="create-form">**Email**: Requires a field containing an email address with the proper syntax - </span>`<span class="pre" id="create-form">name@domain.com</span>`<span id="create-form">. Acquia recommends having a required **Email** field on your forms, as email addresses are the default unique identifier.</span>
- <span id="create-form">**File**: Enables contacts to upload files with the form.</span>
- <span id="create-form">**Hidden**: A field is not displayed with the form. Users may add default values to save with the form for reporting or internal tagging purposes.</span>
- <span id="create-form">**HTML area**: Enables marketers to add custom code into their forms.</span>
- <span id="create-form">**List - Country**: Populates Campaign Studio’s default, non-editable country list. To use a custom list, use a **Select** field type and manually enter the countries that you want to display in the list.</span>
- <span id="create-form">**Number**: Validates that the entered values are digits. This field allows decimals and negatives, but no other non-numerical values (including commas). On mobile devices, the keyboard changes to a number pad when a contact selects this field to complete.</span>
- <span id="create-form">**Page break**: Enables marketers to break up the form into multiple pages or field groupings.</span>
- <span id="create-form">**Password**: Enables contacts to create a password. Use the field if the form is used to create an account and the results post to another form/system. The entered field value should not save, because the field saves in plain text on the contact record.</span>
- <span id="create-form">**Phone**: Like the number field, but maps to the **Phone** field and validates numbers using international format. The validation requires a dialing code (for example, +1 for the United States or +44 for the United Kingdom).</span>
- <span id="create-form">**Radio Group**: Gives contacts a single-select list of options, with a radio button. This may also be called an option button group.</span>
- <span id="create-form">**Select**: Displays a menu where a contact may choose one option. This field also allows multiple selections, which changes the display to a box with the options listed. On mobile devices, a single selection displays as a dialog box with radio buttons, while a multi-select menu displays in a dialog box with checkboxes.</span>
- <span id="create-form">**Text**: A free-form text box with a limit of 255 characters. Common fields such as first name, last name, position/job title, city, etc. are often built as text fields.</span>
- <span id="create-form">**Textarea**: A longer-form text field with a character limit of 65,535 characters.</span>
- <span id="create-form">**URL**: Validates the entry must be a URL, including </span>`<span class="pre" id="create-form">https://</span>`<span id="create-form"> or </span>`<span class="pre" id="create-form">http://</span>`<span id="create-form">.</span>

<span id="id2">Field editor</span>
----------------------------------

<span id="id2">Based on the selected field type, Campaign Studio displays various tabs in the fields editor. The available tabs are:</span>

- [<span class="std std-ref" id="id2">General</span>](#field-editor-general)
- [<span class="std std-ref" id="id2">Mapped Field</span>](#field-editor-contact)
- [<span class="std std-ref" id="id2">Validation</span>](#field-editor-validation)
- [<span class="std std-ref" id="id2">Properties</span>](#field-editor-properties)
- [<span class="std std-ref" id="id2">Attributes</span>](#field-editor-attributes)
- [<span class="std std-ref" id="id2">Behavior</span>](#field-editor-behavior)

<span id="id2">![Field editor general](https://acquia.widen.net/content/xolet2134q/jpeg/campaign-studio_field-editor-general.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

### <span id="field-editor-general">General</span>

- <span id="field-editor-general">**Label**: The title of your field to help the contact understand what they must enter in the field. By default, the label is displayed before the form field.</span>
- <span id="field-editor-general">**Show label?**: When set to **No**, the label does not display on the form.</span>
- <span id="field-editor-general">**Save result?**: When set to **No**, Campaign Studio does not save the data entered in the list of form submission results. If you map the field to a contact field, Campaign Studio still saves the data to the contact record.</span>
- <span id="field-editor-general">**Default value**: In case the contact does not submit data for the field, you may enter a default value to submit with the form. This is useful for hidden fields and reporting.</span>
- <span id="field-editor-general">**Help message**: To add more detail on what you want a contact to enter, add a custom help message.</span>
- <span id="field-editor-general">**Input placeholder**: Adds text within the form field, acting as a label or help message. When used as a basic text field, (styling is from a “Fresh” landing page theme), the options display like this:</span>

### <span id="field-editor-contact">Mapped Field</span>

<span id="field-editor-contact">The **Mapped Field** maps the form field to where you want the data to save on a contact or company record. Without a field mapped here, the data is not saved to the contact or company record. The data type you choose for the form field should match the data type for the Campaign Studio field. For example, a **Date and time** form field should map to a **Date and time** standard or custom field. Checkbox group form fields work well with **Select - Multiple** Campaign Studio fields. **Radio Group** or **Select** form fields work well with **Boolean**, **Select**, or **Select - Multiple** Campaign Studio fields.</span>

### <span id="field-editor-validation">Validation</span>

- <span id="field-editor-validation">**Required**: Determines if the form field must be populated on submission. Campaign Studio does not accept form submissions without data in the required fields. Labels for required fields have an asterisk (</span>`<span class="pre" id="field-editor-validation">*</span>`<span id="field-editor-validation">) to indicate that they are required.</span>
- <span id="field-editor-validation">**Validation message**: A message which displays if a contact attempts to submit a form without data in a required field. Campaign Studio’s default message is </span>`<span class="pre" id="field-editor-validation">This</span><span id="field-editor-validation"> </span><span class="pre" id="field-editor-validation">is</span><span id="field-editor-validation"> </span><span class="pre" id="field-editor-validation">required.</span>`<span id="field-editor-validation"> Enter your custom message in the box to change the display.</span>

### <span id="field-editor-properties">Properties</span>

<span id="field-editor-properties">The **Properties** tab does not display on all field types. Different field types have different properties options.</span>

#### <span id="id3">Captcha</span>

<span id="id3">![Captcha properties](https://acquia.widen.net/content/iermuadcdr/jpeg/campaign-studio_captcha-properties.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

- <span id="id3">**Captcha answer**: To use the CAPTCHA field as a honeypot, leave the CAPTCHA answer field empty. This hides the field, and spambots will try to populate the field with data. Campaign Studio recognizes if there is data in a honeypot CAPTCHA field, and understands it cannot be a human submitting the form. To have humans answer a basic question or statement, like </span>`<span class="pre" id="id3">What</span><span id="id3"> </span><span class="pre" id="id3">is</span><span id="id3"> </span><span class="pre" id="id3">2+2?</span>`<span id="id3"> or </span>`<span class="pre" id="id3">Enter</span><span id="id3"> </span><span class="pre" id="id3">"CAPTCHA"</span>`<span id="id3">, enter the expected response in the **CAPTCHA answer** box. In these cases, </span>`<span class="pre" id="id3">4</span>`<span id="id3"> or </span>`<span class="pre" id="id3">CAPTCHA</span>`<span id="id3"> would be the answers. The field’s **Label** should be your question, or you may label the field </span>`<span class="pre" id="id3">CAPTCHA</span>`<span id="id3"> and use the input placeholder, depending on your preference for the form’s appearance.</span>
- <span id="id3">**Custom error message**: If a human enters a wrong CAPTCHA answer, an error message displays on submission. Campaign Studio’s default error message is </span>`<span class="pre" id="id3">The</span><span id="id3"> </span><span class="pre" id="id3">answer</span><span id="id3"> </span><span class="pre" id="id3">to</span><span id="id3"> </span><span class="pre" id="id3">"{label}"</span><span id="id3"> </span><span class="pre" id="id3">is</span><span id="id3"> </span><span class="pre" id="id3">incorrect.</span><span id="id3"> </span><span class="pre" id="id3">Please</span><span id="id3"> </span><span class="pre" id="id3">try</span><span id="id3"> </span><span class="pre" id="id3">again.</span>`<span id="id3"> You may enter a custom message here instead.</span>

#### <span id="field-editor-properties">Checkbox group, radio group, and select</span>

<span id="field-editor-properties">![Checkbox group properties](https://acquia.widen.net/content/a6nkdjdlno/jpeg/campaign-studio_checkbox-group-properties.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

<span id="field-editor-properties">Here, you enter the options a contact will select from.</span>

- <span id="field-editor-properties">**Use assigned contact/company field’s list choices**: If you have mapped the form field to a Campaign Studio field which has a pre-set option list (in the **Custom Field** setup), you may use those options and not recreate them on the form.</span>
- <span id="field-editor-properties">**Optionlist**: If you are not using the assigned options from a contact or a company field, configure the potential options here. The **Label** field controls how the option will display on the form. The **Value** is how the data will be stored on the contact record and in the database. The **Label** and **Value** often, but do not always, match. As an example, if you are using a checkbox field for GDPR opt-ins, your **Label** may say </span>`<span class="pre" id="field-editor-properties">Yes,</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">I</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">accept</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">that</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">I</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">may</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">receive</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">email</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">communications</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">from</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">this</span><span id="field-editor-properties"> </span><span class="pre" id="field-editor-properties">company.</span>`<span id="field-editor-properties">. Your **Value** could be a </span>`<span class="pre" id="field-editor-properties">Yes</span>`<span id="field-editor-properties"> or </span>`<span class="pre" id="field-editor-properties">1</span>`<span id="field-editor-properties"> as a positive boolean value.</span>
- <span id="field-editor-properties">**Empty Value (on Select only)**: This serves the same purpose as an **Input Placeholder**, which is available on most other field types. The **Empty Value** is not a default value, and Campaign Studio does not save the value to the contact record.</span>
- <span id="field-editor-properties">**Allow Multiple (on Select only)**: This option transforms the field from its default **Select** field type into a **\*Select - Multiple** field type.</span>

#### <span id="field-editor-properties">Description area</span>

<span id="field-editor-properties">Use the **Description Area** field when there is any information you want to display with the form. Often, users add this kind of information on the webpage, landing page, or application instead of the form, but it is an option in the form builder.</span>

#### <span id="field-editor-properties">File</span>

<span id="field-editor-properties">![File properties](https://acquia.widen.net/content/8oc0dnuytt/jpeg/campaign-studio_file-properties.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

- <span id="field-editor-properties">**Allowed file extensions**: By default, Campaign Studio accepts the following file types:</span>
- <span id="field-editor-properties">**Maximum size (MB)**: The maximum size Campaign Studio allows for uploads is 100MB. You may reduce the file size to restrict users to uploads to smaller files.</span>
- <span id="field-editor-properties">**Public accessible link to download**: When a contact uploads a file on a form, Campaign Studio saves the file as a link. Select **Yes** to enable anyone to download the originally uploaded file by visiting the link. Select **No** restrict downloads to users logged into the Campaign Studio instance.</span>

#### <span id="field-editor-properties">HTML area</span>

<span id="field-editor-properties">Add the code that you want to include in an HTML field.</span>

#### <span id="field-editor-properties">List - Country</span>

- <span id="field-editor-properties">**Empty Value**: This serves the same purpose as an **Input Placeholder**, which is available on most other field types. The **Empty Value** is not a default value, and Campaign Studio does not save the value to the contact record.</span>
- <span id="field-editor-properties">**Allow Multiple**: This option transforms the field from its default **Select** field type into a **Select - Multiple** field type.</span>
    
    <div class="admonition note"><span id="field-editor-properties">Note</span>
    
    <span id="field-editor-properties">Campaign Studio’s **Country** field is a predefined, non-editable list. To edit the list’s options, create a **Select** field and manually enter the options for your custom country list.</span>
    
    </div>

#### <span id="field-editor-properties">Page break</span>

- <span id="field-editor-properties">**Next page button label**: This text displays on the button contacts click to move forward to the next page, or set of questions on the form. This is not a submit button and it does not save any data.</span>
- <span id="field-editor-properties">**Previous page button label**: This may apply if you are already on a second or higher page and want to give contacts an option to go back to the previous page. It is a button to move backward in the form, not a submit button.</span>

### <span id="field-editor-attributes">Attributes</span>

<span id="field-editor-attributes">Attributes are CSS tags to change the styling of a particular form. If you set **Render Style** to **No** on the form, these attributes will be ignored.</span>

- <span id="field-editor-attributes">**Field HTML name**: The machine name for the field. Campaign Studio will populate this based on the **Label**, and is customizable if the label is long. Generally, you reference the HTML name when you are connecting Campaign Studio forms to other forms or when you are using the **Manual Copy** function to manually add the form to your page or application.</span>
- <span id="field-editor-attributes">**Label attributes**: Changes the way the label text appears. Use the format </span>`<span class="pre" id="field-editor-attributes">style="attribute:</span><span id="field-editor-attributes"> </span><span class="pre" id="field-editor-attributes">descriptor"</span>`<span id="field-editor-attributes"> to change the style. For example, to change the label to red, use </span>`<span class="pre" id="field-editor-attributes">style="color:</span><span id="field-editor-attributes"> </span><span class="pre" id="field-editor-attributes">red"</span>`<span id="field-editor-attributes"> or </span>`<span class="pre" id="field-editor-attributes">style="color:</span><span id="field-editor-attributes"> </span><span class="pre" id="field-editor-attributes">#ff0000"</span>`<span id="field-editor-attributes">.</span>
- <span id="field-editor-attributes">**Input attributes**: Changes the way any text inside the form field appears. This may apply to the input placeholder text, text entered by the person submitting the form, or the options for select fields when **Allow Multiple** is set to yes (including **List - Country**).</span>
- <span id="field-editor-attributes">**Field container attributes**: Changes the form field. You may want to change the size of the box, fill color, rounded edges, or any of several other properties of the actual field.</span>
- <span id="field-editor-attributes">**Radio/checkbox label attributes**: Where available, changes the way options on radio buttons or checkbox groups display, similar to the input attributes.</span>

### <span id="field-editor-behavior">Behavior</span>

<span id="field-editor-behavior">The **Behavior** tab helps marketers improve the experience for the contact completing the form. It also helps marketers implement progressive profiling, to gather more data from the contact which helps in optimized personalization.</span>

- <span id="field-editor-behavior">**Show when value exists**: If the contact is known and tracked and a value for the field exists on the contact’s record, Campaign Studio can hide the field. Set this option to **No** to hide the field. Marketers may want to hide the field so they are not repeating the same question. Marketers may want to display the question to ensure the contact is entering the most current information. Acquia recommends always displaying the unique identifier (most commonly the email address).</span>
- <span id="field-editor-behavior">**Show after X submissions**: This is the key to progressive profiling. If you are using the same form in several places on your website, you can change the fields the contact sees each time they see the form. Enter a value between </span>`<span class="pre" id="field-editor-behavior">1</span>`<span id="field-editor-behavior"> and </span>`<span class="pre" id="field-editor-behavior">200</span>`<span id="field-editor-behavior">. This field will hide the field until the contact submits the same form the stated number of times. When left undefined, the field will display every time the contact sees the form. The goal is to shorten the form. Use it with hiding fields when values exist.</span>
- <span id="field-editor-behavior">**Auto fill data**: If the contact is known and tracked and a value for the field exists on the contact’s record, Campaign Studio can pre-populate the data. Auto fill works with forms embedded in Campaign Studio landing pages, and data does not pre-populate when the form is placed anywhere else. Even if you are hiding this field, you may want to turn on auto fill to save the result with the form submission.</span>
    
    <div class="admonition important"><span id="field-editor-behavior">Important</span>
    
    <span id="field-editor-behavior">If multiple contacts share the same IP address, this field might prepopulate with incorrect details, including details of other contacts, due to the way Campaign Studio identifies contacts.</span>
    
    </div>

### <span id="id2">Field order</span>

<span id="id2">To change the order of the fields on your form:</span>

1. <span id="id2">Click the field that you want to move.</span>
2. <span id="id2">Drag the field to the new location.</span>

<span id="id4">Form actions</span>
----------------------------------

<span id="id4">![campaign studio forms actions tab](https://acquia.widen.net/content/tyuxgm8bmi/jpeg/campaign-studio_forms-actions-tab.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

<span id="id4">You may want to have things happen after a contact submits a form. These may include communications with your contact, tracking, internal notification, or other lead management.</span>

<div class="admonition note"><span id="id4">Note</span>

<span id="id4">The form actions available on Campaign Forms are also available on Standalone Forms. However, Standalone Forms offer more form actions because they exist outside of campaigns, where you can build these same additional actions directly into the campaign events.</span>

</div>- <span id="id4">**Add to company’s score**: If the contact who submitted the form is associated with a </span>*<span id="id4">Company</span>*<span id="id4"> record in Campaign Studio, you may add points to the company’s overall score. Company scoring in Campaign Studio does not aggregate points for all its associated contacts. Any actions that you want to contribute to a company’s score must be explicitly set. Negative numbers are valid if you want to subtract from a company’s score based on a contact submitting the form. If the contact is not tracked and the form does not include a field mapped to **Company** or **Company Name** (on the Company object), no points are awarded to the company.</span>
- <span id="id4">**Adjust contact’s points**: More in depth than the company score action, this action allows you to multiply or divide a contact’s score. Select the operator and the amount you want to change the points by (for example: add 10, subtract 5, multiply by 3, divide by 2). If the form is collecting information which does not identify the contact, Campaign Studio saves the points to the anonymous contact record. If that anonymous contact record converts to or merges with a known contact record based on some identifying event (form submission with the unique identifier or link click in a message), the points will stay with the contact.</span>
- <span id="id4">**Modify contact’s segments**: This action enables users to change a contact’s segment membership when they submit a form. Type in the name of the segment you want to add a contact to or remove a contact from. You may use both fields in one Action, and may include multiple segments in either or both fields. Dynamic segments based on filters update based on information on the contact record. That includes the data from the form submission, as long as the fields map to Contact or Company fields. Typically, you will want to use static segments here. An example of a time when you could remove someone from a dynamic segment is for an event registration. You may build a filter-based segment for your invitation campaign, but once a contact submits the registration form you want to remove them from the source segment so they are removed from the invitation campaign.</span>
- <span id="id4">**Modify contact’s tags**: If you use tags for tracking, segmentation, and reporting, you may add or remove tags based on a form submission. To add or remove a tag that you have used before, select the tag from the list which displays when you click in the field. To find a tag, type the name to search and shorten the list. To adding a new tag, type the full tag name and press **Enter** on your keyboard to save the tag.</span>
- <span id="id4">**Record UTM Tags**: If the page your form is on has UTM tags, whether it is a Campaign Studio landing page or not, Campaign Studio can record those UTM tags to the contact record. This is useful for reporting on where your new leads and form submissions are coming from.</span>
- <span id="id4">**Remove contact from do not contact list**: If a contact has unsubscribed and this form gives you permission to send them emails again, use this action to remove the **Do Not Contact designation**.</span>
- <span id="id4">**Download an asset**: Using this option triggers an asset download when the contact clicks the **Submit** button. If you use categories to organize your assets and want the contact to receive the most recent published asset from a certain category, choose that option, and then choose the category to download from. Or, choose a specific asset to download. For more information on assets, see </span>[<span class="doc" id="id4">Assets</span>](/campaign-studio/components/assets)<span id="id4">.</span>
- <span id="id4">**Post results to another form**: Use this option to connect your Campaign Studio form with some other form. You may have forms in other tools which you use for tracking and reporting. Or, you may have back end forms triggering software instance creation. Enter the URL where the form should post to, and email address(es) for anyone who should receive error notifications. If the form you are posting to is behind a firewall, also enter the authorization header. If the field aliases (machine names) for any of the fields do not match, enter the alias the other form uses for any fields on the Campaign Studio form.</span>
- <span id="id4">**Push contact to integration**: Once a contact submits the form, you may want to push them to another piece of software you are using for contact management (such as a CRM). Be sure the plugin you want to push contacts is configured and published, then select it here. The Salesforce plugin enables users to select a campaign and a campaign status, beyond a basic push to Salesforce.</span>
- <span id="id4">**Send email to contact**: After a contact submits the form, you can do the following to send an email to them:</span>
    
    
    1. <span id="id4">Click the **Email to send** dropdown.</span>
    2. <span id="id4">Select an existing email or click **+New Email** to build a new email.</span>
    
    When an email is selected, the status of **Send to unsubscribed contacts** is displayed based on the setting of **Send to unsubscribed contacts** on the **Advanced** tab on the Emails page. For more information, see [Transactional and Marketing emails](/node/57576).
- <span id="id4">**Send email to user**: Select this option to email a Campaign Studio user after a contact submits a form. </span>
    
    
    1. Click the **Email to send** dropdown.
    2. Select an existing email or click **+New Email** to build a new email.
    
    When an email is selected, the status of **Send to unsubscribed contacts** is displayed based on the setting of **Send to unsubscribed contacts** on the **Advanced** tab on the Emails page. For more information, see [Transactional and Marketing emails](/node/57576).
    
    <span id="id4">Tokens in the email display the data from the contact who submitted the form, not for the Campaign Studio user receiving the email.</span>
- <span id="id4">**Send form results**: This is most commonly used to send an internal notification when a contact has submitted a form. You may also use it to send a confirmation of the submission to the contact, with the data the contact entered. Make the subject line clear which form the submission is for, particularly if you have several forms with the results going to the same person or people. The **Reply to contact option** sets the </span>`<span class="pre" id="id4">reply-to</span>`<span id="id4"> address on a notification email to the contact’s address, so if you click reply on the email your recipient will be the contact. If you have contact owners assigned in Campaign Studio, you can send the notification directly to the submitter’s owner. You may also decide to send the email directly to the contact. You may style the message section as you want. The tokens for the fields populate for any fields which exist when you add this action. If you later make changes to the fields, come back to this action and re-enter the field tokens. To do that, click in the **Message** box where to place your cursor. Click the field name on the right side and Campaign Studio inserts the token where your cursor is. To use a Template email instead of the basic form results template, select one from the **Import from an existing template** box. Finally, add the addresses for the people you want to receive the form results. Unlike the **Send email to user** action, **Send form results** emails are not limited to Campaign Studio users. You may send these to internal employees who are not users, third parties, or to distribution lists.</span>

<span id="adding-form">Adding forms to pages</span>
---------------------------------------------------

<span id="adding-form">You can add form code to your application or webpage in several different ways.</span>

<span id="adding-form">To embed multiple forms on one page, ensure that the form names and the form fields are unique. Each field must have a unique name.</span>

<div class="widget-status-message important" data-variant="important"><div class="widget-status-message-title">Important</div><div class="widget-status-message-description message">Forms are not supported in emails. Form tokens in emails do not convert into forms. Therefore, you must add the form to a landing page and then add the landing page link to the email.

</div></div>### <span id="adding-form">Shortcodes</span>

![Adding forms to pages](https://acquia.widen.net/content/xj9nazrxiu/jpeg/campaign-studio_adding-forms-to-pages.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)

<span id="adding-form">If you are adding a form to a Campaign Studio landing page or a Drupal, Joomla!, or WordPress page, you can use a shortcode. In each case, replace``ID#`` with the form’s ID number. You can find the ID in the forms list in the far right column, or if you are on the form, it is the number at the end of the URL. These options use JavaScript, and will keep the form up to date as you make changes.</span>

<span id="adding-form">Acquia recommends using the **Automatic Copy** option.</span>

<span id="adding-form">![Short code](https://acquia.widen.net/content/xjy8smq57c/jpeg/campaign-studio_form-short-code.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

- <span id="adding-form">**Campaign Studio Landing Page**: </span>`<span class="pre" id="adding-form">{form=</span><span id="adding-form"> </span><span class="pre" id="adding-form">ID#}</span>`
- <span id="adding-form">**Joomla!**: </span>`<span class="pre" id="adding-form">{mauticform</span><span id="adding-form"> </span><span class="pre" id="adding-form">ID#}</span>`
- <span id="adding-form">**WordPress**: </span>`<span class="pre" id="adding-form">[mautic</span><span id="adding-form"> </span><span class="pre" id="adding-form">type="form"</span><span id="adding-form"> </span><span class="pre" id="adding-form">id=ID#]</span>`

### <span id="adding-form">Automatic copy</span>

<span id="adding-form">![Automatic copy](https://acquia.widen.net/content/klrem3hfia/jpeg/campaign-studio_form-automatic-copy.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

<span id="adding-form">The **Automatic** option keeps your forms updated wherever you use this code. If you make changes to the form in your Campaign Studio instance, you do not need to worry about re-copying the code everywhere the form appears on your site. Features like autofill and progressive profiling will work only with the automatic copy options, not with manual copy. First, if you have a custom domain for your instance, be sure you are logged in using the custom domain rather than </span>`<span class="pre" id="adding-form">subdomain.mautic.net</span>`<span id="adding-form">.</span>

<span id="adding-form">**Via JavaScript**: Other than shortcodes, this is the recommended way to add forms to pages. Copy the line of code in the box and paste it into your website where you want the form to display.</span>

<span id="adding-form">**Via iframe**: While there may be cases where using an iframe is preferred for page load time or styling, iframes can be more difficult to manage. Be sure to adjust the width and height for the space you want the form to be in. Depending on the size of the screen your contact is using, they may still need to scroll within the iframe on your page to see all the fields. You may enter a custom error message to display in place of the form, in case the contact’s browser does not support iframes. To do so, edit the text between the </span>`<span class="pre" id="adding-form"><p></span>`<span id="adding-form"> and </span>`<span class="pre" id="adding-form"></p></span>`<span id="adding-form"> tags before copying the code and pasting it on your website where the form should display.</span>

### <span id="adding-form">Manual copy</span>

<span id="adding-form">![Manual copy](https://acquia.widen.net/content/n59iozanl8/jpeg/campaign-studio_form-manual-copy.jpeg?position=c&color=ffffffff&quality=80&u=xizedw)</span>

<span id="adding-form">The Manual copy option gives you a little bit more flexibility to extend forms with JavaScript snippets and custom styling. It is more manual, and any changes made to the form are not displayed on your page unless you re-copy and paste the HTML code. Ensure that you are logged into your instance using your custom domain, if you have one.</span>

1. <span id="adding-form">Copy the JavaScript code in the top box and paste it into the head or body of your page. If you have multiple Campaign Studio forms on the same page, you add this once.</span>
2. <span id="adding-form">Copy the HTML code in the bottom box and paste it where you want the form to display on your page.</span>
3. <span id="adding-form">If you have **Render Style** set to **Yes** in the form editor, the styling for each field is in this code. If **Render Style** is **No**, styling code will not be in and the form will use the default CSS for your page.</span>

<span id="adding-form">If you are a Campaign Studio Cloud subscriber and have more questions about forms, </span>[<span class="std std-ref" id="adding-form">create a Support ticket</span>](/service-offerings/support#contact-acquia-support)<span id="adding-form">.</span>

<span id="create-form">Forms page</span>
----------------------------------------

<span id="create-form">The **Forms** page lists all the forms that you have created, and provides the following information about each form.</span>

<table class="table verticaltable docutils align-default"><thead><tr class="row-odd"><th class="head"><span id="create-form">**Column**</span></th><th class="head"><span id="create-form">**Description**</span></th></tr></thead><tbody><tr class="row-even"><td><span id="create-form">**NAME**</span></td><td><span id="create-form">The title of the form.</span></td></tr><tr class="row-odd"><td><span id="create-form">**\#CATEGORY**</span></td><td><span id="create-form">The category assigned to the form.</span></td></tr><tr class="row-even"><td><span id="create-form">**RESULTS**</span></td><td><span id="create-form">The number of contacts who submitted the form.</span></td></tr><tr class="row-odd"><td><span id="create-form">**DATE CREATED**</span></td><td><span id="create-form">The date when the form was created.</span></td></tr><tr class="row-even"><td><span id="create-form">**MODIFIED DATE**</span></td><td><span id="create-form">The last date when the form was modified.</span></td></tr><tr class="row-odd"><td><span id="create-form">**CREATED BY**</span></td><td><span id="create-form">The user who created the form.</span></td></tr><tr class="row-even"><td><span id="create-form">**ID**</span></td><td><span id="create-form">The ID of the form indicating the position at which the form is created in Campaign Studio. For example, an ID of 4 indicates that it is the fourth form that is created in Campaign Studio.</span></td></tr></tbody></table>

### <span id="create-form">Search</span>

<span id="create-form">Several operators and commands help you to find forms that meet a certain criteria. To see the list of options, click the question mark next to **Filter**.</span>

### <span id="id5">Batch actions</span>

<span id="id5">With batch actions, you can delete or rebuild the cache for multiple forms simultaneously.</span>

- <span id="id5">To select all forms, select the checkbox at the top of the checkbox column.</span>
- <span id="id5">To select specific forms, select the checkbox for each of the forms individually.</span>

<span id="id5">After selecting the checkboxes, click the green arrow at the top of the checkbox column and select **Rebuild Cache** or **Delete Selected**.</span>

<div class="admonition note"><span id="id5">Note</span>

<span id="id5">A form’s cache must be rebuilt if you make any changes to the fields of the form after publication.</span>

<span id="id5">If you create or change the customer domain for an instance that already contains existing forms, you must rebuild the cache for all forms in the instance. This can occur when </span>[<span class="std std-ref" id="id5">creating a template instance in Campaign Factory</span>](/campaign-studio/add-ons/campaign-factory/configuration/instances#creating-a-template-instance)<span id="id5">.</span>

</div><span id="id5">For each form, you can view and do the following actions by selecting its checkbox and clicking its associate dropdown arrow:</span>

- <span id="id5">**Edit** - To edit the form.</span>
- <span id="id5">**Clone** - To clone the form.</span>
- <span id="id5">**Preview** - To preview the form.</span>
- <span id="id5">**Results** - To view the **Results** page for the form.</span>
- <span id="id5">**Delete** - To delete the form.</span>

<span id="id5"><meta content="width=device-width, initial-scale=1.0" name="viewport"></meta></span></div>