Send data push

Use Send Data Push to send a custom JSON payload to the mobile SDK through a silent push. The payload does not display a notification on the user's device. The mobile application receives the data and determines how to use it.

For example, an application can use a received content ID to update a recommendation module.

A JSON payload consists of keys and values. The key identifies the information being sent, while the value contains the data.

{
  "contentId": "podcast-123",
  "contentType": "podcast"
}

In this example, contentId and contentType are keys, while podcast-123 and podcast are their corresponding values.

Note: The mobile application must be configured to handle the keys and values included in the payload. Netmera sends the payload, while the application determines how to process the received data.

Use this action for immediate-action scenarios. Precise delivery timing is not guaranteed after a time-delayed Wait step.

Step 1: Add the action

1. In Journey Builder, select Add Step.

   1. Under Action, select Send Data Push.

   2. Enter a Step Name.

   Use a name that describes the purpose of the payload, such as Send podcast recommendation. The step name is visible only in the journey flow.

Select Send Data Push from the Action section.

Step 2: Choose a payload method

Choose one payload configuration method.

Both methods create the same payload. Choose Visual Builder when you want to add fields through the interface. Choose Edit JSON when you already have the JSON structure to enter or modify.

Use Visual Builder when you need to select profile attributes or journey variables field by field. Use Edit JSON when your application team provides the payload structure.

Method	Use it to
Visual Builder	Build the payload field by field.
Edit JSON	Enter or update the JSON payload directly.

Select a value source for each payload field.

Step 3: Configure payload values

Visual builder

Build the payload field by field. Each field consists of a key and a value source.

The key identifies the data that the mobile application receives. The value source determines where Netmera retrieves the value.

The following value sources are available:

Value Source	Description
Constant	Uses the same value for every recipient.
Journey Variable	Uses a value from the current journey.
Profile Attribute	Uses a value from the recipient's profile.

For example, you can configure the following fields:

Key	Value Source	Example
contentType	Constant	podcast
campaignId	Journey Variable	Current campaign ID
favoriteCategory	Profile Attribute	User's favorite category

The resulting payload may look like:

{
  "contentType": "podcast",
  "campaignId": "summer-2026",
  "favoriteCategory": "technology"
}

For a Constant value, enter the value directly.

For a Journey Variable or Profile Attribute, select the variable or attribute that contains the required value.

Important: Use keys that match the keys expected by the mobile application. For example, if the application expects contentType, using type will not work unless the application is implemented to handle that key.

Build the JSON payload field by field.

Edit JSON

Enter or modify the complete JSON payload directly in Edit JSON.

Make sure that:

• The payload contains valid JSON.

• The keys match the implementation in the mobile application.

• The values use the expected data types and formats.

Enter or update the payload directly in Edit JSON.

Step 4: Save the action

Select Save.

The Send Data Push step appears in the journey flow. When an eligible user reaches this step, Netmera sends the configured payload through a silent push.

The payload is not displayed as a notification on the user's device. The mobile application receives the data and determines how to process it.

Note: Send Data Push is intended for immediate-action scenarios. Precise delivery timing is not guaranteed when the action follows a time-delayed Wait step.

A saved Send Data Push step in the journey flow.