You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Viewed and screen appended to the screen event name by default and I need to remove them as we have a structure for the events and we also depend on these values and we have a huge old data on customer.io, so we need to keep the current structure.
Example:
screenName I passed to the SDK: Account Screen Opened
event shown on the customer.io's dashboard: Viewed Account Screen Opened Screen.
You may need to look into the comments of this issue
How can we remove this?
Also if you need any help to remove these texts or make it optional I can contribute on both IOS and Android.
Thanks in advance.
Which platform is the issue occurring on
Is the error occurring on:
[1] Both Android and iOS
SDK initialisation snippet
Flutter 3.24.1
Framework version of the SDK
rudder_sdk_flutter: ^3.0.1
Check for Correct Usage of writeKey and dataPlaneUrl
All correct.
The text was updated successfully, but these errors were encountered:
Describe the bug
Viewed and screen appended to the
screen
event name by default and I need to remove them as we have a structure for the events and we also depend on these values and we have a huge old data on customer.io, so we need to keep the current structure.Example:
screenName I passed to the SDK:
Account Screen Opened
event shown on the customer.io's dashboard:
Viewed Account Screen Opened Screen
.You may need to look into the comments of this issue
How can we remove this?
Also if you need any help to remove these texts or make it optional I can contribute on both IOS and Android.
Thanks in advance.
Which platform is the issue occurring on
Is the error occurring on:
SDK initialisation snippet
Flutter 3.24.1
Framework version of the SDK
rudder_sdk_flutter: ^3.0.1
Check for Correct Usage of writeKey and dataPlaneUrl
All correct.
The text was updated successfully, but these errors were encountered: