Hi, I tried the same process as, you and it is working without any problem, are you sure you are not using any custom tracking code? It seems there is some code specific to your environment, which will be getting labels based on URL info table and applying the old labels. meanwhile, can you try
Hi Amit, thank you for sparing time looking into this issue.
I've tried re-open or re-create the delivery but with no luck to solve this problem.
For the issue I mentioned. The un-expected label is generated because the same link is once set in an old delivery template.
E.g. When I set the label of "https://www.abc.com" in delivery "A" as "Test", and then create a delivery "B" to include the same URL several days later. This link's label will automatically generate as "Test" no matter what I set in the HTML of delivery "B".
So, my question is, is there any method to avoid delivery "A" labels continuing taking effect in other new deliveries?
Hi Amit, sorry for the late reply and thank you so much for the answer. I really appreciate it!
I just have a further question on it:
When I trying adding the "_label" attribute to the <a> links. The result doesn't show what I'd like to see in the delivery interface.
Please see the example below:
Though I set the "_label" to be "PreHeader", it still reads "Pre-Header" (with an extra hyphen symbol) in the Adobe delivery interface.
I guess this is a cache problem, but I don't know how to solve it. I don't want the final Label to be "Pre-Header" and need it to be "PreHeader" as what I set in the HTML code.
*I also checked the XML of the delivery and found:
The label I set in the HTML becomes the value of the attribute "guessLabel" (in yellow). However, it is covered by the value of "label" (in pink). But actually, I never set a value "Pre-Header" in my delivery/code.
Do you know why this problem happened and what to do with it?