Skip to main content

Hi everyone,

We’re currently using Klaviyo for marketing campaigns and have enabled push notifications (via web or mobile). I’d like to know how we can opt customers out of receiving push notifications, especially for marketing campaigns.

Specifically:

  • Is there a way to unsubscribe a user from push notifications, similar to email unsubscribes?

  • Can users self-manage their push notification preferences (e.g., via profile or a preference center)?

  • Is there a way to programmatically suppress or remove users from the push channel?

The goal is to ensure we’re fully compliant and that customers who no longer want push messages don’t receive them.

Thanks in advance for your help!

Hi ​@MostafaOsama , welcome to the community

 

Klaviyo does not have an "unsubscribe" button for push like it does for emails. If someone turns off notifications on their phone or browser, klaviyo will stop sending them messages automatically.

 

There's no built in page where people can manage push settings. If you want that, you will need to create it yourself on your website or app. 

Klaviyo already stops sending to anyone who blocks notifications, so you just need to keep your lists clean and give people clear ways to opt out.


Thanks for your answer ​@MANSIR2094, currently we are dealing with user email subscription. as per Klaviyo API documentation, i should be able to update email subscription using update profile API, as per doc i should able to add “subscription” field to update email consent. but it always throughs the following error “"'subscriptions' is not a valid field for the resource 'profile'."”. is update profile endpoint could really do that? it their another way to achieve same goal.


@MostafaOsama You are right to look into the API for managing email subscriptions, but currently, the upload profile API in klaviyo does not support the subscriptions field. That's why you are getting the error. To update a users email subscriptions status (like subscribes or unsubscribe) you should use the subscribe profiles endpoint instead. This is the correct way to manage consent for email.

 

The update profile endpoint is only for updating profile properties, not subscription preferences.