# Step 3. Showing a Coupon In-App Message to Returning Users
### How to keep returning customers from leaving again
Did churned users re-enter your service after receiving a Push Message?
The cost of acquiring new customers is far higher than the cost of retaining existing ones, and reactivating churned users is an efficient way to reduce marketing costs. Don't lose users who have come back — deliver additional messages with other benefits or information to activate them and improve conversion rates across other services!
#### Use the scenario below to display In-App Messages and boost conversion rates
> 1. We sent a Push Message to users who abandoned their cart,
> 2. Those users tapped the push and entered the service,
> 3. We want to improve purchase conversion by issuing a coupon.
> 4. At this point, we want to run an [A/B (MAB) Test](/en/ab-test/mab-test/create-mab-test.md) on coupon-issuing In-App Messages to find out which message is most effective.
#### Maximize the effect with the best-performing creative!
If you're curious which copy works best, you can find out through In-App Message A/B Testing.
{% content-ref url="/pages/QavFDadjFOjP7S9ee7mO" %}
[In-App Message A/B Test](/en/crm-marketing/in-app-message-guide/in-app-message-ab-test.md)
{% endcontent-ref %}
{% stepper %}
{% step %}
**Prepare the creatives to test.**
If you don't have design resources, you can use the In-App Message image templates provided by Hackle.
{% hint style="info" %}
If you don't have time to prepare multiple creatives, try simply changing the button text to gauge user reactions!
{% endhint %}
{% content-ref url="/pages/Zwj4VwIZ3lufjhwbQmU3" %}
[In-App Message Image Template](/en/crm-marketing/in-app-message-guide/create-campaign/in-app-message-template.md)
{% endcontent-ref %}
{% endstep %}
{% step %}
**Create the In-App Message.**
Click the **+** button to set up the creatives to test.\
For details on experiment configuration, refer to the Docs below!
We will display the following three copies to users who re-entered via the push, and identify which message performs better.
* Group A: Emphasize urgency
* Group B: Emphasize benefits
* Group C: Personalized approach
{% endstep %}
{% step %}
**Configure the screen and audience for the In-App Message.**
* In the exposure settings, select the event where the In-App Message should be displayed.
* Display the `view_home` In-App Message when users who entered via push reach the home screen.
* In the audience settings, select the users to show the In-App Message to. Register the Cohort created in [Hackle Tip - Finding Churned Users](https://dash.readme.com/project/hackle/v4.1.0/docs/%EC%9D%B4%ED%83%88-%EC%82%AC%EC%9A%A9%EC%9E%90-%EC%B0%BE%EC%95%84%EB%B3%B4%EA%B8%B0).
{% hint style="info" %}
It is better if the link set in the touch action of the Push Message matches the screen where the In-App Message is displayed.
If you want to test how it looks to actual customers, enter the desired identifier value in a Test Device.
{% endhint %}
{% endstep %}
{% step %}
**Start the campaign.**
Check the In-App Message performance. End the test with the highest-converting creative to display the message that gets the best response.
{% content-ref url="/pages/bmCCnHcuguH1tWBUkgoz" %}
[Measure In-App Message Campaign Performance](/en/crm-marketing/in-app-message-guide/analyze-in-app-message.md)
{% endcontent-ref %}
{% endstep %}
{% endstepper %}
Once you've run CRM Marketing tailored to your situation, it's time to analyze your users and identify the next Action Items!
---
# Agent Instructions: 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/use-cases/bounced-users-in-app-message.md?ask=
```
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.