The Nylas blog

The hidden costs of building your own communications features

Discover how product teams can save resources, deploy integrations faster, and improve UX by investing in communications solutions.

5 reasons why you should invest in scheduling features

Want to save users eight hours or more per week, reduce context switching, and maximize retention? Learn how with this infographic on why you should invest in powerful scheduling features.

Hang with Spang February 2022

In our latest Hang with Spang webinar session, Ash and Spang discussed the much anticipated…

Combat Rising Customer Acquisition Costs with Email Data

As e-commerce continues to experience exponential growth, learn how to curb customer acquisition costs and use email data to drive higher lifetime value from your customers.

How Email Parsing Software Builds a Stickier E-Commerce CX

Learn how to create more engaging customer experiences across your purchasing flywheel by using email inbox parsing software to extract context-rich data.

Launch Communications Features Faster (While Improving Efficiency) With Pre-Built Solutions

Building communications features in-house can restrict your resources and slow your go-to-market. Choose pre-built solutions to improve velocity and efficiency.

Three Ways You Can Maximize Gross Merchandise Value (GMV) With Communications Data

See how e-commerce services companies can tap into context-rich communications data to supercharge their purchasing funnel and maximize gross merchandise value.

How To Drive Repurchases With Personalized E-Commerce Experiences

Learn how e-commerce services can leverage personalization across their purchasing funnel to drive repurchases, retention, and maximize gross merchandise value.

How E-Commerce Services Boost Engagement With Universal Package Visibility

Learn how e-commerce services can create more engaging user experiences that drive engagement with universal package visibility.

Nylas’ Response to the Log4j Vulnerability

At Nylas, our information security team took action to investigate the Log4j vulnerability and found that our codebases were not impacted. As the incident unfolds, see how Nylas responded to identify the impact and protect customer data.