Event metadata for campaigns #433
Conversation
| NSString *notificationURL = [metadata objectForKey:@"radar:notificationURL"]; | ||
| NSString *campaignId = [metadata objectForKey:@"radar:campaignId"]; | ||
|
|
||
| if (notificationText) { |
There was a problem hiding this comment.
| if (notificationText) { | |
| if (notificationText & campaignType = 'notification') |
There was a problem hiding this comment.
Am I right to say that this check is just for consistency?
Or do we see a future where we are explicitly using nearby geofences synced down for in app messaging as well?
There was a problem hiding this comment.
We discussed this in-person — idea is to be able to use the other metadata keys for different campaign types (notificaitons, in-app messages, etc)
There was a problem hiding this comment.
My impression was that that differentiation is only to be made for metadata on events, and implemented the checks within the logic extracting that info from the event based notifications.
Are you suggesting this change as we are intending to also leverage nearby geofences for in app messaging , hence necessitating this be done for both client side geofences and event based campaigns?
lmeier
changed the title
No description provided.