Push Notifications

Ready to take your push notifications to the next level? Use Taplytics' integrated push notification service to immediately get in touch with your users at exactly the right time.

In general, push objects consist of five main elements.

Audience Selection:

To define the audience for your push notification, you can either brodcast your push notification to all clients, or target specific clients. If you wish to send to all users, do not specify any filters.

Filter Fields:

• The filters field is an array of objects. These objects have the following fields.

Filter Types:

In order to target specific subsets of your userbase, you will need to use one of the following targeting identifiers for your type field:

Examples - Filters:

"filters": [{
    "type": "an_version",
    "comparator": ">=",
    "values": ["5.0.0"]
},
{
    "type": "ios_version",
    "comparator": "!=",
    "values": ["8.0.1"]
},
{
    "type": "country",
    "comparator": "=",
    "values": ["Canada", "US"]
},
{
    "type": "custom_data",
    "comparator": ">=",
    "values": [16],
    "dataKey": "dollars spent"
}]

This filter will send the push notification to users who:

• Have an Android phone with a version greater than or equal to 5.0.0 OR have an iPhone with versions not equal to 8.0.1
• AND are currently in either Canada OR the US
• AND have a custom data field dollars spent with a value greater than or equal to 16

With great power comes great responsibility. Though this filter language is powerful, since you have so much control over how the data is manipulated, if used incorrectly there could be unintended consequences:

Examples - BAD Filters, DO NOT DO THIS:

"filters": [{
    "type": "ios_version",
    "comparator": "!=",
    "values": ["8.0.1", "8.1.3"]
},
{
    "type": "app_lang",
    "comparator": ">",
    "values": ["en"]
}]

• Since a user is matched if they fulfill ANY of the values in the array, this will send to every iPhone device. If they are on 8.0.1, then obviously they are NOT on 8.1.3. They will pass the check and thus the message will send to them. To avoid this unintended behaviour, create multiple filters per version
• Here you are using a 'greater than' comparator on a string. This will try and match on numerical ASCII values and will produce unexpected results.

Scheduled Messages:

Push notifications can be sent out immediately, or they can be sent out at a specific time. Additionally, they can be sent out at a standard time to everyone, or they can be sent out based on the audience member's local time.

One of these two strings must be provided. If they both are, local time takes precedence. All times must be in the future.

{
    "schedule": {
        "time": "2015-11-05T13:15:30Z",
        "local_time": "2015-11-05T13:15:30"
    }
}

This will get sent at each user's local time.