The extra Subscriber Profile Fields in Dada Mail are saved in the
dada_profiles table. Right now, there's a limit of 100 extra columns and each column is given the data type of,
The Subscriber Profile Fields feature in Dada Mail requires that you use one of the supporting SQL backends. Currently, Dada Mail supports MySQL, Postgres and SQLite.
Most likely, if you ever have to downgrade Dada Mail, these extra fields shouldn't hurt too much to keep around. From my tests, Dada Mail will simply just ignore the extra fields.
Adding a new subscriber field is pretty easy. Log into the list control panel with the Dada Mail Root Password (very important) to any list. On the left hand menu, under, Profiles, click, Profile Fields
This screen will allow you to add/remove the Subscriber Profile Fields. This screen will also let you set a fallback value. The fallback value is used in mailmerging and is used as the value fo the field tag when no value is present.
The fallback value is saved in the dada_settings table in the fallback_field_values setting.
Please note that removing any Subscriber Profile Fields will permanently delete all the information that once was saved in this particular field for ALL Mailing Lists.
The other thing to note is that Subscriber Profile Fields are GLOBAL, meaning, they'll be there for each Mailing List that Dada Mail manages.
Mail Merging in Dada Mail in mailing list messages using your new Subscriber Profile Fields is pretty easy:
Say you have a field named, first_name. To use the value of the saved field in an email message, you'd write the field as a tag, like this: <!-- tmpl_var subscriber.first_name -->. It would look like this in your actual message:
Hello, <!-- tmpl_var subscriber.first_name --> It's really nice to talk to you! -- Me.
Mail Merging works for almost every single type of email message Dada Mail can send out.
You can now make a query on your subscription list to send to only part of your mailing list. For example, if you have a field named, "city", you can tell Dada Mail, "only send to people whose, "city" value is set to, 'Denver'.
Currently, this is done in the, "Send a Message" and, "Send a Webpage" screens. Click the, +/- Partial Sending Options. You'll be presented with a form that allows you to make simple queries and give you a preview of who's going to the message.
The subscription process is similar to previous versions of the program, except that the subscription form now supports capturing any Subscriber Profile Fields present.
Currently, all subscription fields will be shown, except (by default), Subscriber Profile Fields that are prefixed with an underscore ("_"). For example, the field,
Will be shown! The field,
Will not. Consult the Config.pm file for how to set the special prefix.
Currently, all the subscription fields are optional, except the email address.
You may acquire the HTML code needed to embed the subscription form in a webpage in the usual location: Under Appearance and Templates , click on, Subscription Form HTML.
There are a few difference internally with the subscription process. The largest is that all subscription requests by users will first have the subscriber information saved in the, "sub_confirm" sublist. This is where the information filled out in your subscription form is saved, before a subscription is confirmed. Once a subscription is confirmed, the information is moved to the main, "list" sublist.
A similar scenario takes place for unsubscriptons: The subscriber is first put on a, "unsub_confirm" sublist and is taken off this list, as well as the main, "list" sublist once the confirmation process is completed.
Because of this, you will no longer be able to use complete confirmaton URLS, (URLS that have the pin number and email address embeded in the URL) in any place other than in the subscription and unsubscription confirmation email messages.
Every single instance of the subscription form is handled by one template file, living in the dada/DADA/Template/templates directory called,
subscription_form_widget.tmpl. Changes to this file will affect every instance of the subscription form in the program.
The file type you need to import your subscribers in must be in CSV format. The order of the fields in that CSV format should be displayed at the top of the screen.
You can edit an individual's subscriber information in the list control. Under, Your Subscribers, click on, View. You'll be presented with a table of your subscribers, with all their subscription information. Clicking on the email address of the subscriber will bring you to a screen to edit the subscription information. Pretty simple.
The HTML Screen and Email Template parts of Dada Mail all use the same system. See: