> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/create-and-send-newsletters-to-partners.md). # Create & Send Newsletters to Partners Use *Newsletters* in impact.com to send email and in-app newsletters to your joined partners. These newsletters can be used for correspondence, upcoming changes about your program, special promotions, and more. {% hint style="warning" %} **Important:** Newsletters can only be sent to partners who are already in the impact.com network. Imported prospects or out-of-network contacts will not receive newsletters. To reach out to new or out-of-network prospects, use [email workflows](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md) instead. {% endhint %} {% embed url="" %} {% stepper %} {% step %} ## Initial setup 1. From the left navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **Partners** → **Automation** → [**Newsletters**](https://app.impact.com/secure/advertiser/fr/newsletter-ui.ihtml). 2. Select **Create Newsletter**. 3. Enter the *Newsletter Name.* {% endstep %} {% step %} ## Define your audience segment Determine which partners will receive the newsletter. 1. In the Partner Segment section, select **Add Segment**. 2. You now have two choices: * **Use a pre-existing segment:** Select an existing segment from the **Select Segment** drop-down menu. * **Create a new segment:** Select **Create Segment** and then specify the conditions that determine which partners are included. For a complete guide on how to set up these rules effectively, refer to the [Create a Partner Segment](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/segments/create-a-partner-segment.md) article. 3. Optionally, select **Preview Segment Partners** to review the list of recipients. 4. Select **Save**. {% endstep %} {% step %} ## Enter your email details & content 1. In the *Email* section, select **Add Email**. 2. Optionally, ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Toggle on]** the messaging template setting to apply an existing messaging template, then select a template from the ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c2cb550b55c51ea1eeff0acbd6f437a03b621a2c%2F60d033ae8a04c14498d5229c3c0160ac05feea7f605dbd770741793c900469f0.svg?alt=media) **\[Drop-down menu]**. 3. Fill in the essential email details: * **Send from:** The name partners will see in their inbox. The sender email address is filled in automatically and can’t be changed. * **Reply to:** The email address that receives partner replies. * **CC/BCC:** ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Toggle on]** to send a copy to one internal CC and one BCC address. 4. Create your newsletter content using one of the following methods: * **Use AI to generate the content:** 1. Select **Help me write** to expand the section. 2. Enter a short paragraph describing the content of your newsletter. 3. Optionally, ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Toggle on]** **Advanced Options** to further refine the AI's output by providing *Additional examples* or *Additional context*. 4. Select **Generate**. 5. Select **Insert** to add the generated text to the *Content* section. * **Write the content manually:** Enter your text directly into the **Subject** and **Content** fields. {% endstep %} {% step %} ## Insert dynamic elements Use the *Insert dynamic elements into the email content* section above the editor to add tokens, ads, and signup links. * **Dynamic Tokens:** Personalize your email with partner-specific information (for example, `{firstName}`). 1. Place your cursor where you want the token to appear. 2. Search for or select a token from the **Select a Token** drop-down menu. 3. Select **Insert**. 4. Refer to the [Dynamic fields reference](#dynamic-fields-reference) for the available tokens. * **Ads:** Add your active ads to the email without copying ad IDs by hand. 1. Place your cursor where you want the ads to appear. 2. From the **Select a Token** drop-down menu, select **Ads**, then select **Insert**. The *Select Ads To Insert* slideout opens and lists your active ads. Each ad shows its image, name, ad ID, ad type, expiration date, and when it was last updated. * Optionally, use the search bar or the *Ad Type* and *Labels* filters to find specific ads. 3. Select the checkbox on each ad you want to insert. To select every ad in the list, select **Select all**. You can insert a maximum of 20 ads per email. The *inserted* counter shows how many ads the email already contains. Larger partner segments allow fewer ads, so check the ad code limitations in the [Dynamic fields reference](#dynamic-fields-reference) to prevent delivery failure. 4. Select **Insert Ads**. The button shows how many ads you selected (for example, **Insert 1 Ad**). An ad token for each selected ad is added to your email content (for example, `{adcode_1122330}`). If you select **Back to Email** before selecting **Insert Ads**, your ad selection is discarded.
* **Signup Link:** Add a button that links to a specific set of template terms. 1. Select template terms from the **Select a Template** drop-down menu. 2. Select **Insert**. {% endstep %} {% step %} ## Review & save your content 1. Select **Preview** for a preliminary display of how the newsletter will look. 2. Optionally, select **Send test email** to send a draft copy to your own inbox for a final review. 3. Select **Done** to save your content and return to the main newsletter setup screen. {% endstep %} {% step %} ## Choose the contact type Select which of the partners' email addresses should receive the newsletter. 1. In the *Contact Type* section, select one or more options: * **Newsletter (Recommended):** Sends to the partner's registration email or the one specified in their profile. * **Custom Contact:** Sends to a specific contact you have configured on the partner's profile. For more information, refer to the [Get Partner Contact Information](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-management/get-partner-contact-information.md#add-a-contact-to-your-contact-list) help article. {% endstep %} {% step %} ## Add an In-app announcement (Optional) Send an accompanying notification that will appear directly within the impact.com platform: 1. ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Toggle on]** the **In-app Announcement** feature. 2. A content editor will appear. You can either: * Leave it as is to use the same content you wrote for your email. * Edit the text to create a custom message for the in-app announcement. {% endstep %} {% step %} ## Schedule your newsletter (Optional) If you want to send your newsletter at a future time, you must schedule it. 1. ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Toggle on] Schedule**. 2. Set a future **Date and time** for when the newsletter should be sent. 3. Select the correct **Timezone** for the schedule. {% endstep %} {% step %} ## Finalize & send * **To send or schedule:** Select **Send Newsletter** (or **Schedule Newsletter** if the schedule is toggled on). * **To send a test:** Select **Send Test Newsletter** to send a copy to yourself or your team. * **To save your work:** Select the **Save as draft** drop-down menu for two options: * **Save and exit:** Save your work and leave the page. * **Save and stay on the same page:** Save your work but stay on the page to keep editing. {% endstep %} {% endstepper %}
Dynamic fields reference {% hint style="danger" %} **Attention:** Tokens are case sensitive and must not contain extra formatting (for example,`{firstName}` is valid but `{FirstName}` is not.) {% endhint %} | Name in drop-down menu | Token | Description | | ----------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Ads | `{adcode_}` |

Populates with the full ad listing of the specified \ value (for example, {adcode\_1122330}).

To add ad tokens without typing ad IDs, select Ads from the Select a Token drop-down menu.

To prevent delivery failure, ensure your segment size does not exceed the maximum limits based on your newsletter's ad code count.

Ad code limitations

Number of Adcodes/Limit

Maximum of 1: up to 60,000 partners
Maximum of 5: up to 30,000 partners
Maximum of 10: up to 20,000 partners
Maximum of 20: up to 5,000 partners

| | Partner ID | `{mpid}` | Populates with the ID value of the partner’s account (e.g., 98765). | | Partner company name | `{mpname}` | Company name. | | Partner First Name | `{firstName}` | Populates with the first name of the partner (e.g., John). | | Partner Last Name | `{lastName}` | Populates with the last name of the partner (e.g., Doe). | | Current Day | `{currentDay}` | Populates with the current date (e.g., January 19, 2038). | | Current Time | `{currentTime}` | Populates with the full date in ISO format (e.g., 19-Jan-2038 03:14:08 UTC). | | Current month and year | `{currentMonthYear}` | Populates with the current month and year (e.g., January, 2038). | | Opt-out URL | `{unsubscribeUrl}` |

URL to unsubscribe from the newsletter.

All email newsletters must include a visible and functional unsubscribe link. If you don’t add an unsubscribe token, our system will automatically append one at the end of your newsletter to ensure compliance.

| | Name of the program | `{programName}` | The program name. | | Program logo source URL | `{programLogoSrc}` | The source URL of the program logo. |
{% hint style="success" %} **Note:** After a newsletter is sent, it can take between one hour and a full day (24 hours) for the [associated metrics](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/review-newsletter-engagement-performance.md) to fully update. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/create-and-send-newsletters-to-partners.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.