--- title: "Adding Newsletters" slug: "adding-newsletters" updated: 2024-11-12T14:48:09Z published: 2024-11-12T14:48:09Z canonical: "help.nexudus.com/adding-newsletters" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.nexudus.com/llms.txt > Use this file to discover all available pages before exploring further. # Adding Newsletters You can create newsletters using the built-in editor. Its drag-and-drop elements make it a breeze to add and edit content. You can edit the HTML or use dynamic tokens to further customize your newsletters. *For example, include subscriber names in the content or add some code to include animated elements in your newsletters.* --- ![AddingNewsletters](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/AddingNewsletters.gif) 1. Log in to [dashboard.nexudus.com](https://dashboard.nexudus.com/) if you aren't already. 2. Click [**Community > Newsletters**](https://dashboard.nexudus.com/content/newsLetters). 3. Click on **Add newsletter**. 4. Add your newsletter's **Subject**. 5. Select your **Location**. 6. Drag and drop the different elements you want to add onto your newsletter. 7. Add your content to each element. 8. Click the **Save Changes** button. All set! Your newsletter is now ready to [test](/docs/testing-newsletters) and [send](/docs/sending-newsletters) to your subscribers. --- ## Newsletter Dynamic Fields You can add multiple dynamic fields to your newsletters to customize them. All the available fields are listed and detailed below: ### {unsubscribe} Adds link that customers can click on to unsubscribe and stop receiving your newsletter. Giving your customers the option to 'unsubscribe' from your newsletter is a **legal requirement** in multiple countries including the United Kingdom and the United States. For the link to work you need to add the token in the newsletter's code using the snippet below. ``` Unsubscribe ``` ### {fullname} Newsletter subscriber's full name. This information is pulled from the subscriber record, not the customer's account. For example, if a customer's name was originally **John Doe** and you change it to **John Dowe**, the {fullname} dynamic field will still use **John Doe** until you manually change their full name via their corresponding subscriber record. ### {firstname} Newsletter subscriber's first name. This information is pulled from the subscriber record, not the customer's account. For example, if a customer's first name was originally **John** and you change it to **Jon**, the {firstname} dynamic field will still use **John** until you manually change the first name via their corresponding subscriber record. ### {lastname} Newsletter subscriber's last name. This information is pulled from the subscriber record, not the customer's account. For example, if a customer's last name was originally **Doe** and you change it to, the {lastname} dynamic field will still use **Doe** until you manually change the last name via their corresponding subscriber record. ### {companyname} Newsletter subscriber's company name. This information is pulled from the subscriber record, not the customer's account. For example, if a customer's company name is **Business** in their account and you add {companyname} to your newsletter, **Business** won't appear in the newsletter unless you manually add it to the *Company name* field in their corresponding subscriber record. ### |email| Newsletter subscriber's email address. ### {businessUrl} Members Portal URL. ### |suid| Newsletter subscriber's unique ID. ### |nid| Newsletter subscriber's integer ID ### |nuid| Newsletter's unique ID.