KakaoTalk channel push
This article describes how to connect Infobip in AE, create a KakaoTalk Brand Message channel, and complete test sends, production pushes, and result troubleshooting.
Sending window: KakaoTalk messages are sent only between 07:00 (inclusive) and 19:00 (exclusive) Beijing time, which corresponds to 08:00 (inclusive) to 20:00 (exclusive) Korea time. Schedule task trigger times within this window.
1. Overview
The KakaoTalk channel sends Brand Messages through Infobip to Korean users who meet the marketing authorization conditions. The complete flow includes configuring the Infobip authorization, creating and enabling a channel, selecting the target audience, editing and testing the message, sending it in production, and viewing delivery and click results.
The channel supports message preview, test sends, and a system touch funnel. After you turn on the touch funnel, the system automatically records five steps: Scheduled Send, Attempted, Success, Delivered, and Clicked. You don't need to create touch events manually.
2. Prerequisites
Before you start, confirm that the Infobip side and the AE user data are ready, and make sure the current account has permission to view and edit Engage channels.
| Item | Requirement |
|---|---|
| Infobip account | The account has the KakaoTalk Brand Message capability enabled and has sending permissions. |
| Connection information | Prepare a valid HTTPS API Base URL and API Key. The API Key is a sensitive credential; enter it only in the application authorization dialog. |
| KakaoTalk Sender | The Sender has been configured in Infobip and can be used for Brand Message. You need to enter this Sender when creating a channel. |
| Mobile Phone Number Property | A user property for storing Korean mobile phone numbers already exists in AE, and its type is string or number. The actual sending number should be +82 followed by a 10-digit number, for example +821012345678. |
| Marketing authorization | Recipients meet the marketing consent conditions required by your business and can be selected as Channel Friends, Non-channel Friends, or All Marketing-consented Users. |
Kakao and Infobip checks: The KakaoTalk account used to send Brand Messages should complete Business Channel verification. Information such as the channel name and profile picture should match the submitted business information, and the customer center contact information should be completed in KakaoTalk Channel Manager. Also confirm that Infobip is linked to the channel and Sender, and that the API Key includes the required KakaoTalk API permissions and has not expired. The actual configuration is subject to the KakaoTalk and Infobip consoles.
Go to your Infobip dashboard and collect the following information.
API keys and base URL
- In the Infobip portal, select Developer Tools > API Keys.
- On the API keys page, copy the API base URL.
- Select Create API key.
- Enter a name, select an expiration date, and then select the API scopes required for KakaoTalk. These scopes control which Infobip API operations your key can perform.
- Under channel, select KakaoTalk and click Request Sender
3. Configure Infobip application authorization
- Go to Engage > Settings > Channel Settings > Third-party Platform.
- Expand KakaoTalk - Brand Message, and in the Application Authorization area, click Add application.
- Enter the Authorization Name, API Base URL, and API Key.
- Click Save and Connect. After the connection succeeds, the authorization can be used to create KakaoTalk channels.
- Configure the Infobip connection information in the application authorization dialog, as shown below.
| Field | Instructions |
|---|---|
| Authorization Name | Enter a name your team can easily recognize. We recommend including business or environment information. |
| Provider | Fixed as Infobip; no change needed. |
| API Base URL | Copy the API Base URL from the Developer Tools > API Keys page in the Infobip Portal. Enter the complete HTTPS service URL. |
| API Key | Create or copy a key on the Developer Tools > API Keys page in the Infobip Portal. When creating it, set a recognizable name and a reasonable expiration time, and grant the API permissions required for KakaoTalk. When editing an existing authorization, you can keep the original key if you don't replace it. |
- When you save, the system connects to Infobip to verify the credentials.
- The API Key is stored encrypted and is not displayed again on later pages. When editing an existing authorization, leave it blank to keep the original key.
- Authorization names must be unique within the current project.
- If the connection fails, check in order whether the Base URL is a valid HTTPS address, whether the API Key is correct and not expired, whether the account has KakaoTalk permissions, and whether the current network can access Infobip. An authorization that is referenced by a channel can't be deleted directly; handle the associated channels first.
4. Create and enable a KakaoTalk channel
- In the KakaoTalk - Brand Message area, click New Channel.
- Enter the Channel Name, select a connected authorized application, enter the KakaoTalk Sender, and select the Mobile Phone Number Property.
- Turn on Funnel Setting as needed, and then click Create Channel.
- Return to the channel list and enable the channel. When you enable it, the system verifies the authorization, Sender, and mobile phone number property again.
When creating a channel, complete the following configuration, as shown below.
| Field | Instructions |
|---|---|
| Channel Name | A name that identifies the channel within the project. |
| Select authorized application | Select only an Infobip authorization whose status is normal and that has connected successfully. |
| KakaoTalk Sender | Confirm and enter an enabled Sender from Channels and Numbers > Channels > Senders in the Infobip Portal. Within the same project, the same authorization can't use the same Sender to create multiple channels. |
| Mobile Phone Number Property | Select a string or numeric user property that stores Korean mobile phone numbers. |
| Funnel Setting | When turned on, the system automatically records five fixed touch steps. System steps can't be modified. |
You can't modify the configuration of an enabled channel directly. To change the authorization, Sender, mobile phone number property, or touch funnel, disable the channel first, make the changes, and then enable it again.
5. Edit a message and send a test
- In the operation column of the channel list, click Send Test.
- Enter a test phone number and select the Target Audience: Channel Friends, Non-channel Friends, or All Marketing-consented Users.
- Select a message type and fill in the content the page requires, such as the body, images, buttons, products, coupons, or video.
- Check how the message looks in the Message Preview on the right, and click Confirm & Send when everything is correct.
The test send page shows the audience scope, eight message types, the content editing area, and the client preview, as shown below.
About target audience
Target audience is required and declares which types of users Kakao allows you to reach. It doesn't replace target user filtering in AE; recipients must meet both the task's audience conditions and Kakao's audience authorization conditions.
| Target Audience | Reachable users | Recommendation |
|---|---|---|
| Channel Friends | Users who have added the current KakaoTalk channel as a friend and meet Kakao's corresponding authorization conditions. | Default. Suitable for sending only to users who follow the channel. This scope doesn't support the Add Channel button. |
| Non-channel Friends | Users who haven't added the current channel as a friend but have subscribed or agreed to receive marketing messages through Kakao. | Suitable for reaching compliant audiences who don't follow the channel yet; you can use the Add Channel button to encourage them to follow it. |
| All Marketing-consented Users | Covers both eligible channel friends and non-channel friends, that is, the largest reachable scope with the corresponding marketing authorization. | Suitable when compliant coverage is the priority; you can use the Add Channel button. |
Kakao checks at delivery whether recipients match the selected scope; users who don't qualify won't receive the message. Therefore, choose a scope that matches the actual marketing authorization for both test and production sends.
| Message Type | Code | Main content limits | Buttons and other rules |
|---|---|---|---|
| Text Type | FT | Body required; up to 1300 characters and 99 line breaks. | Up to 5 buttons; up to 4 when a coupon is used. Button names up to 14 characters. |
| Image | FI | Image and body required; body up to 1300 characters and 99 line breaks. | Button and coupon limits are the same as Text Type; image links must be HTTP/HTTPS addresses. |
| Wide Image | FW | Image and body required; body up to 76 characters and 5 line breaks. | Up to 2 buttons, button names up to 8 characters; place the Add Channel button last. |
| Item List | FL | Title up to 20 characters with no line breaks; contains 3-4 items. | Up to 2 buttons, button names up to 8 characters; place the Add Channel button last. |
| Carousel Feed | FC | Contains 2-6 content cards; each card must have an image and text. | 1-2 buttons per card; up to 1 coupon and 1 Add Channel button for the whole set. |
| Commerce | FM | Product and image required; product title up to 30 characters; price is an integer from 0 to 99999999. | 1-2 buttons, button names up to 8 characters; place the Add Channel button last. |
| Commerce Carousel | FA | Up to 6 product cards; at least 2 without a header card, or at least 1 with a header card. | 1-2 buttons per card; up to 1 coupon and 1 Add Channel button for the whole set. |
| Advanced Video | FP | Video required, and only tv.kakao.com addresses are supported; body up to 76 characters and 5 line breaks. | Up to 1 button, button name up to 8 characters. |
General rules: Currently, only two types of buttons are supported: URL and Add Channel. URL buttons must have a Mobile Link, and a Desktop Link is optional. Images and links must use accessible HTTP/HTTPS addresses.
The Add Channel button doesn't support the Channel Friends audience, and its position requirements differ by message type. The complete required fields and length limits for each message type are subject to real-time validation on the page. In production tasks, you can insert user properties to dynamically replace content for each recipient.
Image recommendations: Use JPEG or PNG where possible, with a width of at least 500 px, and keep the file size small without affecting clarity. Commonly supported aspect ratios are 2:1, 16:10, 3:2, 4:3, 1:1, and 3:4.
Before publishing, confirm that the URLs are publicly accessible, don't require login, and won't expire, and use a test send to check the final cropping and display.
Enter the test phone number in a format the page accepts. The following three formats are currently supported:
01012345678
010 1234 5678
010-1234-5678
When sending, the system automatically converts the number to the Korean E.164 format, for example +821012345678.
The system reports a successful test only after Infobip returns a final delivery result. If the request has been accepted but no delivery result is received within 30 seconds, the system prompts you to keep waiting or troubleshoot later.
6. Production sending and troubleshooting
When creating an Engage task or flow, select an enabled KakaoTalk channel, set the target users, target audience, and message content, and publish within the allowed sending window. The system replaces dynamic content based on user properties, so different users in the same task may receive different final text.
How results are counted: Infobip accepting a request only means the message has entered the provider's processing; it doesn't mean the user has received it.
After you turn on the touch funnel, you can view results by Scheduled Send, Attempted, Success, Delivered, and Clicked. Delivered is based on the final delivery result returned by Infobip, and Clicked is based on click callbacks.
| Symptom | Troubleshooting |
|---|---|
| Authorization unavailable or connection failed | Check whether the Base URL is a complete HTTPS address, whether the API Key is valid, whether the account has KakaoTalk permissions, and whether the current network can access Infobip. 403 usually means insufficient permissions, and 401 usually means an invalid key. |
| Channel can't be enabled | Confirm that the authorization is connected, the Sender is valid and not reused under the same authorization, and the mobile phone number property is of string or numeric type. |
| Invalid phone number format | Confirm that the final number is +82 followed by 10 digits, for example +821012345678. Remove spaces, hyphens, and other symbols; the first digit after the country code can't be 0. |
| Message not sent at the scheduled time | Confirm that the trigger time is between 07:00 (inclusive) and 19:00 (exclusive) Beijing time. The system checks again before submitting the send, and no request is sent to Infobip outside this window. |
| Content validation failed or rejected | Check the required fields, text length, number of images or cards, button order, and links according to the page prompts. Currently, only URL and Add Channel buttons are supported; URL buttons must have a mobile link. |
| Request accepted but test not successful | A test send succeeds only when a final delivery result is received. The system waits up to 30 seconds; if the status is still processing, check the number status, content review, account quota, and service status in Infobip. |
| Delivery failed | Check the rejection, undeliverable, or expiration reason returned by Infobip, focusing on the target audience, marketing authorization, Sender, number status, and message content. |
| Service throttling or temporary error | Resend later. The system doesn't automatically retry Infobip send requests; if failures persist, contact the platform admin or Infobip support with the returned information. |
Pre-publish checklist: Confirm that the channel is enabled, the target users meet the marketing authorization, the mobile phone number property is available, the message preview is correct, the links are accessible, and the trigger time is within the allowed sending window.