• Type: Browser error
• Description: Error provided by the browser. An existing registration token may cease to be valid in a number of scenarios, including:
  • If the contact unregisters for receiving Web Push notifications.
  • If the registration token expires.
• Troubleshooting:

1. Check your Web Push segmentation criteria and only include Push Enabled users (Recommended).

2. Check your implementation of the Emarsys web SDK for setting the push tokens.

• Whom to contact: Your website developer if you want to check it is not a technical issue.

• Type: Segmentation error
• Description: At the time of sending we were not able to find any browsers linked to the contact selected by the segmentation criteria. This error message could also mean that the specific contact has been deleted. In this case, we recommend combining your Web Push segment with a combined segment including all contacts.
• Troubleshooting: Check your segmentation criteria. It might contain a condition that is contradictory to what you want to achieve, or potentially, it could also select inactive or old users.
• Whom to contact: Marketer

• Type: Personalization error
• Description: We were not able to resolve personalization details for the contact. This might be due to missing data on the contact level that are required for sending the message out.
• Troubleshooting:

1. Check your campaign and personalization attributes that you are using.

2. Check if the personalization is required for the message.

• Whom to contact: Marketer

• Type: Browser error
• Description: Error provided by the browser. The specified browser token is invalid.
• Troubleshooting: Check your implementation of the web SDK.
• Has your domain certificate been changed recently?
• Whom to contact: Your website developer.

• Type: Browser error
• Description: Error provided by the browser. The VAPID key is used when gathering the Web Push permission from the contact and it does not match with the VAPID key used when sending the campaign. The VAPID key is the authentication method used to send to all browsers (with the exception of Safari) and it is normally configured when onboarding with the Emarsys Web Push feature.
  Alternatively, two Web Push providers (i.e. Emarsys and another provider) are being used in parallel, by having the Emarsys Web SDK and the other provider's SDK on the same web page at the same time. For instructions on how to migrate correctly, see Web Push - Migrating from a previous provider.
• Troubleshooting: Check the VAPID key.
  • Has the VAPID key been changed mistakenly?
  • Has the VAPID key been ceased using the other provider?
• Whom to contact: Your website developer.

• Type: Browser error
• Description: The public key used for requesting subscription on the website does not match the one defined in Emarsys.
• Troubleshooting: Check if the VAPID key in Emarsys (domain configuration) matches with the public key used in the web SDK initialization.
• Whom to contact: Your website developer.

• Type: Browser error
• Description: Error provided by the browser. The VAPID key is used when gathering the Web Push permission from the contact and it does not match with the VAPID key used when sending the campaign. The VAPID key is the authentication method used to send to all browsers (with the exception of Safari) and it is normally configured when onboarding with the Emarsys Web Push feature.
• Alternatively, two Web Push providers (i.e. Emarsys and another provider) are being used in parallel, by having the Emarsys Web SDK and the other providers SDK on the same web page at the same time. For instructions on how to migrate correctly, see Web Push - Migrating from a previous provider.
• Troubleshooting: Check the VAPID key.
  • Has the VAPID key been changed mistakenly?
  • Has the VAPID key been ceased using the other provider?
• Whom to contact: Your website developer.