Discussion

A typical EVGScreen context is active when the screen is visible and the app is not backgrounded.

Besides some initial setup just before becoming visible/active (setCampaignHandler:forTarget:, viewItem: etc), activity generally occurs while a context is active.

Context activity, in addition to app state and user idleness, can affect campaign delivery, see setCampaignHandler:forTarget:

Discussion

Campaigns can potentially be received in response to actions (see trackAction:) and item interactions (see viewItem: etc) tracked on this context.

The target is an app-defined string that uniquely identifies the payload data schema - what the data represents and its purpose. See [EVGCampaign target].

While the context, app, and user is active, the handler may receive asynchronous callbacks (on the main thread) with campaigns for the target, in response to actions/events sent. The handler code should show/update the campaign to the user, when appropriate, and follow best practices using weak references, see EVGCampaignHandler for example code.

Campaigns may be held for delivery while either:

• The context, app, or user is inactive
• No handler is found for the campaign’s target within this context

For each context and target, only the most recent campaign will be held.

Lifecycle details for an EVGScreen based context:

• Recommended to always call this method just before becoming visible, specifically UIViewController viewWillAppear:.
• In order to prevent accidental leaks in the handler block (see weak references in EVGCampaignHandler example code to prevent this), a screen has a limited time to become visible, after which its handlers and held campaigns will be cleared.
• When a screen transitions to not visible (viewWillDisappear:), all handlers and held campaigns are cleared.

These limitations and automatic cleanup do not apply to [Evergage globalContext].

Discussion

Evergage automatically tracks clicks on push notifications. However, when the notification is received while the app is in the foreground, the notification is not automatically shown to the user. If you are using UNUserNotificationDelegate, you have some options with userNotificationCenter:willPresentNotification:withCompletionHandler :

• If you don’t show anything to the user, there is no click to track.
• If you show the notification with UNNotificationPresentationOptionAlert, Evergage will automatically track any user click.
• If you don’t show the notification, but instead render some other UI based on the notification, and want to track user clicks, call this method when the user clicks on the associated UI.

Discussion

Recommended to call just before visible, viewWillAppear for a view controller.

Evergage will automatically track the time spent viewing the item while the context, app, and user is active. The item will remain the one viewed until this method or viewItemDetail: are called again.

Discussion

Only tracks an action if item is non-null.

Discussion

Recommended to call just before visible, viewWillAppear for a view controller.

Evergage will automatically track the time spent viewing the item while the context, app, and user is active. The item will remain the one viewed until this method or viewItem: are called again.

Discussion

Only tracks an action if item is non-null.

Discussion

Recommended to call just before visible, viewWillAppear for a view controller.

Discussion

Only tracks an action if category is non-null.

Discussion

Recommended to call just before visible, viewWillAppear for a view controller.

Discussion

Only tracks an action if tag is non-null.

Discussion

A cart can be considered an ‘open’ order. Most carts will not have an orderId, and so the field can be left un-set.

Discussion

If the order contains no lineItems, the lineItems currently in the cart will be used. If orderId is set and multiple purchase events are received for the same orderId, all but the first will be ignored.

Discussion

When considering the action name, remember that datasets encompass multiple platforms and apps. The name can match a corresponding action/behavior from another platform/app. A campaign can use a source rule to be limited to a specific source or set of sources. See Mobile Data Campaigns Guide for recommended rules.