Static Forms

Use static forms to:

  • Add or remove contacts from lists/unsub lists,

  • Trigger campaigns,

  • Set contact data on Core and Data Tables,

  • Send notification emails when the form is submitted and a landing page upon submission.

Note: static forms do not prefill with contact data and you can only submit to one core table at a time.

The following Defaults and Commands allow you to configure your form.

Defaults

The Form Handler, Account ID, and Table ID defaults determine what domains and IDs are associated with the form.

Form handler

Delegated domain can be used.

<form action="http://domain.example.com/s/" method="post">

_account_id

ID of account that data is being sent to, you can find this by hovering over the account name in the breadcrumb trail in Adestra.

<input type="hidden" name="_account_id" value="180">

_table_id

ID of the core table that data is being sent to.

<input type="hidden" name="_table_id" value="1">

Commands

The commands tell Adestra how to process your form, e.g. define dedupe fields, lists to update, etc.

Tip: use form validation, e.g. CAPTCHA, when using commands to trigger a send, unsubscribe, etc. to protect against bot-submission of forms and bot-triggered sends.

_dedupe

Lets Adestra know which field is the dedupe value, not defining this may give you duplicate records on your Core Table. We recommend using email, as it will always be unique.

<input type="hidden" name="_dedupe" value="1"> <input type="hidden" name="_email_field" value="1.email">

1.email must relate to the Core Table defined under _table_id, so if you are using Core Table 2 the value should be 2.email.

_static_update

Overrides the dedupe for adding contacts to the Core Table, always needs a value of 1.

<input type="hidden" name="_static_update" value="1">

_rp

The page a contact will be sent to on successfully submitting the Form. If omitted a default page is used.

<input type="hidden" name="_rp" value="http://hosted.adestra.com/adestra/thanks.html">

_ep

The page a contact will be sent to if the contact is already on the core table.

<input type="hidden" name="_ep" value="http://hosted.adestra.com/adestra/error.html">

Note: For both _rp and _ep, you can also use form:<form_id> (or form_ssl:<form_id>) to send the contact to a prefilled form.

_list_id

ID of the list a contact will be added to, multiple lists require a new command for each list.

<input type="hidden" name="_list_id" value="13">

_unsub_list_id

ID of list contact will be unsubscribed from.

<input type="hidden" name="_unsub_list_id" value="14">

_unsublist_add

ID of unsublist the contact will be added to.

<input type="hidden" name="_unsublist_add" value="15">

_unsublist_remove

ID of unsublist the contact will be removed from.

<input type="hidden" name="_unsublist_remove" value="13">

_notify

Sends a notification email to an Adestra user when a form is submitted. The value should be the user's ID, to send to multiple users separate the values with a comma.

<input type="hidden" name="_notify" value="1,2">

Sending a Campaign

This will send a copy of a particular campaign to the new or updated contact, all are mandatory and require a campaign ID and launch ID.

Tip: use form validation, e.g. CAPTCHA, when using a form to trigger a campaign to protect against bot-submission of forms and bot-triggered sends.

_send_copy

<input type="hidden" name="_send_copy" value="1">

_send_dupe

<input type="hidden" name="_send_dupe" value="1">

These above need to be set as 1.

_copy_campaign_id

<input type="hidden" name="_copy_campaign_id" value="9">

_copy_launch_id

<input type="hidden" name="_copy_launch_id" value="12">