Comprehensive UTM tags documentation (backport of #712 to 7.2) - #922
Draft
promptless-for-oss wants to merge 2 commits into
Draft
Comprehensive UTM tags documentation (backport of #712 to 7.2)#922promptless-for-oss wants to merge 2 commits into
promptless-for-oss wants to merge 2 commits into
Conversation
to 7.1) Replicates user-documentation PR mautic#712 onto the 7.1 branch: adds an 8-page UTM Tags section under docs/utm_tags/, removes the old docs/channels/utm_tags.rst, repoints its two inbound :doc: links, adds the UTM Tags toctree caption, and adds CPC/DWC to the Vale vocabulary.
| @@ -0,0 +1,166 @@ | |||
| UTM tags overview | |||
Contributor
Author
There was a problem hiding this comment.
All 8 UTM Tags pages on this branch are a verbatim backport of already-reviewed content from user-documentation PR #712 (base 7.0). Product-behavior claims are inherited from that PR's review; the Mautic app source is not in this docs repo. Objective RST-defect fixes applied during backport: flattened a nested .. note:: in utm_tags_landing_pages.rst, corrected a malformed utm_content literal in utm_tags_segment_filters.rst, and lowercased utm_medium=email inside example-URL code blocks.
Source: #712
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Open in Promptless
Backports the comprehensive UTM tags documentation from user-documentation PR #712 onto the 7.2 branch, at the maintainer's request. It replaces the single thin
docs/channels/utm_tags.rstpage with a dedicated eight-page UTM Tags section underdocs/utm_tags/— an overview plus per-feature guides for Landing Pages, Asset downloads, Forms, Emails, Dynamic Web Content, Campaign conditions, and Segment filters. The two inbound:doc:links (from Focus Items and Dynamic Web Content) are repointed to the new overview, the old page is removed, the UTM Tags toctree caption is added to the docs index, andCPC/DWCare added to the Vale vocabulary.A few objective RST defects present in the source PR (a nested
.. note::, a malformed inline literal, and inconsistent casing inside example-URL code blocks) are corrected in this backport; a placeholder screenshot TODO in the Forms page is carried over as-is.Trigger Events
Synced from #712 code review (2026-08-14)
Applied maintainer @RCheesley's "Apply suggestions from code review" edits from #712 to keep this backport in step: swapped the placeholder example-URL host to
example.comindocs/utm_tags/utm_tags_forms.rstanddocs/utm_tags/utm_tags_landing_pages.rst(three sample URLs total). All three edits were applied verbatim. The third file changed on #712 (utm_tags_segment_filters.rst, an inline-literal typo fix onutm_content) needed no change here — that defect was already corrected in this backport, so it was a no-op.