Difference between revisions of "Customizing Campaign Data"
m |
m |
||
(17 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | [[ | + | [[ File:AR-LCPforms-defineFields-tab.png ]] |
− | + | The most basic capture form used by TrafficWave.net captures the subscriber's e-mail address. | |
+ | |||
+ | However, your TrafficWave.net AutoResponder Campaign is designed to be a fully usable contact management system. This creates the ability to collect more data from your subscribers than just a basic name/e-mail combination. | ||
Your Capture Forms can be "customized" to contain any number of additional data fields. Further, these fields can be specified as ''required'' or ''optional'' for subscribers wishing to join your Campaign. | Your Capture Forms can be "customized" to contain any number of additional data fields. Further, these fields can be specified as ''required'' or ''optional'' for subscribers wishing to join your Campaign. | ||
− | + | To access these features, select the '''Define Capture Fields''' link under your Campaign's '''''Capture Pages/Forms''''' tab. | |
− | + | == Capturing Subscriber Names == | |
Subscriber Names can be specified as either a single field (first and last name collected together one text box) or split fields (first and last names collected separately). This flexibility is necessary when [[Letter Tokens | using tokens]] in your AutoResponder Letters. | Subscriber Names can be specified as either a single field (first and last name collected together one text box) or split fields (first and last names collected separately). This flexibility is necessary when [[Letter Tokens | using tokens]] in your AutoResponder Letters. | ||
{{mbox | small = left | text = Tokens allow Letters to be personalized - like <i>"Hello, Robert..."</i>}} | {{mbox | small = left | text = Tokens allow Letters to be personalized - like <i>"Hello, Robert..."</i>}} | ||
− | |||
== Additional Standard Data Fields == | == Additional Standard Data Fields == | ||
Line 30: | Line 31: | ||
* Gender (M or F) | * Gender (M or F) | ||
+ | {{ mbox | type = small | text = These '''Standard Fields (or Tokens)''' are considered ''global'' tokens for each subscriber - meaning that these tokens contain subscriber data that is available to multiple Campaigns. For more on using tokens, see [[Letter Tokens]]}} | ||
== Custom Data Fields == | == Custom Data Fields == | ||
Line 53: | Line 55: | ||
{{mbox | type = caution | text = We advise using <b>pulldowns</b> and <b>checkboxes</b> instead of text fields whenever possible. This will allow these fields to be easily searchable later! }} | {{mbox | type = caution | text = We advise using <b>pulldowns</b> and <b>checkboxes</b> instead of text fields whenever possible. This will allow these fields to be easily searchable later! }} | ||
+ | |||
=== Hidden Fields === | === Hidden Fields === | ||
''Advanced''. If you wish to pass a piece of data along with a form that does not require anything from the subscriber, you may do so with a hidden field. | ''Advanced''. If you wish to pass a piece of data along with a form that does not require anything from the subscriber, you may do so with a hidden field. | ||
+ | |||
+ | |||
+ | {{ mbox | type = small | text = These '''Custom Fields (or Tokens)''' are available only to a specific Campaign. They are used to collect and store subscriber information specific to a single Campaign. For more on using tokens, see [[Letter Tokens]]}} | ||
+ | |||
+ | |||
+ | |||
+ | ==''See Also''== | ||
+ | [[Letter Tokens]] | ||
+ | |||
[[Category: AutoResponder]] | [[Category: AutoResponder]] |
Latest revision as of 14:52, 1 February 2021
The most basic capture form used by TrafficWave.net captures the subscriber's e-mail address.
However, your TrafficWave.net AutoResponder Campaign is designed to be a fully usable contact management system. This creates the ability to collect more data from your subscribers than just a basic name/e-mail combination.
Your Capture Forms can be "customized" to contain any number of additional data fields. Further, these fields can be specified as required or optional for subscribers wishing to join your Campaign.
To access these features, select the Define Capture Fields link under your Campaign's Capture Pages/Forms tab.
Contents
Capturing Subscriber Names
Subscriber Names can be specified as either a single field (first and last name collected together one text box) or split fields (first and last names collected separately). This flexibility is necessary when using tokens in your AutoResponder Letters.
Tokens allow Letters to be personalized - like "Hello, Robert..." |
Additional Standard Data Fields
The additional standard options for collecting data in your autoresponder include:
- Salutation (Mr., Mrs., Ms., and Dr.)
- Company Name
- Country
- Address Line 1
- City
- State/Province
- Postal Code
- Phone Number
- Fax Number
- Birthday
- Gender (M or F)
These Standard Fields (or Tokens) are considered global tokens for each subscriber - meaning that these tokens contain subscriber data that is available to multiple Campaigns. For more on using tokens, see Letter Tokens |
Custom Data Fields
In addition to the standard options, each Campaign can utilize up to nine custom data fields. Custom data fields allow the marketer to collect very specific information from prospective subscribers such as:
Pulldown List
A pulldown list allows the marketer to give a subscriber choices that can be used later to create subsets (or new lists) of subscribers.
Text Fields
A text field can be used to collect information such as a URL. A text field can also be used as an Other box if a subscriber cannot select from a Pulldown List.
Checkboxes
Simple "Yes" or "No" questions can be simplified with checkboxes.
We advise using pulldowns and checkboxes instead of text fields whenever possible. This will allow these fields to be easily searchable later! |
Hidden Fields
Advanced. If you wish to pass a piece of data along with a form that does not require anything from the subscriber, you may do so with a hidden field.
These Custom Fields (or Tokens) are available only to a specific Campaign. They are used to collect and store subscriber information specific to a single Campaign. For more on using tokens, see Letter Tokens |