Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update campaign_builder.rst - Added Transactional No DNC text to M5 branch #136

Open
wants to merge 3 commits into
base: 5.x
Choose a base branch
from

Conversation

jos0405
Copy link

@jos0405 jos0405 commented Jan 13, 2023

Added Transactional No DNC text to M5 branch

Added Transactional No DNC text to M5 branch
Added reference to Email settings
Copy link
Member

@RCheesley RCheesley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be best to have a section on the Channels > emails.rst file which explains Transactional v Marketing (and maybe also Personal emails and form results emails) with the key differences.

We could then link to it from within this table, making it less of a wall of text in a small table cell!

WDYT @jos0405 ?

@@ -79,6 +79,7 @@ The actions that Mautic offers in a Campaign include:
- Sends a Webhook to a defined URL, using the GET, POST, PUT, PATCH, or DELETE methods. Headers and data is customizable, and support the use of tokens, such as Contact fields and the Contact's IP address. For example, ``{contactfield=firstname}``
* - **Send Email**
- Sends a transaction or marketing Email to the selected Contact. You can send a transactional Email to the Contact multiple times. You can only send a marketing Email to the Contact once across multiple sources. If the Contact has already received this Email from another source or the current Campaign, they aren't sent the Email again and the Contact progresses through the Campaign.
- Emails can be transactional or marketing. Marketing emails will obey Email Channel's Do Not Contact setting of the contact, Transactional Emails will disregard the Do Not Contact value. This allows to send Transactional emails as campaign step to Contacts even if they opted out to recieve Marketing emails via standard unsubscribe action and have DNC set as 'no'. Enable transactional email ignoring DNC can be turned on in Email Settings.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Emails can be transactional or marketing. Marketing emails will obey Email Channel's Do Not Contact setting of the contact, Transactional Emails will disregard the Do Not Contact value. This allows to send Transactional emails as campaign step to Contacts even if they opted out to recieve Marketing emails via standard unsubscribe action and have DNC set as 'no'. Enable transactional email ignoring DNC can be turned on in Email Settings.
- Sends a transaction or marketing Email to the selected Contact. You can send a transactional Email to the Contact multiple times. You can only send a marketing Email to the Contact once across multiple sources. If the Contact has already received this Email from another source or the current Campaign, they aren't sent the Email again and the Contact progresses through the Campaign. Emails can be transactional or marketing. Marketing Emails obey Do Not Contact (DNC) settings of the Contact, Transactional Emails disregard the DNC value. This allows sending Transactional Emails as a Campaign step to Contacts, even if they opted out to receive marketing Emails via a standard unsubscribe action and therefore have DNC set for the Email Channel. Turned on by default in Mautic 5.0, it's possible to override the setting in Email Settings.

Just like we test code PR's in Gitpod, please review your docs edits in Gitpod too! This one broke the RST table layout, and there were several Vale fixes to do after addressing that 😸 .

There should be a Gitpod button to click and you'll see any issues in the 'output' tab.

As a side thought, this is a big wall of text to have in a small area in a table. Maybe it makes more sense to have a dedicated section which explains transactional and marketing emails, and link to it from this with a small description? WDYT @jos0405 ? I think a sub-section of emails.rst under Channels would make the most sense.

@@ -79,6 +79,7 @@ The actions that Mautic offers in a Campaign include:
- Sends a Webhook to a defined URL, using the GET, POST, PUT, PATCH, or DELETE methods. Headers and data is customizable, and support the use of tokens, such as Contact fields and the Contact's IP address. For example, ``{contactfield=firstname}``
* - **Send Email**
- Sends a transaction or marketing Email to the selected Contact. You can send a transactional Email to the Contact multiple times. You can only send a marketing Email to the Contact once across multiple sources. If the Contact has already received this Email from another source or the current Campaign, they aren't sent the Email again and the Contact progresses through the Campaign.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Sends a transaction or marketing Email to the selected Contact. You can send a transactional Email to the Contact multiple times. You can only send a marketing Email to the Contact once across multiple sources. If the Contact has already received this Email from another source or the current Campaign, they aren't sent the Email again and the Contact progresses through the Campaign.

@RCheesley
Copy link
Member

@jos0405 would you be up for refactoring this based on the feedback? I feel it's too much of a wall-of-text to go into a table as it stands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants