search

braze-inc / braze-web-sdk

Public repo for the Braze Web SDK
https://www.braze.com
Other
73 stars 26 forks source link

Get in-app message to display on user's first page view #25

Closed edwardchen closed 7 years ago

edwardchen commented 7 years ago

This message appears in the logs: Appboy: Not refreshing in-app messages because this is the user's first session.

Is there any way to get in-app messages to display on a user's first page view?

Thanks.

froodian commented 7 years ago

Hi @edwardchen,

That message is actually only relevant for "legacy" (non-triggered) in-app messages, so if you're using triggered in-app messages (referred to simply as "in-app messages" in our dashboard) you should disregard this message - it will be removed in an upcoming SDK release, apologies for the confusion. Triggered in-app messages should be available to users on their first page view, assuming they're targeted to a segment that includes new users.

edwardchen commented 7 years ago

Hi @froodian

I'm actually a little confused. My triggered in-app message is displaying that message in the log, AND the in-app message actually is not being displayed. My targeted segment is just All users in an app group, so I believe new users should be included.

I think what you're saying is that I should see it, but I...don't.

I'm following the Soft Push Prompt example under web push notifications.

froodian commented 7 years ago

If you have a custom subscriber, there are many reasons you may not be displaying the message, I would need to see your implementation - other deliverability issues could include using a trigger event that isn't one that is being fired, or creating the campaign with a control group or send limits - if you email support@appboy.com they'll be able to help you debug specifically what your deliverability issue is.

edwardchen commented 7 years ago

I did some testing and I think I know my issue. appboy.changeUser hadn't returned when I called appboy.logCustomEvent. Adding a short timeout before calling appboy.logCustomEvent made it properly display the message on the first pageview.

froodian commented 7 years ago

Ah, yes, that makes sense - I should have recalled, custom event triggers that are fired at the very beginning of the very first session can be prone to that issue - it's a cross-platform race condition with how in-app messages sync, we have it on our roadmap to iron out that particular wrinkle. Apologies again, glad you found a workaround!

edwardchen commented 7 years ago

No problem. Thanks for working through it with me.