...
You can use subscribe.aspx as the form handler from a form hosted on your Web site. It allows you to offer your Web site visitors a way to sign up for your newsletter(s), while giving you full control on the look & feel of the signup form. By default the signup process uses the double opt-in method (confirmed opt-in).
The signup form must be structured as described below:
- the field “name” attribute for each field must match the corresponding code that can be located under Settings > Codes Table in your MailUp admin console
- the field "type" is entirely up to you
Codes Table
Info | ||
---|---|---|
| ||
The field code uses the word "CAMPO" because MailUp's original source code was developed in Italy. "Campo" means "Field" in Italian |
Subscription form action
...
language | html/xml |
---|
...
...
...
...
The parameters for calling subscribe.aspx are described below.
...
...
...
...
Info | ||
---|---|---|
| ||
In case a user subscribes to more than one list, the system will still only send one confirmation request message, which will allow the user to confirm their subscription to all the lists included in the signup request. Note that the system will use the message templates (e.g. subscription confirmation request message and subscription confirmation message), as well as the Web page templates defined for the first List that the user was subscribed to. |
The “value” field must contain the ID of the list the user will be subscribed to. You can see that numeric value shown in the MailUp admin console under Settings > Edit lists or looking at the dropdown menu at the top left of the page. In the image below, the list called "Business" has value=3.
Mobile phone number (optional)
You can use the mobile number field to record the customer's mobile number in the database and be able to send text messages to them.
Code Block | ||
---|---|---|
| ||
<input id="prefix" value="001" type="text" name="prefix" />
<input id="sms" type="text" name="number" /> |
Please note that the field “prefix” (international prefix) needs not be entered as a separate field, it can also be inserted in the field “number”. We recommend passing it as a separate field for clarity’s sake.
Groups (optional)
...
...
...
...
...
...
...
...
...
...
...
...
...
...
In the example above, the user is automatically subscribed to groups 2, 8 and 10. The Group IDs are listed in your MailUp admin console under Settings > Codes table.
Other personal data fields (optional)
...
...
...
...
...
...
Xmlsubscribe.aspx (User subscription)
...
...
...
...
...
...
Group
...
N
...
Groups to which to subscribe the user
...
Confirm
...
N
...
Parameter to enable or disable confirmation request email. Accepted values: 0/1. Default value: 1
...
csvFldNames
...
N
...
Personal data codes (separated by the ";" character)
...
csvFldValues
...
N
...
Values related to personal data codes (separated by the ";" character)
...
...
Dynsndmail(3)
...
N
...
"dynamic sender e-mail address" Sender address in the confirmation request email (If blank, default value for the list will be used)
...
dynsndname(3)
...
N
...
"dynamic sender name" Sender name in the confirmation request email (If blank, default value for the list will be used)
...
RESPONSE VALUES
CODE | DESCRIPTION |
0 | Operation completed successfully / User already subscribed |
1 | Generic error |
2 | Invalid email address or mobile number |
Xmlchksubscriber.aspx (User subscription check)
This function performs a check on a user subscription status
URL
The URL to use depends on your MailUp account's unique URL. If your MailUp admin console address is xyzw.espsrv.com, the correct action URL for the form (the URL of the form handler) will be http://xyzw.espsrv.com/frontend/Xmlchksubscriber.aspx
REQUEST PARAMETERS
Name | Mandatory? | Description |
ListGuid | Y | Alphanumeric code associated to a distribution list |
List | Y | List ID |
N (1) | User email address | |
Sms | N (1) | User mobile number, with international prefix (2) |
...
RESPONSE VALUES
CODE | DESCRIPTION |
1 | Generic error / user not subscribed |
2 | User subscribed (OPT-IN) |
3 | User unsubscribed (OPT-OUT) |
4 | User subscription to be confirmed (PENDING) |
Info |
---|
NOTE: Code 1 is given as output value both in case of error (e.g. when ListGuid code does not match ListID) and when the user is not a subscribed user. |
Xmlunsubscribe.aspx (User unsubscription)
This function forces the unsubscription of a subscriber from a list.
URL
The URL to use depends on your MailUp account's unique URL. If your MailUp admin console address is xyzw.espsrv.com, the correct action URL for the form (the URL of the form handler) will be http://xyzw.espsrv.com/frontend/Xmlunsubscribe.aspx
REQUEST PARAMETERS
Name | Mandatory? | Description |
ListGuid | Y | Alphanumeric code associated to a distribution list |
List | Y | List ID |
N (1) | User email address | |
Sms | N (1) | User mobile number, with international prefix (2) |
...
RESPONSE VALUES
CODE | DESCRIPTION |
0 | User unsubscribed successfully |
1 | Generic error |
3 | User unknown / already unsubscribed |
Info |
---|
NOTE: If successfully unsubscribed, the user will be moved to unsubscribers and will receive an unsubscription confirmation email, if this option has been selected |
Updsubscriber.aspx (User update)
This function allows to update a user's personal data.
URL
The URL to use depends on your MailUp account's unique URL. If your MailUp admin console address is xyzw.espsrv.com, the correct action URL for the form (the URL of the form handler) will be http://xyzw.espsrv.com/frontend/Updsubscriber.aspx
REQUEST PARAMETERS
Name | Mandatory? | Description |
ListGuid | Y | Alphanumeric code associated to a distribution list |
List | Y | List ID |
N (1) | User email address | |
Sms | N (1) | User mobile number, with international prefix (2) |
Replace | N | Parameter to enable or disable group replacement for the specified user. Accepted values: 0/1/false/true – Default value: false |
Group | N | Groups to which to subscribe the user |
csvFldNames | N | Personal data codes (separated by the ";" character) |
csvFldValues | N | Values related to personal data codes (separated by the ";" character) |
...
RESPONSE VALUES
...
CODE
...
DESCRIPTION
...
0
...
Data updated successfully
...
1
...