Why a larger, more diverse message inventory leads to more effective messaging

At Aampe, we talk a lot about aligning your app content with your message content, and then aligning your message content with your users preferences, but we always start that talk in the same way: “write a whole bunch of messages.” This isn’t intuitive to many of our customers. They’re used to what we call […]

Structure app inventory for message-led personalization

We’ve written a lot about how important timing is in sending push notifications (see here and here, for example), and we’ve also written about how you can get smart about what copy you write, but one theme we haven’t touched on (until now!) is the actual focus or topic of the message. Every app is […]

Do truncated product names from your CMS hurt your push notification open rates?

“Check out the new SWISSGEAR Scan Smart TSA Lapto…”‍ Most consumer retail apps send a lot of generic notifications like this: ‍ …and one reason they do is because the product names and descriptions stored in their CMS are super long and clunky. For example, here are two relatively random items in the Walmart app […]

Crunching clickstream data into ML features at scale

Context Aampe ingests structured clickstream data on the order of hundreds of million rows on a daily basis. Because we believe in making the lives of our customers as easy as possible, we allow them to share this data with Aampe in the format of their preference (as long as it contains 3 main data […]