I have a high priority situation wherein i need some help from you guys-
I have a script which pulls in subject line dynamically and in the delivery subject field (let's say the script is <%=subjectline%>) but when i look into the delivery/emailHeaderParameters/@subject it shows me exact script instead of the actual subject line which went to a recipient.
Is there a way to convert it into an actual subject line in the broadlog subject field?
@Sukrity_Wadhwa - Please suggest.
Hi @akashaj7696 - You don't mention the context for this or why you need this. Generally speaking, you cant accurately reconstruct the subject line from the template at a later date as you don't know if the data that was used in the targeting for the delivery is still current. If the underlying target data changes, so does the dynamic subject line script.
If you store the data attributes used in the subject in the broadLog at the time of the delivery, you could do this accurately as well.
Hi @akashaj7696 - you can compute the subject during the workflow and create a workflow attribute to store the subject. Then in the delivery you just put the variable that you computed earlier. This way you can extend the broadLog schema and store the subject so you can find it again in the broadLog. Once common way to see what the email subject you sent was is to use the same text in the HTML <title> or in some preview header text. That way you can pull up the MirrorPageUrl and look at the title in the window - that would then show you the email subject. Cheers
Hi @akashaj7696 - I'm not sure what you mean by "try something inside the delivery"? @wodnicki has given you a response above on how to store the computed subject in the BroadLog. Unfortunately this is the only way to retrieve it after the delivery have been sent. Does this help you get what you need? Cheers
Follow these steps:
NB this can get expensive storage-wise so be mindful of database sizing and lower retention/increase disk space as appropriate.
Hi @akashaj7696 - a subject that is unique to a recipient can't be stored under the definition for a delivery, because the delivery object doesnt contain all the data per recipient.
If you need to see the subject before you send the delivery you can enrich the subject using a formula onto the temporary schema in the workflow. If you need to see the subject after you send the delivery then you can add it to the broadLog as @wodnicki has described below. Cheers Darren