Search the Omeda Knowledge Base

Dragon Forms URL Structure and Appending Parameters

Dragon URLS with parameters attached should follow the format shown below. That is, it should begin with the base Dragon form URL, include a ? before the first parameter, and an & before each additional parameter.

Example: https://subdomain.dragonforms.com/formcontext?parameter1=x&parameter2=y&parameter3=z

  • Blue: Dragon form URL
  • Red: the ? indicates the beginning of a query string. This must always be used if you want to append parameters.
  • Green: indicates the various parameters appended to the URL. Examples would be pk=promokey, em=clientsuccess@omeda.com, r=encrypted_customer_id, etc.
  • Purple: the & indicates that an additional parameter is being added to the URL

In most cases, you should use the live URL in the format shown above. However, there are some instances where the publisher has been using the longer form of the Dragon form URL shown below. In this case, the form context has been included as the first parameter following the ? query indicator. In this case, add the next parameter with an &.

Formats of your Dragon URL:

Standard: https://subdomain.dragonforms.com/formcontext
Longer Version (adding the bolded part to the URL): https://subdomain.dragonforms.com/init.do?omedasite=formcontext&parameter2=y&parameter3=z

Common Standard Parameters to Use:

em=       Email Address

r=            Encrypted Customer ID (this r is case sensitive, other parameters are not case sensitive)

pk=        Promo Code

ln=          Last Name

an=        Postal ID (the postal ID tied to that product)

Examples

New Paid form, assuming Promo is “newoffer”

https://omeda.dragonforms.com/OSM_paidn?pk=newoffer

or

https://omeda.dragonforms.com/init.do?omedasite=OSM_paidn&pk=newoffer

Renewal:

https://omeda.dragonforms.com/OSM_renew?r=@{encrypted_customer_id}@&pk=@{promo_code}@

or

https://omeda.dragonforms.com/init.do?omedasite=OSM_renew&r=@{encrypted_customer_id}@&pk=@{promo_code}@

Email Builder (Omail) Merge Variables:

When you are using the Omail Merge Variable Tags, they will show up in the Omail Message Content Pleat (see example from a paid renewal effort where Promo Code is part of the file and you pull it as a merge variable and not a constant)

https://omeda.dragonforms.com/init.do?omedasite=OSM_renew&r=@{encrypted_customer_id}@&pk=@{notice_promo_code}@

From Omail Pleat of the available Merge Variables:

Last Updated On February 21, 2019
Knowledge Base Feedback