Clarification on In-App Messaging Display Timing #14982
Unanswered
ryoooooory
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm using Firebase in an iOS app via Swift Package Manager (SPM).
I have a few questions regarding the display timing of Firebase In-App Messaging, specifically when using auto-collected events like screen_view and session_start as triggers.
1, When registering messages with auto-collected events such as "screen_view" or "session_start" as triggers, the in-app messages are not displayed at the moment those events are fired.(I have confirmed that events like screen_view are being correctly triggered in Analytics (DebugView))
Why does this happen?
(It appears that no processing occurs on the In-App Messaging side when these events are triggered — e.g., FIRIAMDisplayCheckOnAnalyticEventsFlow.messageTriggered doesn't seem to be called.)
When tracing the internal processing within the Firebase SDK,
For "app_launch" and "on_foreground", messages are not triggered through event logging and listener callbacks via Analytics, but rather through internal lifecycle detection within In-App Messaging itself (as defined in FIRIAMRenderTrigger).
Therefore, when a message is configured with on_foreground as the trigger, it is automatically displayed at that timing in the app as well.
2, When I manually call logEvent("screen_view"), the In-App Messaging logic is triggered (via checkAndDisplayNextContextualMessageForAnalyticsEvent), but the event name is received as "_vs".
Why is this the case?
Because of this, even if a message is registered with "screen_view" as the trigger, calling logEvent("screen_view") in the app will not display the message.
Beta Was this translation helpful? Give feedback.
All reactions