Unregister Push Token

[AhmadNaeemK]

Checklist

• I have read the contributing guidelines
• This issue hasn't been addressed in an existing issue or pull request

Description

I can't find a way to unregister a user's push token if they opt out of push notifications after opting in once.

Proposed Solution

Implement unregisterPushToken method that calls the `unregister client push token` api and removes the push notification from Klaviyo.

Alternatives Considered

There's an unregister client push token api (https://developers.klaviyo.com/en/reference/unregister_client_push_token). The api requires the user's Klaviyo profile but there's no client api to fetch it. It would be great if there was a way to fetch the current profile too.

Additional Context

No response

[ajaysubra]

Hey @AhmadNaeemK! Thanks for this request. This is something we plan on implementing some time in the future. We are not sure of the timeline but will update this issue whenever we have any updates!

[PapaIII]

We also need this implemented.

[ccodrin]

I am facing this issue as well. Is there any update here?

[invctusdotco]

@AhmadNaeemK did you find a workaround? @ajaysubra any progress?

[AhmadNaeemK]

@invctusdotco I found a way to call the unregister api by making several other api calls to klaviyo but that's not usable. because of rate limits on them.

[ajaysubra]

Hey, folks! Sorry for the delay in responding. Unfortunately, there are no updates on this front yet. We plan to address this issue but do not have a timeline currently. I will post updates as and when we have them.

In the meantime, if it's not too much to ask, would you all be able to highlight the specific use case that you are trying to address with this SDK method? If users opt out of push notifications at the OS level (i.e., within the device's notification settings), Klaviyo will automatically opt that device out of push notifications the next time the user opens the app. Does that functionality not suffice for your use case? Do you have a notification preference in your app settings that will opt the profile out of notifications (in theory) across all devices? If you can provide any specific examples, that would be incredibly helpful. Thanks!

[AhmadNaeemK]

@ajaysubra We were trying to remove the push token when the user signs out. In our testing, some signed out users received push notifications on their devices.

[rafaellbaptista]

Hey everyone, I was also facing this issue, but if you use Klaviyo.resetProfile() when logging out, the push token will be disassociated from Klaviyo's user profile

[jakemadash]

@ajaysubra the use case for us is that our app uses multiple push services, so directing users to turn off all notifications from our app isn’t a viable option if they only want to turn off marketing (Klaviyo) notifications.

What would be even better than an unregister push token method would be one that allows you to control consent for push notifications at the profile level rather than per token.

In the meantime, we'll be calling several API methods as a workaround, but can you or anyone else advise what the correct enablement status should be after a token is unregistered? Thanks in advance.

[ajaysubra]

@jakemadash thanks for letting us know your use case and the suggestion for profile level consent. I will discuss this with the team.

As for the answer to you question goes, when unregister api is called the token is removed from the profile so there isn't a valid enablement status. If you are asking what are the enablement status we don't send a push notification to, that would be UNAUTHORIZED and DENIED

[jakemadash]

@ajaysubra thanks for the quick reply! I also added a post in the developer forum that goes into more detail about our use case and what we hope to achieve with the workaround in case that helps further the discussion.

[deanhet]

Just wondering if there's any progress on this issue? We've just stumbled into it too.

Our use case is we have a notifications preferences page in our app where the user can change how they want to be contacted. Right now if they want to turn off push notifications they have to exit the app and disable them at the operating system level instead? This is unlike airship or onesignal implementations I've used previously.

Additionally, if a user logs out with our current scenario. They will still receive pushes.

We tried a workaround of setting a custom attribute on the user (pushEnabled), and filtering our campaigns on that but the SDK also doesn't seem to have a way to fetch profile attributes either, so we can't set the state of the on/off button. Unless I'm missing something?

Any help would be much appreciated!

[ajaysubra]

@deanhet Thanks for highlighting your use case. I'll discuss this with the team and get back to you. Thanks for all the patience on this issue.