> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/crm-marketing/push-message-guide/recommended-templates/personalized-message-template.md).

# Personalized Message Campaign Template Based on Customer Interests

If you're unsure about which campaign to run and how to set it up, refer to this template document.

We recommend cohorts for setting campaign targets by target and purpose, along with appropriate send types for each message. Replace the event keys with those used in your actual workspace.

## Campaign to Improve Purchase Conversion Using Interest Product Information

![](/files/yaNX6uBxcVzxKr0ot4mb)

#### Target & Purpose

The goal is to use information about products/brands that customers have shown interest in to improve purchase conversion rates and encourage their purchasing decisions.

#### Content

Send personalized messages with news alerts about promotions including products the customer expressed interest in, as well as exclusive coupons for those products. Through personalized messages, you can achieve click-through rates more than 5 times higher than regular push messages.

#### Message Examples

| Title                                       | Content                                                                                        |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| 5% off new arrivals from \[Brand] you saved | 👉 A chance to buy \[Brand]'s new products at a discounted price!                              |
| 💌 Discount news has arrived                | Meet \[Product] from your cart at a 15% reduced price                                          |
| 🔔 \[Category] promotion ends tomorrow      | The \[Category] promotion you frequently shop is ending tomorrow. Click now for up to 60% off. |

#### Message Content

* **Personalized message example**: User properties, API properties
  * **Required properties**: name (user name), brand\_name (brand name), product\_name (product name)

> **TIP**\
> To use API properties, you must configure \[API-based] send in the send settings. When calling the API for personalized messages, make sure the properties used in the personalized message are included.

![](/files/xWRKwOE11I9n5Xd6cMTv)

#### Cohort

* **Cohort setup example**: Event type cohort
  * **Required events**: add\_to\_favorite (add to favorites), view\_item (visit specific product detail page)

![](/files/cbu2ScUhSYl5JtrVxODN)

#### Send Settings

Send messages timed to when the brand's discount promotion starts.

* Send type: API-based [👉 Learn more about API-based send](https://docs.hackle.io/en/crm-marketing/push-message-guide/recommended-templates/pages/jijFoP1pGiiQp2cBF8S9#1-3-api-기반-발송)
  * Write your code based on the sample code. You need to insert the campaign key and Hackle API key.
  * If you added API properties to the personalized message, make sure to include apiProperties in the code.
  * The message is sent when the API is triggered.

![](/files/AAkzBOuANgl2MLPsr2CL)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hackle.io/en/crm-marketing/push-message-guide/recommended-templates/personalized-message-template.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.