Replies posted by markpiana

20 Replies

jsaleniuk
Contributor I
jsaleniukContributor I
asked in Developer Group

toastNotification.errorMessages.fcm_unspecified_error when sending an Android notification

Hi @jsaleniuk ! This issue could be due to a variety of issues, so it’s hard to tell without more information. However, I can try to point you in the right direction.Can you confirm that you’ve uploaded the correct file for the google service account key and that it has all of the right permissions? This guide should walk you through all of the necessary steps to ensure your key has the right permissions and you’re uploading the right file. Can you confirm that the token is linked to a profile in Klaviyo? If not, the send will fail. Is the token that you’re using for the same version of your app for which uploaded credentials in Klaviyo? Some people have run into issues when they try to use a token from a test version of an app but have their production credentials in Klaviyo. Look at the sender ID mismatch error here for more context. This error looks like it’s happening when you send a preview notification. Have you tried sending an actual campaign to a this device? If it fails when

4
markpiana
Klaviyo Employee
5 days ago
ocastx
Contributor I
ocastxContributor I
asked in Integrations and Reviews

Update push token from client

Hi @Hoang Dung, As general guidance, please make sure that you are following our React Native documentation, specifically the directions for collecting push tokens. Based on the error message, it appears that you do not have a push token associated with the profile to which you would like to send a push notification. You may also take a look at our example app that demonstrates how to use the Klaviyo SDK for more help.If after following those instructions, you still have issues, please contact Klaviyo Support for additional help.Thanks,Mark

7
markpiana
Klaviyo Employee
1 month ago
D
Contributor I
daniarora.17Contributor I
asked in Developer Group

Push Notification for React Native app

@Hoang Dung to find your public API key, follow this guide - https://help.klaviyo.com/hc/en-us/articles/115005062267.In terms of actually implementing that code, I would refer to our iOS SDK docs for more guidance. https://github.com/klaviyo/klaviyo-swift-sdk?tab=readme-ov-file#event-tracking

17
Y
Contributor I
3 months ago
D
Contributor I
daniarora.17Contributor I
asked in Developer Group

Push Notification for React Native app

@Hoang Dung you’re in luck! We just released a beta version of our react native SDK. Here are some links to help you get started.NPM - https://www.npmjs.com/package/klaviyo-react-native-sdk Github - https://github.com/klaviyo/klaviyo-react-native-sdk Help docs - https://help.klaviyo.com/hc/en-us/articles/22344173696539

17
Y
Contributor I
3 months ago
D
Contributor I
daniarora.17Contributor I
asked in Developer Group

Push Notification for React Native app

Hi, everyone! I’m Mark from the Klaviyo product team. We’ve heard your request for a React Native SDK and are actively working on one now. We expect to have an initial version available for use in the near future, so keep an eye out for updates soon. Sorry I can’t say anything more specific in terms of dates!Mark

17
Y
Contributor I
3 months ago
J
Contributor I
jemantillaContributor I
asked in Developer Group

Hybrid - Push notification Not Working in Production

Since sending to iOS through FCM is not currently supported, my hunch is that that is the cause of the issue somehow, but it is hard to troubleshoot this problem without more specific information about your account. If you haven’t yet, I would recommend creating a Klaviyo Support ticket, so we can take a look at your account and more thoroughly help you triage this issue. https://www.klaviyo.com/support

10
J
Contributor I
5 months ago
J
Contributor I
jemantillaContributor I
asked in Developer Group

Hybrid - Push notification Not Working in Production

Just confirming again, have you updated the tokens in Klaviyo to be platform = ios and vendor = apns?

10
J
Contributor I
5 months ago
J
Contributor I
jemantillaContributor I
asked in Developer Group

Hybrid - Push notification Not Working in Production

Just to confirm, are you using an APNs token for iOS and still getting that error? If you’re using an FCM token, that won’t work. If you are using an APNs token, make sure that you are using a token for the correct environment. If your app is in production (i.e., in the App Store or TestFlight), you have to use a production token. If you’re using a debug build, you should use a sandbox token. 

10
J
Contributor I
5 months ago
J
Contributor I
jemantillaContributor I
asked in Developer Group

Hybrid - Push notification Not Working in Production

Hi @jemantilla ,Klaviyo does not currently support sending iOS push notifications through FCM. All iOS push notifications are routed through APNs. Therefore, when you try to send to an iOS device using an FCM token, APNs flags the token as invalid, and Klaviyo removes the token from the profile.To send push notifications to iOS devices, you will need to follow the steps in our guide for setting up iOS push notifications, including uploading your APNs authentication key in your Klaviyo account settings. Plus, when you send iOS tokens to Klaviyo via the API, you will need to set the vendor to APNs. I hope that helps! Thanks,Mark

10
J
Contributor I
5 months ago
K
Contributor I
KorpycContributor I
asked in Developer Group

Push notifications on iOS not work in debug mode

@jenssoegaard We now support sending to Apple Sandbox as long as you are using v2.2.0 or higher of the Klaviyo Swift SDK. With that version and above, we automatically collect the environment for each token when you send it to Klaviyo, so when you try to send to a token, we funnel sends to the right environment. If you’re building a wrapper / bridge for React Native to the Swift SDK, I believe this functionality should still work.Also for testing purposes, you may want to make use of our new feature that enables sending preview notifications. https://help.klaviyo.com/hc/en-us/articles/18011985278875

7
J
Contributor IV
4 months ago
ocastx
Contributor I
ocastxContributor I
asked in Integrations and Reviews

Update push token from client

Hi @ocastx !Klaviyo now has a client endpoint specifically for creating and updating push tokens - https://developers.klaviyo.com/en/reference/create_client_push_token. This endpoint is the only way to add or update push tokens.The previous answer will NOT work for actually sending push notifications. It is possible to create a profile property for push tokens and store tokens there; however, Klaviyo will not use that profile property when actually attempting to send notifications.Thanks,Mark

7
markpiana
Klaviyo Employee
1 month ago
C
Contributor I
chaqmeowContributor I
asked in Developer Group

Public and stable Android SDK for push notifications

Hi @chaqmeow!Yes, our Android SDK is now public and stable. We will continue to make improvements to the SDK and release new versions, but you should feel comfortable using v1.3.1.Thanks,Mark

1
markpiana
Klaviyo Employee
9 months ago
R
Contributor I
RukshanContributor I
asked in Developer Group

Why are my IOS push notifications not sending?

Hi @Arvind ,In case you are still having issues, we recently created the Bounced Push event where you can see more details about the sending failure, including the specific iOS or Android error. You can use this information to troubleshoot any issues you’re having.  Thanks,Mark

3
markpiana
Klaviyo Employee
9 months ago
K
Contributor I
KorpycContributor I
asked in Developer Group

Push notifications on iOS not work in debug mode

Hi @Korpyc ,I’m the Klaviyo product manager for mobile push notifications. I’m assuming when you’re trying to send a notification to a local build that you’re trying to use the APNs Sandbox environment. We do not currently support Sandbox tokens, but this functionality is coming very soon. Until then, you should use TestFlight builds to ensure that push notifications are working correctly through Klaviyo if you want to test before fully publishing your app.Thanks,Mark 

7
J
Contributor IV
4 months ago
Y
Contributor I
YoungContributor I
asked in Campaigns and Flows

What is Smart Sending window for push notification?

Hi @Young ,In case you are still curious about push smart sending windows, you now can create a custom smart sending window for push that is distinct from email under your push notification settings. By default, the window is set to 24 hours. See our guide to understanding your push notification settings for more details. Thanks,Mark

2
markpiana
Klaviyo Employee
9 months ago
M
Contributor I
Manish-fueledContributor I
posted in Developer Group

Sending custom payload with push notifications

Hi @Manish-fueled, I’m the Klaviyo Product Manager responsible for mobile push notifications. Would you mind sharing more information about your use case? What are you hoping to do with the flow ID / message ID? Would you change the state of your app based on it?In case you were not aware, you currently can find information about the campaign / flow / message in the Received Push event in Klaviyo. Is that sufficient for your use case?Thanks,Mark

4
markpiana
Klaviyo Employee
9 months ago
R
Contributor I
rtsao
asked in Integrations and Reviews

Is there a Workaround for using Deep links for push notifications?

Hi @rtsao,I know it has been a while since you asked your initial question, but I wanted to provide a quick update. Klaviyo released the ability to include deep links in push notifications in March 2023 along with support for Android. For more information about how to leverage deep linking, see our guide called How to use deep links in push notifications. If you have any feedback or questions about the functionality, let us know!Thanks,Mark

2
markpiana
Klaviyo Employee
9 months ago
Jon Palmer
Klaviyo Employee
Jon PalmerKlaviyo Employee
published in News & Announcements

Product Update: BenchmarksNews

@Mhagen we’re a couple months behind schedule, but as of today, you should be able to update any flows you see selected in Benchmarks!

4569
markpiana
Klaviyo Employee
3 years ago
Jon Palmer
Klaviyo Employee
Jon PalmerKlaviyo Employee
published in News & Announcements

Product Update: BenchmarksNews

@Travis Great question! Currently, we are not accounting for the number of emails in a flow. Instead, we’re simply averaging the percentages across all of the emails in a flow - an approach that we know has drawbacks. We have the ability to compare specific emails in a flow to each other on the roadmap, but I do not have a specific timeline for when that update will be available. 

4569
markpiana
Klaviyo Employee
3 years ago
Jon Palmer
Klaviyo Employee
Jon PalmerKlaviyo Employee
published in News & Announcements

Product Update: BenchmarksNews

Hi @Mhagen !I’m the Klaviyo Product Manager working on Benchmarks. We’re happy you’re excited about this new feature, and thanks for all of your great feedback!You have pinpointed the number one feature request for Benchmarks thus far. Our flow classifying algorithm is solid, but as with any algorithm, there is some error. As a result, we know that we need to give users the power to update the flows for each category, and we aim to release that functionality in Q1. I’m sorry for the temporary frustration, but hang tight for a month or two!In the meantime, we update Benchmarks every month by the 10th of the month. Every time we update the data, we refresh the flows for each category, so your changes will take effect when we release the data for December 2020, which should happen in the next few days. Specifically for the Welcome Series Flow, we do look for flows with the word “Welcome” in the name, so your intuition was correct. When the data updates in the next few days, you should see

4569
markpiana
Klaviyo Employee
3 years ago

Most helpful members this week

Terms & ConditionsCookie settings

Links & Resources

Platforms

Partners

Useful Things

About

  • Terms and Privacy
    © 2024 Klaviyo All rights reserved. Klaviyo and the Klaviyo logo are trademarks or registered trademarks of Klaviyo, Inc. or its affiliates.