Send test message
Test push messages
Growth actions > Push Message > Select +Create Push Message in the upper right corner >
You
can
select it in the what section.
When creating a push message, choose an audience type.
At this time
, the method of executing the test message will be determined depending on the selected audience type.
-
Audience Type
- Device: Select test device / Enter test target
- User: Select test user / enter test target (search user ID, enter directly)
Push message > Audience type: Device
Sending a test message is possible in the When section at the end of the push setup step.
If the audience type is Device , the only channel that can create a push message campaign is the App/Web channel.
따라서 선택 및 시에는 기등록한 를 선택하거나
You can send a test message by directly entering the identification value for each platform.
1.Select test device
You can select up to 5 pre-registered test devices in
the Growth Action > Settings > Test Message Setting tab
.
>> Learn how to register a test device
>> 등록방법 알아보기
Please check and test your platform and language selection before sending a message.
2. Test target input
If you cannot register the test device in advance, you can test it by directly entering the identification value.
If the test is successful, you can save the test device with its identification.
If successful, click the [Save this device] button in the toast alarm. Just enter the device name and a test device will be created.
Push message > Audience type: User
Sending a test message is possible in the When section at the end of the push setup step.
If the audience type is User , you can create a push message campaign on any channel.
테스트 방식은 크게 기존에 등록했던 를 선택하거나, 테스트 대상을 입력하는 방식으로 나뉩니다.
방식은 다시 2가지로 나뉩니다.
- If you know the user ID, you can search for that ID and select it.
- If you know the identification value, Kakao ID, and number, you can perform a test by entering the values directly.
1.Select test user
You can select up to 5 pre-registered users in the Growth Action > Settings > Test Message Setting tab.
>> How to register as a test user
유저의 선택 시 테스트 가한 유저를 확인할 수 있습니다.
Check whether test messages can be sent based on the inquiry date.
[[Quote:Warning:Medium]]
Note
목록에서 '테스트 가'이었으나 조회 후 해당 의 기기가 확인되지 않는 경우,
Please click the refresh button.
2. Test target input
When the audience type is User, there is a difference from when the audience type is Device.
First, even if the test is successful by entering the identification value, the test user cannot be saved with that identification value. Similarly, even if the test is successful by entering a number or Kakao ID, it is not possible to save that number or Kakao ID as a test user.
Since test users can only be saved by searching the user ID, the test user can be saved with that user ID only when the user ID is searched.
2-1. User ID inquiry
App/Web Channel
If you look up the ID collected using abx:user_id, you can check which devices have completed push token integration among the devices logged in with that ID.
At this time, logged in devices are searched based on the platform selected for sending messages (Android, iOS, Web). For example, if a specific ID is logged in to the iOS platform but not to the Android platform, when you select the Android platform and look up that ID, the result will be displayed that there is no device connected.
After checking the ID, a list of devices for which push token integration has been completed appears in the device details, and you can select up to 5 devices to send a message.
[[Quote:Warning:Medium]]
Devices exposed in device details are only those for which push token integration has been completed.
🧐 Why can I only select devices that have completed push token integration?
Kakao and SMS Channel
Unlike App/Web channels, Kakao and SMS channels have a 1:1 matching Kakao ID and number for each user ID, so there is no need to select a device after looking up the ID. Therefore, by looking up the ID, you can only check whether testing is possible or not.
In this case, the criteria for possible/impossible are as follows.
- Kakao: Whether you have a mobile phone number or Kakao ID
[[Quote:Warning:Medium]]
Precautions
For Kakao channels, messages are sent to your mobile phone number or Kakao ID.
When sending an actual message successfully, it is not possible to determine whether the success was due to the number or Kakao ID.
- SMS: presence of mobile phone number
When searching for a user ID, you can save the test user with the searched ID by clicking the [+Save Test User] button in the search results.
2-2. Direct input
Depending on the selected channel, you can send a message by directly entering the identification value, Kakao ID, and number. However, in the case of the User type, even if the test is successful when entered directly, the test device and test user cannot be saved with the corresponding identification value, Kakao ID, or number.
App/Web Channel
In the case of App/Web channels, testing can be performed by directly entering the identification value for each platform, the same as when the audience type is Device.
>> Go to information on identification values for each platform
Kakao and SMS Channel
Kakao can be tested by directly entering the Kakao ID or number, and SMS can be tested by directly entering the number.
How to respond when push message test results fail
If a push message fails, we will guide you on how to respond according to the error code.
Error when using App/Web channel
| Error code | error message | explanation | solution | |
| 40001 | MessageTooBig | FCM/ Message Length Error | Please check the message length limit and try again. | |
| 40002 | MismatchSenderId | Occurs when the Sender ID of the FCM / app and the Sender ID of the app registered on the FCM server do not match. | Please check the apps Sender ID in FCM settings and update it to match the Sender ID of the app that sent the message. | |
| 40003 | NotRegistered | FCM | / If the device token is disabled in the topic. Mainly occurs when app is deleted | The device has been deleted or the token is invalid. Please reinstall the app and try again. |
| 40004 |
Canonical RegistrationId |
FCM / Occurs when there are multiple registration IDs on the same device, and usually recommends updating registration IDs that are no longer in use. | Please update your client apps to use the new registration ID and keep your registration ID up to date. | |
| 40005 | InvalidRegistration | Occurs when trying to send a message to a device that is not registered with FCM/ FCM | Please make sure you are registered with FCM before sending a message. Unregistered devices may receive messages after registration | |
| 40006 | Unavailable | FCM / Error that occurs when FCM service is temporarily unavailable | In case of a temporary service outage, please try again later. | |
| 40041 | InvalidTopicException | APNS / Not allowed to push this topic. Occurs when the bundle_id registered in DFN and the bundle_id of the topic do not match. | Please try after checking whether the bundle_id registered in DFN matches the bundle_id registered in APNS or when building the app. | |
| 40042 | BadDeviceToken | APNS / The token specified in the request is invalid. Mainly occurs when the authentication environment changes | You need to verify that the token is valid and that it matches the environment. (Tokens issued from apps built in the development environment cannot be processed by the production APNS server.) | |
| 40043 | BadCertificate | APNS / Occurs when the APNS certificate is invalid or the certificate is set incorrectly. | Generate the correct certificate and apply it to your server. You will need to reset your certificate and check your APNS settings again | |
| 40044 | InvalidProviderToken | APNS / Occurs when APNS fails to process a push due to an invalid device token or authentication issue. | Be sure to use the correct device token and resolve any authentication issues. Please check your certificate or authentication information again. | |
| 40045 | ExpiredProviderToken | If the APNS/ device token has expired. | The push token has expired. Please try after re-issuing the token. | |
| 40081 | PayloadTooLarge | Occurs when the payload of a web /push message exceeds the size limit. | Use smaller payloads or optimize them to contain the minimum amount of information needed. (Inquire about maximum size limit) | |
| 40082 | TooManyRequest | Web / This can happen if too many push requests are sent in a short period of time. | Please check your campaign settings to avoid sending too many push requests to one device (cookie). | |
| 40083 | ExpiredSubscription | Web / Occurs when your subscription has expired or is no longer valid | Check for expired subscriptions, renew or delete expired subscriptions. | |
| 50001 | UnHandledException | unexpected error | If the problem occurs even after retrying, please contact customer service. |
Error when using Kakao channel
| Error code | error message | explanation | solution |
| 40001 |
InvalidSenderKey Exception |
Sending profile key is invalid | Please check the status of the outgoing profile set. |
| 40002 | TalkUserIdNotFonud | Invalid app user ID request | Please check the user ID of the Kakao app before trying. |
| 40003 |
Invalid UserKeyException |
Invalid user key request | Please check the registered phone number and app user ID again. |
| 40004 |
FailedToSendMessage ByNoFriendship Exception |
Failed to send friend chat because channel was not added | Please add the channel and try again. |
| 40005 |
InvalidPhone NumberException |
Phone number error | This is an invalid phone number. Please check again. |
| 40006 |
MessageLength OverLimitException |
message length error | Please check the message length limit and try again. |
| 40007 |
TemplateNot FoundException |
Template not found | Notification Talk template could not be found. It may have been stopped or deleted, so please check Growth Action > Assets > Notification Talk Template. |
| 40008 |
NoSendAvailable Exception |
Message could not be sent | If you are a user of a version that is subject to discontinuation of support, or if there is a problem with your carriers network or terminal at the time.Please try again. |
| 40009 |
NoMatched TemplateException |
Message content does not match template | Please check the template and message content and try again. |
| 40011 |
NoSendAvailable
|
Not available time to send message
(Friend Talk/Marketing messages can be sent from 08:00 to 20:50) |
Please try when delivery is available. |
| 50001 | UnHandledException | unexpected error | If the problem occurs even after retrying, please contact customer service. |
Error when using SMS channel
[[Quote:Warning:Small]]
Precautions when testing SMS
SMS can only confirm whether a message has been sent. If the message is not displayed after successful delivery, please refer to the error situation below and perform the test again.
| Error code | error message | solution |
| 40000 | BadRequest | Please contact us through customer service. |
Internal validation error
| Error code | error message | explanation | solution |
| 40001 |
PushToken NotFoundException |
Push token not received | Please check whether the push token is connected properly. If not, please delete the app, reinstall it, and run it again. |
| 40002 |
InvalidPushToken Exception |
Badly formatted push token | Please check whether the push token is connected properly. If not, please delete the app, reinstall it, and run it again. |
| 40003 |
InvalidWebLinkUrl Exception |
Incorrectly formatted web link URL (web push) | Please recheck the web link URL linked to the web push settings. |
| 40004 |
DisabledPush NotificationException |
Agree to receive push Off | The push reception consent setting is set to Off. Please check the reception consent settings on your device. |
| 40005 | InvalidOSException | Unrecognized OS (Supported OS: Android, IOS, Web, Etc) | Please check whether the target device platform is Android, IOS, or web environment before trying. |
| 40006 |
AvailableChannels lNotFoundException |
Notification channel setting issue | There is an error in the push settings related to the target devices platform.Please check the environment settings for each platform in Growth Action > Settings. |
| 40007 |
DeviceProfile NotFoundException |
When ad tracking is restricted or SDK is not integrated |
1.Please make sure Limit Ad Tracking is turned on.
2. This device is not registered in DFINERY.Please check SDK integration. |
| 40008 | InvalidDeviceFormat | Invalid device format | Please check the device format again. |
| 40009 |
NotSupported DevicePlatform |
If the test devices platform does not exist on the campaign target platform | Please select a test device included in the campaign target platform. |
| 40010 |
AbortMessage Exception |
When aborted in personalized message grammar | Interrupted by personalized message grammar. Please check the personalized grammar to see if it is an intended abort. |
| 50001 |
UnHandled Exception |
unexpected error |
If the problem occurs even after retrying, please contact customer service. |
Test pop-up messages
When creating a pop-up message, you can select an audience type like a push message. Options include Device, User, or the entire audience including both types. notionvc: 6f571fd0-e472-49d8-977b-e33279ba5f57 notionvc: 6f571fd0-e472-49d8-977b-e33279ba5f57
Pop-up message test
- When audience type is Device: Only test devices can be selected
- When the audience type is User: Only test users can be selected
- When selecting all audience types: You can select either test device or test user type.
[[Quote:Warning:Moderate]] Unlike push messages, pop-up messages are not subject to testability, but rather expose your campaign to all connected devices. You can check device information connected to that user in the test user list. notionvc: 48fc5acf-1c63-495a-8cb1-ac2eca42134b notionvc: 48fc5acf-1c63-495a-8cb1-ac2eca42134b
Pop-up message precautions
Unlike push message testing, pop-up messages are one-time senders. Once you save a campaign, you can view the campaign on the test device or any device connected to the test user. However, if a campaign is terminated or deleted, the campaign will no longer be displayed, and the campaign will be displayed according to the language settings of the device.
If no language is set, the default language will be displayed.