Skip to content

Commit

Permalink
Excluding segments from segment emails
Browse files Browse the repository at this point in the history
  • Loading branch information
@fedys
fedys committed Apr 16, 2024
1 parent a38ad61 commit 2b5981f
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion docs/channels/emails.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,15 @@ Segment Emails are marketing Emails by default. On creation the marketer assigns

This entry field is a multi-select which allows you to choose several Segments if necessary.

Excluding segments

Check warning on line 42 in docs/channels/emails.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Segments' instead of 'segments'.

Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Segments' instead of 'segments'.", "location": {"path": "docs/channels/emails.rst", "range": {"start": {"line": 42, "column": 11}}}, "severity": "INFO"}
==================

There is a multi-select field that allows excluding contacts belonging given segments.

Check warning on line 45 in docs/channels/emails.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Contacts' instead of 'contacts'.

Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Contacts' instead of 'contacts'.", "location": {"path": "docs/channels/emails.rst", "range": {"start": {"line": 45, "column": 53}}}, "severity": "INFO"}

Check warning on line 45 in docs/channels/emails.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Segments' instead of 'segments'.

Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Segments' instead of 'segments'.", "location": {"path": "docs/channels/emails.rst", "range": {"start": {"line": 45, "column": 78}}}, "severity": "INFO"}

.. image:: images/emails/email-excluding-segments.png
:width: 400
:alt: Screenshot showing selecting Segments that should be excluded

Check warning on line 49 in docs/channels/emails.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('be excluded').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('be excluded').", "location": {"path": "docs/channels/emails.rst", "range": {"start": {"line": 49, "column": 59}}}, "severity": "INFO"}

Mautic initiates the sending of these Emails with a :doc:`/configuration/cron_jobs` - see section on Send Scheduled Broadcasts - for example, Segment Emails - for more details on this.

Email formats
Expand Down Expand Up @@ -370,4 +379,3 @@ This is because Mautic sends test Emails to a Mautic User and not to a Mautic Co
Mautic Users can't unsubscribe and therefore the unsubscribe link looks like this: ``https://mautic.example.com/|URL|``. However, the link **does** work correctly when you send the Email to a Contact.

Best practice is to create a Segment with a small number of Contacts to receive test Emails - for example, yourself - which ensures that you can fully test features such as unsubscribe behaviour.

Binary file added docs/channels/images/emails/email-excluding-segments.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 2b5981f

Please sign in to comment.