Suggestions
Chris Kelly
Growth & Product Consultant
Chris Kelly is a highly skilled marketing and communications professional with a diverse educational background in English language and literature. He has worked with numerous organizations in different capacities over the years, including Growth PM consultant at LandTrust, Growth Product Manager at Hipcamp, and Head of Content Marketing at Terminal.
Chris has a proven track record in problem-solving, project management, digital marketing, CRM management, lifecycle marketing, retention, email campaigns, and content strategy. He also has experience in managing diverse teams and driving successful outcomes.
Chris received his Bachelor of Arts degree in English from Santa Clara University and participated in study abroad programs in Seattle University and the Institute for the International Education of Students. Chris is a hardworking, happy, and purposeful individual who is focused on achieving his professional and personal goals.
Highlights
This post is like Christmas morning. When great growth minds validate the things you feel but don't say: https://lnkd.in/gcp6vYyv #growth
Let's face it - sometimes our data fails us when we're trying to personalize bulk customer communications. We fall flat on our faces in front of the customer, and it's embarrassing. Here's an example from a clothing brand (that I don't consult for):
Subject Line: It's a scorcher out there! (based on my location) Subcopy: When we think July weather, we think about these items... Content: a grid of 12 items containing Long sleeve shirts, sweaters, jeans! (based on the season)
90% of the time this kind of error is due to how we're structuring data outside of the marketing automation tool, typically in a data warehouse. In this case, it could have been that a seasonal property was set to "Summer22" instead of "Fall22" for each item used within the email, (which pulls in items dynamically based on rules the marketer defines). Whether you're using a Shopify integration into an ESP like Klaviyo, a Reverse ETL into Braze, or implementing a direct API into Iterable's awesome Catalog feature, the key is to have a decent understanding of how this data is created, stored, and sent to your marketing automation tool. For better or worse, it's up to the power users of the tool to understand this process in order to pinpoint how to fix issues when they arise. You can't expect your engineering team to diagnose the problem. You sent the email. You create the game plan for how to make sure it doesn't happen again - even if it was entirely not your fault
