docs: Add Tags documentation for Contact management#647
docs: Add Tags documentation for Contact management#647promptless-for-oss wants to merge 2 commits into
Conversation
Signed-off-by: promptless-for-oss <promptless-for-oss@users.noreply.github.com>
| @@ -0,0 +1,125 @@ | |||
| .. vale off | |||
There was a problem hiding this comment.
Citation: Referenced Modify Contact's tags action and Contact Tags condition from the Campaign Builder documentation to ensure consistency in describing Tags usage within Campaigns.
View source
| @@ -0,0 +1,125 @@ | |||
| .. vale off | |||
There was a problem hiding this comment.
Citation: Referenced the Modify Contact's Tags Form action documentation to ensure consistency in describing Tags usage within Forms.
View source
adiati98
left a comment
There was a problem hiding this comment.
@promptless-for-oss there are some reviews for you to address.
| Managing Tags | ||
| ************* |
There was a problem hiding this comment.
Let's wrap this in vale off and vale on.
| Managing Tags | |
| ************* | |
| .. vale off | |
| Managing Tags | |
| ************* | |
| .. vale on |
| Creating Tags | ||
| ============= |
There was a problem hiding this comment.
| Creating Tags | |
| ============= | |
| .. vale off | |
| Creating Tags | |
| ============= | |
| .. vale on |
| Adding Tags to Contacts | ||
| ======================= |
There was a problem hiding this comment.
| Adding Tags to Contacts | |
| ======================= | |
| .. vale off | |
| Adding Tags to Contacts | |
| ======================= | |
| .. vale on |
| Using Tags in Campaigns | ||
| *********************** |
There was a problem hiding this comment.
| Using Tags in Campaigns | |
| *********************** | |
| .. vale off | |
| Using Tags in Campaigns | |
| *********************** | |
| .. vale on |
| 4. Select Tags to add or remove. | ||
| 5. Click **Add** to save the action. | ||
|
|
||
| This action is useful for marking Contacts who have reached certain stages, completed specific actions, or require follow-up. |
There was a problem hiding this comment.
| This action is useful for marking Contacts who have reached certain stages, completed specific actions, or require follow-up. | |
| .. vale off | |
| This action is useful for marking Contacts who have reached certain stages, completed specific actions, or require follow-up. | |
| .. vale on |
| - To find Contacts with a specific Tag, use: ``tag:tagname`` | ||
| - To find Contacts without a specific Tag, use: ``!tag:tagname`` |
There was a problem hiding this comment.
We use * for unordered list.
| - To find Contacts with a specific Tag, use: ``tag:tagname`` | |
| - To find Contacts without a specific Tag, use: ``!tag:tagname`` | |
| * To find Contacts with a specific Tag, use ``tag:tagname`` | |
| * To find Contacts without a specific Tag, use ``!tag:tagname`` |
| - **Use consistent naming conventions** - Establish naming rules to avoid duplicates like "Webinar" and "webinar-attendee" for similar purposes. | ||
| - **Document your Tag taxonomy** - Keep a record of what each Tag means and when to use it. | ||
| - **Avoid over-tagging** - Too many Tags can become difficult to manage. Consider whether a Segment or Custom Field might be more appropriate. | ||
| - **Review Tags regularly** - Periodically audit your Tags to remove outdated or unused ones. | ||
| - **Combine with Segments** - Use Tags for quick manual labeling and Segments for dynamic, filter-based grouping. |
There was a problem hiding this comment.
Use single quote for word(s) and double quotes for quotes.
| - **Use consistent naming conventions** - Establish naming rules to avoid duplicates like "Webinar" and "webinar-attendee" for similar purposes. | |
| - **Document your Tag taxonomy** - Keep a record of what each Tag means and when to use it. | |
| - **Avoid over-tagging** - Too many Tags can become difficult to manage. Consider whether a Segment or Custom Field might be more appropriate. | |
| - **Review Tags regularly** - Periodically audit your Tags to remove outdated or unused ones. | |
| - **Combine with Segments** - Use Tags for quick manual labeling and Segments for dynamic, filter-based grouping. | |
| * **Use consistent naming conventions** - Establish naming rules to avoid duplicates, such as 'Webinar' and 'webinar-attendee', for similar purposes. | |
| * **Document your Tag taxonomy** - Keep a record of what each Tag means and when to use it. | |
| * **Avoid over-tagging** - Too many Tags can become difficult to manage. Consider whether a Segment or Custom Field might be more appropriate. | |
| * **Review Tags regularly** - Periodically audit your Tags to remove outdated or unused ones. | |
| * **Combine with Segments** - Use Tags for quick manual labeling and Segments for dynamic, filter-based grouping. |
| - To find Contacts with a specific Tag, use: ``tag:tagname`` | ||
| - To find Contacts without a specific Tag, use: ``!tag:tagname`` | ||
|
|
||
| Replace ``tagname`` with the actual name of the Tag. If the Tag name contains spaces, wrap it in quotes: ``tag:"tag name"`` |
There was a problem hiding this comment.
Let's stay away from : when possible.
| Replace ``tagname`` with the actual name of the Tag. If the Tag name contains spaces, wrap it in quotes: ``tag:"tag name"`` | |
| Replace ``tagname`` with the actual name of the Tag. If the Tag name contains spaces, wrap it in quotes. For example, ``tag:"tag name"``. |
| 1. Navigate to the **Contacts** section. | ||
| 2. Use filters to find the Contacts you want to update. | ||
| 3. Select the checkboxes next to the desired Contacts. | ||
| 4. Click the green arrow at the top of the column. | ||
| 5. Select **Change Tags** from the dropdown menu. | ||
| 6. Choose Tags to add or remove. | ||
| 7. Click **Save**. |
There was a problem hiding this comment.
| 1. Navigate to the **Contacts** section. | |
| 2. Use filters to find the Contacts you want to update. | |
| 3. Select the checkboxes next to the desired Contacts. | |
| 4. Click the green arrow at the top of the column. | |
| 5. Select **Change Tags** from the dropdown menu. | |
| 6. Choose Tags to add or remove. | |
| 7. Click **Save**. | |
| #. Navigate to the **Contacts** section. | |
| #. Use filters to find the Contacts you want to update. | |
| #. Select the checkboxes next to the desired Contacts. | |
| #. Click the green arrow at the top of the column. | |
| #. Select **Change Tags** from the dropdown menu. | |
| #. Choose Tags to add or remove. | |
| #. Click **Save**. |
| 1. Navigate to the Contact's record. | ||
| 2. Click **Edit** to open the Contact edit form. | ||
| 3. In the **Tags** field, start typing to search existing Tags or enter a new Tag name. | ||
| 4. Press Enter or select from the dropdown to apply the Tag. | ||
| 5. Click **Save** to save the changes. |
There was a problem hiding this comment.
The word "form" here is general, not Mautic's feature. So, let's wrap this in vale off/on.
| 1. Navigate to the Contact's record. | |
| 2. Click **Edit** to open the Contact edit form. | |
| 3. In the **Tags** field, start typing to search existing Tags or enter a new Tag name. | |
| 4. Press Enter or select from the dropdown to apply the Tag. | |
| 5. Click **Save** to save the changes. | |
| .. vale off | |
| #. Navigate to the Contact's record. | |
| #. Click **Edit** to open the Contact edit form. | |
| #. In the **Tags** field, start typing to search existing Tags or enter a new Tag name. | |
| #. Press Enter or select from the dropdown to apply the Tag. | |
| #. Click **Save** to save the changes. | |
| .. vale on |
Open this suggestion in Promptless to view citations and reasoning process
Creates comprehensive documentation for Tags in Mautic. The new
tags.rstpage covers creating and managing Tags, adding Tags to Contacts manually and via batch updates, using Tags in Campaigns (Modify Contact's Tags action, Contact Tags condition), using Tags in Forms and Segments, Tag search syntax, and best practices for Tag taxonomy.Trigger Events
Web UI: Can you check if there is any missing documentation
Agent Response
Tip: Set up a GitHub Issues trigger in Projects to enable @Promptless mentions in issues 🐙