BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
marcreych
Calcite | Level 5

Hi there.

We are about to advertise a service that is called "Pick@Home". Given our bulk email task, we would like to show the product name as the sender name in the email header.

What we did: In the "Header"-tab we tried two things:

  • Inserting a merge tag in the "Display as" field, where we use the product name depending on the language. This makes sense only, if we add some other words that are indeed language specific. (See screenshot)
    marcreych_0-1713529948278.png

     

  • Inserting the string "Pick@home" plainly in the "Display as" field.

When testing (Tab "Review" and sending a test email with "Responsive previews"), SAS CI360 shows an error message:

marcreych_2-1713530205955.png

 

 

When we change the "Display as" to only "PickHome", then the testing works flawlessly.

 

This raises the questions:

  • Which special characters are allowed in the "Display as" field?
  • Which special characters are allowed in merge tags in general?
  • Is there any way to escape special characters in order to be able to use them?

So far I have found nothing in the official SAS CI360 user documentation.

Thanks for your help!

1 ACCEPTED SOLUTION

Accepted Solutions
PeterAns
SAS Employee

yes, right now we can not get the @ symbol to work in the From name, that is what is causing the error.   I can speak to our team about it, but for now, while not ideal, I'd recommend using "at".  

 

Peter

View solution in original post

3 REPLIES 3
PeterAns
SAS Employee

Thank you for your question.   If you were to use "Pick at home" instead of "pick@home" do you get the error message?

 

That error usually means their is somethign with your from address or send agent, where this issue is your from name.  

marcreych
Calcite | Level 5

Hi Peter. Thanks for your suggestion. Indeed, the error occurs only, when "@" or some other special characters are used. Could this be due to some standards that prohibit those characters from being used as "from"-data in e-mails? This would mean, SAS CI360 behaves according to those standards. Otherwise it would be nice, if those restrictions are either lifted or documented in the user documentation.

PeterAns
SAS Employee

yes, right now we can not get the @ symbol to work in the From name, that is what is causing the error.   I can speak to our team about it, but for now, while not ideal, I'd recommend using "at".  

 

Peter

Review SAS CI360 now.png

 

Want to review SAS CI360? G2 is offering a gift card or charitable donation for each accepted review. Use this link to opt out of receiving anything of value for your review.

 

 

 

 

SAS Customer Intelligence 360

Get started with CI 360

Review CI 360 Release Notes

Open a Technical Support case

Suggest software enhancements

Listen to the Reimagine Marketing podcast

Assess your marketing efforts with a free tool

 

Training Resources

SAS Customer Intelligence Learning Subscription (login required)

Access free tutorials

Refer to documentation

Latest hot fixes

Compatibility notice re: SAS 9.4M8 (TS1M8) or later

 

 

How to improve email deliverability

SAS' Peter Ansbacher shows you how to use the dashboard in SAS Customer Intelligence 360 for better results.

Find more tutorials on the SAS Users YouTube channel.

Review SAS CI360 now.png

 

Want to review SAS CI360? G2 is offering a gift card or charitable donation for each accepted review. Use this link to opt out of receiving anything of value for your review.

 

 

 

 

SAS Customer Intelligence 360

Get started with CI 360

Review CI 360 Release Notes

Open a Technical Support case

Suggest software enhancements

Listen to the Reimagine Marketing podcast

Assess your marketing efforts with a free tool

 

Training Resources

SAS Customer Intelligence Learning Subscription (login required)

Access free tutorials

Refer to documentation

Latest hot fixes

Compatibility notice re: SAS 9.4M8 (TS1M8) or later

 

 

Discussion stats
  • 3 replies
  • 1716 views
  • 0 likes
  • 2 in conversation