AdobeDocs / AdobeDocs/experience-cloud.en

Branding documentation for V8 does not distinguish between MKT and RT Instances

Open
#9 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
1
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Issue in ./help/campaign/branding/branding-assign.md and https://experienceleague.adobe.com/en/docs/experience-cloud/campaign/branding/branding-configure

When configuring and using Branding it is very important that the brand selected is available for the Instance the delivery will be sent from. As sub-domains are not shared between MKT/MID and RT servers the same Brand setup cannot be used for a delivery being sent from the MKT as one being sent from the RT.

There should be indication in the documentation to indicate where the brand is to be used (Batch/MKT or Transactional/RT) as well as to make it clear when assigning a Brand to the template or delivery to select the correct brand for the instance.

It would be even better if the product was enhanced to not allow MKT Brands to be added to RT Templates and RT Brands to be added to MKT Templates or Deliveries. A check as well that the sub-domain was fully configured, included in the authorized sending mask for the instance would also be very helpful to avoid sending errors when the Template is attempted to be used.

Thanks,
Michael

Contributor guide

Open the contributing guide

Research direction

Start with ./help/campaign/branding/branding-assign.md and the linked branding-configure page, focusing on the sections covering brand assignment to templates and deliveries. The documentation work is done when it clearly distinguishes Batch/MKT from Transactional/RT brands and explains how to select the brand for the delivery instance; treat the requested product validation separately.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.