Push Notifications¶

The Push Notifications feature allows you to create messaging campaigns and send them to your users in the field, in order to react faster and gather feedback.

This feature requires Famoco Layer version 3.18.0 or above.

Experimental Feature (Beta - β)

This feature is in its β-phase and is an ongoing experiment. Some things might not work as expected.

Create a template¶

The first step in creating a messaging campaign is to define what it will contain and how it will be displayed to your users. In the sub-menu "Templates", you can define the basis of your future messages.

By clicking the "+ New" button, a form will open and allow you to define:

A title for your template, in order to differentiate it from other ones
A title for the message itself that will show up on the notification
A message to be displayed below the title
Text and background colors for the notification window
Optional images or videos to be displayed
One or two buttons, their text color, and whether they contain a link to be opened when the user presses it or not

About images and videos

Famoco will not host your images and videos. The URL to provide must be a direct URL to said ressource (i.e. an URL ending with .png, .mp4 or others, not a YouTube URL)

Permissions

The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface or the MDM API.

You can pick and choose these permissions when creating a new Custom Role or MDM API token.

Permission category - "Push Campaigns - Templates"

Read (fms.pushcampaigntemplate.read)

What it does: Allows users to:
- Access the Push Campaigns - Templates page
- Send Push Campaigns via the Device panel (using the Send Push Message button)
Note that the following permissions are also required to see the Send Push Message button in the Device panel:
- fms.pushcampaign.create
- fms.pushcampaign.read
- fms.pushcampaigntemplate.create
Where it applies:
- Push Campaigns - Templates page (/push-campaigns/templates)
- Devices page (/devices)
What happens without this permission:
- The Push Campaigns page is not accessible.
- The Send Push Message button in the Device panel is not visible.

Create (fms.pushcampaigntemplate.create)

What it does:
- Create Push Campaign Templates
- Send Push Campaigns via the Device panel (using the Send Push Message button)
Note that the following permissions are also required to see the Send Push Message button in the Device panel:
- fms.pushcampaign.read
- fms.pushcampaign.create
- fms.pushcampaigntemplate.read
Where it applies:
- Push Campaigns - Template page (/push-campaigns/template)
- Devices page (/devices)
What happens without this permission:
- The buttons to create and send Push Campaigns are not visible.
- The Send Push Message button in the device panel is not visible.

Update (fms.pushcampaigntemplate.update)

What it does: Allows users to edit Push Campaign Templates.
Where it applies: Push Campaigns Templates page (/push-campaigns/templates).
What happens without this permission: The buttons to create Push Campaign Templates are not visible.

Delete (fms.pushcampaigntemplate.delete)

What it does: Allows users to delete Push Campaign Templates.
Where it applies: Push Campaigns Templates page (/push-campaigns/templates).
What happens without this permission: The buttons to delete Push Campaign Templates are not visible.

Sending a messaging campaign¶

If you want to create a messaging campaign, go to the "Campaigns" sub-menu and press the "+ New" button.

Name your campaign to identify it
Define your message content, either by selecting an existing template (which you can modify on the fly by pressing the button) or by composing a new message that will not be stored as a template, for a one-shot message
Select the audience for your campaign, either by selecting target fleets of devices, or by selecting specific devices that will receive the message (you can search devices and select them on a dropdown, or upload a file containing the Famoco IDs of your desired audience)

Once you have created your campaign, it will be stored as a Draft, in order for you to select the perfect moment to send it. When that time comes, press the "Send" button at the end of the row concerning your campaign.

Before sending, if you think you made a mistake, you can still edit the campaign by selecting it and pressing the button on the action bar. However, once it is sent, the contents of the message is not modifiable.

After sending, clicking on the row of a campaign opens its side panel which displays information about the campaign's state: how many notifications were sent, how many devices were not eligible to receive the message and how many users pressed on which button.

Permissions

The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface or the MDM API.

You can pick and choose these permissions when creating a new Custom Role or MDM API token.

Permission category - "Push Campaigns"

Read (fms.pushcampaign.read)

What it does:
- Access the Push Campaigns page
- Send Push Campaigns via the Device panel (using the Send Push Message button)
Note that the following permissions are also required to see the Send Push Message button in the Device panel:
- fms.pushcampaign.create
- fms.pushcampaigntemplate.read
- fms.pushcampaigntemplate.create
Where it applies:
- Push Campaigns page (/push-campaigns)
- Devices page (/devices)
What happens without this permission:
- The Push Campaigns page is not accessible.
- The Send Push Message button in the Device panel is not visible.

Create (fms.pushcampaign.create)

What it does:
- Create and send Push Campaigns
- Send Push Campaigns via the Device panel (using the Send Push Message button)
Note that the following permission is also required to send Push Campaigns:
- fms.pushcampaign.update
Note that the following permission are also required to see the Send Push Message button in the Device panel:
- fms.pushcampaign.read
- fms.pushcampaigntemplate.read
- fms.pushcampaigntemplate.create
Where it applies:
- Push Campaigns page (/push-campaigns)
- Devices page (/devices)
What happens without this permission:
- The buttons to create and send Push Campaigns are not visible.
- The Send Push Message button in the device panel is not visible.

Update (fms.pushcampaign.update)

What it does: Allows users to edit and send Push Campaigns.
Note that the following permission is also required to send Push Campaigns:
- fms.pushcampaign.create
Where it applies: Push Campaigns page (/push-campaigns).
What happens without this permission: The buttons to create and send Push Campaigns are not visible.

Delete (fms.pushcampaign.delete)

What it does: Allows users to delete Push Campaigns.
Where it applies: Push Campaigns page (/push-campaigns).
What happens without this permission: The buttons to delete and send Push Campaigns are not visible.