The Iterable SDK provides easy code to track user events enabling your team to record a specific action at a given time. Iterable will also collect user track calls from your website, mobile-app, tablet or offline events to ensure all of your events aggregate back to the same user across multiple devices.
Table of contents
Event tracking specifications
Before you start adding Iterable event tracking SDK code to your app, you will want to spec-out which events to track. At a high level, you will want to think about each of the milestones within your user journey (sign up, viewed product, add to cart, purchase, share). Your Iterable Implementation Manager can assist on this section but we also have some recommended events in the following sections.
It is not recommended to add a session event or app launch event to your app because it happens far more frequently than other events. This creates a noise and can distract from the main signal coming from your data.
Campaign Attribution is the idea of attributing (or giving credit) a particular conversion event (or user action) to a given campaign.
For example, if you are testing different content in three push notification
campaigns, you will want to track and attribute your conversion event to
ensure your team knows which push notification is most effective for your
given user base. Some common custom conversion events could be:
Iterable uses two common methodologies for attributing events back to particular campaigns. By default, the majority of the mobile attribution tracking will be automatically handled by the SDK.
Here are the two options for attribution when creating a campaign within Iterable:
Campaign ID explicitly set
Only conversion events with a campaignId field set to this campaign will be attributed to the campaign.
When the Attribution Window is chosen, all Custom Conversions Events in the given time frame will be automatically attributed to the that particular campaign.
To learn more, read Tracking Custom Conversions.