11/27/2023 0 Comments Io domainBy using a subdomain for authentication, we can ensure that: In order to verify and authenticate your domain for sending in Customer.io, you will place our required DNS records in your account-specific subdomain (like: cio#. and krs._domainkey.cio#.) rather than the root domain.īecause our authentication records are stored in a subdomain, there won’t be any conflict with your existing email configurations that are already setup in your DNS host. How about Universal Links? If you need to enable them for your mobile app, HTTPS domain authentication is required as well. In addition to improving email deliverability, authenticating your sending domains in Customer.io will also let you control the appearance of your tracked links. Check out our post on Email Deliverability to know more about how it works. Although it’s just one piece of the deliverability puzzle (along with your copy and overall reputation), authenticating the domains you use for sending email from Customer.io will help your messages reach your users. Why we require domain authenticationĬreating great copy means nothing if your messages don’t make it to the People you’re trying to reach. You will need to add certain records to your DNS provider to allow Customer.io to send emails using your domain. Use Google Forms or Jotforms with Zapier.Getting conclusive results from A/B tests.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |