Aampe can ingest several types of data, including user events, interaction data, metadata, user properties/attributes, content data from a CMS, recommender system output, and RSS-like feeds.

At minimum, Aampe needs either:
- Notification received and notification opened events
- Bottom of funnel events such as add to cart, start checkout or order completed
Either group of events will allow the Aampe personalization engine to optimize your push notifications.

Aampe principally needs funnel events. The most common examples are: item viewed, add to cart, start checkout and order completed events. That being said, every app is unique and your user journey might include more steps. You should include those as well.

No. The Aampe algorithm can optimize for funnel events, regardless of whether the user tapped on the notification itself. Having notification-specific events allows to ensure that notifications are actually being delivered and not dropped during transport.

Of course. Our algorithms preprocess, cleanup and cluster your event data. So definitely feel free to share all the events you collect, and we will take it from there.

It's easiest to explain with a few examples:
- For add to cart events, it's useful to add the item reference (SKU), price, currency, and discount
- For start checkout and order completed events, it's useful to add the list of items, total price, currency, and discount
- For page view events, it's useful to include the page name, brand name, game name, or restaurant name where applicable

No. We want to make your life as simple as possible. Our data engineers will take anything you share and transform it into the Aampe data model.

The Aampe agents use historical data to create user-level event embeddings for cold-start situations to determine what worked for similar users, but also to train content recommendation models, if you chose to use the ones that Aampe provides.

In its default mode, Aampe triggers messages on your behalf using your push provider API. If you use FCM, Aampe will call the FCM API whenever it needs to trigger a message to one of your users. The same goes for Braze, OneSignal, MoEngage, CleverTap, APNs and all the providers Aampe is integrated with.

That being said, Aampe also provides a Copy via API mode.

Aampe's "Composer" tool is designed for message creation and management. It allows operators to maintain a rich label catalog and create thousands of labeled message alternates so agents are empowered to learn user preferences. The Aampe Composer allows message creation for all standard channels (for example: Email, Push, SMS, WhatsApp, etc.) along with custom surfaces where you will be at liberty to define a template (for example: in-app messages, app-native banners, etc).

The Aampe agents achieve user-level personalization by triggering messages based on user behavior and interactions within customer-defined guardrails.

Aampe allows you to define action-based triggers to control message delivery. The agents consider all the action-triggered messages along with the ever-green messages and proceed to make a decision about the best message to send for each and every user among them.

Aampe integrates with Braze via API. Aampe agents action Braze via API (for example, to send a push notification or an email). Feedback from Braze (for example, push open events) can be ingested using a Braze Current, via Segment or from a data warehouse (if events are forwarded there).

Aampe is a Segment destination, which means a no-code integration that only takes a few minutes. If needed, the Segment integration can be complemented with a direct warehouse connection or API pull (for data not available in Segment, such as internal recommender system output or catalog data).