Add PushNotification Action page
|Action panel item||Description|
|A||Text box to give your action a descriptive, meaningful name.|
|B||Create a new action.|
|C||Load an existing action.|
|D||Create a new action based on the current action. This is useful if you’re setting up multiple similar actions.|
|E||Add a tag to categorize the campaign.|
|Push Notification Platform||Choose whether the push notification is for iOS, Android, or both platforms.|
|Message ID||Unique ID to identify the message in the Message Localization tool. You must provide your own ID when you create an action, or select an existing localized piece of text from the “Select a localization” drop-down list. You can assign other localized versions of the text in the Manage Localizations tool and the message delivery system will ensure the correct version is sent to the player based on their last known device language and territory. This is a mandatory field.|
|Message Body||The text that the notification displays. This can be any unicode character, including emojis. This is a mandatory field.|
|Badge (iOS only)||Sets the number that appears on the game icon. A value of zero clears the badge. If no value is given, the existing badge value is used.|
|Action Key (iOS only)||Changes the value that appears on the notification button to launch the game.|
|Sound (iOS only)||Sound file to play when the game launches, instead of the default sound. This must be a filename that matches a sound resource in the game build.|
|Image||Image to display when the game launches. This must be a filename that matches an image resource in the game build.|
|Add custom field||Add key value pairs to the notification payload for deeplinking. To save custom fields that you create, select the green commit button.
You can use custom fields to reward players or direct them to specific content within the game. Your game can read the values when it launches. The fields appear as top-level JSON keys in the notification object.
Google limits the total payload of all fields to 4096 bytes. Google Messages with optional data payload
Apple limits the total payload of all fields to 4096 bytes. Apple Payload Key Reference
|Add dynamic field||Add dynamic content to your notifications. This substitutes values into the notification when it is delivered.|
|Placeholder||String of characters to replace. This uses freeform text as the substitution key in your content. To prevent additional unexpected substitutions, ensure that the placeholder text doesn’t appear naturally in the value text. For example, you could wrap your substitution text in characters that won’t appear naturally, such as %maxLevel% or #lastMission#.
Ensure that the characters you use are acceptable with any third party content delivery channels.
|Type||Type of value to replace the placeholder.|
|Value||The value to replace the placeholder. This can be a metric or a constant value associated with the campaign content.|
Dynamic field types
|Dynamic field type||Description|
|Environment metric||One of your player’s metric values.|
|Derived metric||A derived metric that is calculated from a mathematical derivation of multiple other metrics or derived metrics. For example, you could create a missionSuccess ratio as a derived metric based on the missionCompleted and missionFailed event counts then use that dynamically in your message, such as “Because you lose in 65% of battles, here’s a bigger gun”.|
|Variant Property||Dynamically alter content for each variant group in a campaign. For example:
|Static||Static value that you define during campaign creation.|
|Localization||Pre-configured localization to display different values based on territory and/or language.|
Your game is responsible for reacting to any custom parameters you put in the payload. As such, you should plan and implement this when your developers are integrating with deltaDNA and planning your event collection and engagement specification.