Content is a JSON response that is served to the users via Channels with Messages. Content can be used for many purposes: app configuration changes for A/B testing, sales promotions, displaying messages, push notifications, emails, and alerts to users, etc.

The content has a Content Type associated with it that can be seen as a template that defines the structure of the JSON. Both Contents and Content Types can be found in Engage > Content.

Creating Content Types

Navigate to Engage > Content > Content Type. You will see a list of existing Content Types. Create a new one by clicking 'New Content Type' and selecting either "Display", "Push", or "Email".

Display Content Type

Under Display Content Type, you have the option to configure the following:

  • Content Template
    • in raw JSON (or)
    • using a form
  • Preview Templates
    • Teaser Template (only for Display content)
    • HTML Template

Creating Content

Navigate to Engage > Content. You will see a list of existing Contents. Add a new one by clicking 'New Content'. Here you choose the Content Type you want to use for the Content, or create a new Content Type.

The Content view will list all Content Types available. Select one Content Type. This opens up a page to create (or edit) the Content using predefined JSON schema, if available.

Omniata does not limit the contents of the JSONs in any way. However, when serving the Content via push notifications, pay attention to the guidelines by Apple and Google.

Using Remote Content

Remote content can be embedded in the Content JSON as a URL request:

"id": "value",
"name": "<%= GET('') =%>"

Replace the example URL ( with the URL of the remote content in question.

Using User Properties

Values of User State and Custom User Fields (user variables) can be embedded in the Content JSON:

"key": "value",
"first_day": "<%= $user_state->{'first_daynum'} %>"

Replace first_daynum with the machine name of the User State field in question.

Note: Do not use the machine name of a System User Field, but the machine name of a field in User State.

"key": "value",
"level": "<%= $user_vars->{'cuf_level'} %>"

Replace cuf_level with the machine name of the Custom User Field in question.

This article was last updated on February 24, 2016 22:44. If you didn't find your answer here, search for another article or contact our support to get in touch.