LocalStorage entries do not have a fixed term and remain in place until the user deletes their browser data.

The following entries can be set. Most of these are only set for registered subscribers and some only when using special features (e.g. tagging subscribers).

All technically necessary Local & Session Storage entries can also be set if the user does not accept or ignores the CleverPush Opt-In Consent. They are necessary for the functionality of the CleverPush script and prevent, for example, that the opt-in is played out several times per user.

Technology: SessionStorage
Description: Contains data about the current session
Runtime: Automatically empties after closing the browser tab

Technology: LocalStorage:
Description: Contains data that is also required beyond the current session
Term: Without a fixed term

Technology: IndexedDB:
Description: Contains data required in the ServiceWorker used for registered subscriptions. The ServiceWorker has no access to the LocalStorage, so separate storage is necessary here.
Term: Without a fixed term

Der Beitrag Which cookies does CleverPush set? erschien zuerst auf CleverPush.

Step 1

SSH to your server and navigate to your Magento 2 installation folder.

Step 2

Add the composer repository for the Metrilo Magento 2 plugin to your setup:

composer config repositories.cleverpush-magento git “https://github.com/cleverpush/cleverpush-magento-plugin.git“

Step 3

Install the plugin:

composer require cleverpush/webpush

Step 4

Now that the plugin is successfully installed run:

$ bin/magento setup:upgrade

Step 5

Configure the plugin by going to “Store” > “Configuration” > “CleverPush”.

You can take the CleverPush Channel ID from Web Push Channel Settings under “General” > “Advanced Settings” in CleverPush.

Step 6

Clear any caches you might have to make sure that the CleverPush code appears on all of your pages.

$ bin/magento cache:flush

Der Beitrag Installing the CleverPush Magento Plugin erschien zuerst auf CleverPush.

The following reasons can ensure that the message is displayed as sent but not as delivered in CleverPush and may therefore not have been displayed on the device.

Network issues

Devices must have an active internet connection to receive push notifications. If the device is offline, in flight mode or has an unstable internet connection, the push message is only displayed when the connection is stable.
It is also important to note the set expiration date. By default, this is 28 days, but can be defined per push message and also globally in the CleverPush channel settings. If the device is offline longer than the defined expiration date, the message will no longer be displayed when the device comes back online.

In addition, it can happen that the device has lost the connection to the Apple or Google servers. We recommend deactivating the Internet connection on the device and then reactivating it.

iOS: If the device was offline and now goes online again, only the last push message sent is received by the device. Unfortunately, Apple has this limitation, see the APNS developer docs.

Targeting

Another possibility is that the device does not match the segments, tags or topics of the recently sent messages. It is advisable to locate the device in CleverPush under Channels -> Subscriptions in the subscription list. You can then see which segments etc. the device has in the subscription profile. If the device has no segments, it only receives messages that were sent without segmentation, i.e. to all users.

Push notification device settings

In the system settings of the device under Notifications -> (App Name) push notifications for the app can be completely deactivated. Here it is important to ensure that the necessary settings are all allowed.

Energy saving mode

Some devices have special energy saving rules that can either prevent the delivery of push messages or reduce the number of messages displayed.

Android: In the settings, search for:

• Energy saving mode or Battery – When “Battery Saver” and/or “Restrict Apps and Start Screen” is enabled, receiving all background activity (push notifications) will be restricted.
• Adaptive Battery – When enabled, the device will automatically turn on or off “Low Power Mode” based on usage patterns.
• Battery optimization or Background Usage Restrictions – Background features (such as push notifications) are limited for battery-optimized apps. Make sure your app is not optimized.

iOS: If the device is in energy-saving mode (recognizable by the yellow battery symbol at the top right), the number of notifications sent by the system can be throttled.

App was force-killed (Android)

When an app is in the Force Stopped / Force Killed state, most events, including FCM events for push notifications, are not received. An app can be brought into this state in the following ways.

• In Settings > Apps, “Force stop” is pressed.
• Long press the back button on some devices.
• Using a third-party task killer like Hibernator or Greenify.
• Automatically on some devices due to custom Android tweaks made by manufacturers. This is a known issue that affects all push providers. The website dontkillmyapp.com contains instructions for all common manufacturers on how to solve the problem on the device.

Do not disturb mode

Do not disturb mode ensures that notifications do not appear on the lock screen, but are still visible in the notification center.

Der Beitrag App Push Notifications are not received erschien zuerst auf CleverPush.

1. Sync events from CleverPush to Mixpanel (opt-ins, opt-outs, notification deliveries, notification clicks)
2. Sync cohorts from Mixpanel to CleverPush tags

Sync events from CleverPush to Mixpanel

In CleverPush, navigate to Channels -> (select channel) -> (select platform) -> Webhooks.

Here you can add a new Webhook:

Now, please select the type “Mixpanel” at the top. You should then see the following settings:

• Mixpanel server location: Depends on where your Mixpanel account is hosted (EU / non-EU)
• Mixpanel project ID: You can see it in your project settings: https://help.mixpanel.com/hc/en-us/articles/115004490503-Project-Settings
• Mixpanel Service account username & password: Please see the Mixpanel docs on how to create a new Service account: https://developer.mixpanel.com/reference/service-accounts
• CleverPush Attribute: Here you can select the attribute which will contain the “Distinct ID” from Mixpanel. This is required for matching the users from Mixpanel and CleverPush. This attribute can be populated via our SDKs, see below for some examples.
• Webhook events: The events you want be sent to Mixpanel

Sync cohorts from Mixpanel to CleverPush tags

Please see the official Mixpanel guide for more information on how to setup the Webhooks to Mixpanel:
https://developer.mixpanel.com/docs/cohort-webhooks

To setup the Webhook you will need to following data:

• URL:
  https://api.cleverpush.com/channel/CHANNEL_ID_HERE/mixpanel-webhook
  Please replace the Channel ID with your CleverPush channel ID. You can find the channel ID in the CleverPush backend when editing a channel. It is the last part of the URL (e.g. AbC123DeFgH123TgH)
• HTTP Basic Auth Username:
  apikey
• HTTP Basic Auth Password:
  Your CleverPush API Key, can be found in CleverPush under settings -> API.

Populate Mixpanel Distinct ID to CleverPush attribute

Der Beitrag Mixpanel Integration erschien zuerst auf CleverPush.

Head (Script):

<script async custom-element=”amp-story-player” src=”https://cdn.ampproject.org/v0/amp-story-player-0.1.js” ></script>

Body (Content):

<amp-story-player layout=”fixed” width=”360″ height=”600″>
  <a href=”https://stories.example.com/story-url-here“>Story Name</a>
</amp-story-player>

Der Beitrag Embed Web stories into AMP erschien zuerst auf CleverPush.

Step 1: Install the WordPress plugin

Navigate to “Plugins -> Install” in WordPress

Then enter “CleverPush” in the search at the top right. Install and activate the CleverPush plugin.

Step 2: Enter API data

Then navigate in WordPress to “Settings -> CleverPush”

Enter the API access data, which can be found in the CleverPush Backoffice under Settings -> API and save them.

Then select the desired channel from the drop-down menu and save again.

When new posts are published, you can now also send push notifications via the sidebar with a click on the right.

Step 3: Place files

f your website runs over HTTPS, please navigate to Channels -> (select channel) in your CleverPush back office.

There you will find the operating mode setting. Set this option to Own Domain (HTTPS).

The cleverpush-worker.js file can then be downloaded by clicking on the button.

This file must now be placed in the main directory of your web server. So it should be available at https://your-domain.com/cleverpush-worker.js.

Der Beitrag How to use the CleverPush WordPress Plugin erschien zuerst auf CleverPush.

It can be found under Settings » Teams. Create a new team there and select the channels you want to share. Now you have the possibility to enter the e-mail address of the desired user.

The user will then receive an invitation by e-mail, if he/she does not yet have an account.

Der Beitrag How can I give other people access to my channels? erschien zuerst auf CleverPush.

We will show the creation of a campaign using the example of abandoned shopping cart notifications (so-called “abandoned cart notifications”).

To do this, first select your channel in the “Channels” menu item and then click on the “Follow-Up Campaigns” tab in the menu on the left. Then you can create a new campaign via the green button.

You can now give your campaign a meaningful name and select the “trigger”. The trigger determines when a user enters the campaign. On the one hand, this can be the opt-in, ie the time of entry – but also an event that can be triggered via a tracking code.

The latter we will use for our example of shopping basket cancel notifications. As trigger event we choose “addToCart”. The crash event is very helpful as it allows us to stop the campaign with a user. In our case, we choose the event name “checkout”, which we will trigger later in a completed order process. Thus, no further notifications will be sent to the user when he has completed his order process correctly.

The notifications are arranged in time, you have the option to send a message after X days at XY clock, or directly XY minutes after the trigger or after the last notification. Also variables can be used, which can be sent along with the tracking code of the trigger event.

A variable is always written between curly braces and can be used in any field of the notification. The variable name is completely freely selectable. For example, you can include the productName variable with your {productName} in your notifications.

Then we save the campaign below. Now we can see the event tracking codes.

The codes can be installed on every page, where the normal CleverPush code is installed. Whether the code is included before or after the CleverPush Opt-In Code is not important.

Der Beitrag Creating follow-up campaigns in CleverPush erschien zuerst auf CleverPush.

2. Click on Project settings (Gear on the top left) > Service accounts in the Firebase console and then click Generate new private key.

3. Enable “Firebase Cloud Messaging API” in the Google Cloud Console for the previously created Firebase project

     When you click on the link, make sure that the correct Google account is selected if you have more than one. You can change the account in the top right if necessary.

3.1. Please ensure that the service account has the following permissions:

• cloudmessaging.messages.create
• firebase.projects.get

These permissions should be enabled by default for new Firebase projects. If you’re using a custom service account with limited permissions, you can add these permissions by assigning the following roles:

• roles/firebasemessaging.admin (includes cloudmessaging.messages.create)
• roles/firebase.viewer (includes firebase.projects.get)

4. Upload the Service Account JSON file in the CleverPush Channel settings at General > Android. If you cannot find the corresponding button for uploading, please activate “V1” as in the image below.

After you have carried out the above steps, there is a link from FireBase to CleverPush. Now you can start building the app in our system and later upload it to the Google Play Store. Further support articles will follow in the future.

Did you know already? – If you wish, we will be happy to advise and support you with your app project. Simply contact our CleverPush support via support@cleverpush.com or your personal contact person with us.

Der Beitrag How can I set my own FCM data (Firebase Cloud Messaging)? erschien zuerst auf CleverPush.

Der Beitrag How can my visitors unsubscribe from notifications? erschien zuerst auf CleverPush.