Handle URLs in Messages

For security reasons, the Engagement SDK doesn’t automatically handle URLs sent in Push Notifications, In-App Messages, or Inbox Messages. Instead, your app’s code must handle the URLs that are passed to the SDK. Use the SDK’s URL handling methods to manage and process the URLs in your app.

The SDK doesn’t automatically present URLs from Alert+CloudPage push notifications.

Important

For more information about handling URLs from push notifications and in-app messages, see:

Handle Custom Keys

Marketers use custom keys to provide metadata for personalization and tracking information within a push notification. Here are some example use cases for custom keys:

A marketer uses AMPscript or a merge field to send metadata about a contact’s loyalty level.
A marketer sends an ID value for the app to retrieve additional data.
A marketer sends image URLs with the push notification to allow a developer to build and include a carousel of images for a rich push notification.

The Engagement SDK doesn’t automatically act on the custom keys delivered with the push notification. Your app’s code must handle the key-value pairs that it passes to the SDK. The SDK offers methods to facilitate custom key handling. See NotificationMessage.

Handle URLs in Messages

Handle Custom Keys

See Also