We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This all stared when it became obvious, on our end that users opting into our Wootric surveys went down significantly after a pod update.
This is because, after 'Segment-Wootric', '0.2.1' the SDK's behaviour changed automatically and by default the event name is sent.
'Segment-Wootric', '0.2.1'
event name
See WTRWootricIntegration.m line 45
WTRWootricIntegration.m
45
- (void)track:(SEGTrackPayload *)payload { NSDictionary *properties = payload.properties; NSString *eventName = payload.event; NSString *language = [properties objectForKey:@"language"]; if (language) { [Wootric setCustomLanguage:language]; } [Wootric setEventName:eventName]; }
This automatically started causing issues on our end as we saw a massive fall in users who participated in our surveys.
This is definitely an issue in the SDK, by default, it shouldn't be sending a an event name.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This all stared when it became obvious, on our end that users opting into our Wootric surveys went down significantly after a pod update.
This is because, after
'Segment-Wootric', '0.2.1'
the SDK's behaviour changed automatically and by default theevent name
is sent.See
WTRWootricIntegration.m
line45
This automatically started causing issues on our end as we saw a massive fall in users who participated in our surveys.
This is definitely an issue in the SDK, by default, it shouldn't be sending a an event name.
The text was updated successfully, but these errors were encountered: