BETA FEATURE
Custom event usage monitoring is a beta feature. It is subject to Iterable's Beta Feature Disclaimer.
As your Iterable projects grow to contain more users—and more custom events from their interactions with your marketing campaigns, websites and apps—you'll likely want to understand which custom events they're using and how they're being used.
Iterable's Custom Event Usage screen provides details about a project's custom events, how many have been saved, and the workflows and dynamic lists that reference them.
This screen does not include information about contact profile fields—only custom events.
Table of contents
Custom Event Usage screen
To view the Custom Event Usage screen, you'll need the Project Configuration > Project Settings permission. With that permission, navigate to Settings > Current Project > Custom Event Usage.
This screen displays usage data for an Iterable project's top 1000 most saved events (as counted over the project's entire lifetime). It only displays events that the project has saved at least once (regardless of whether or not they're specified on the Settings > Project Settings screen).
On this screen, you can select a date range from which to display events, filter and sort custom events, view the dynamic lists or workflow nodes that reference them, and export the displayed data.
NOTE
- If your Iterable project has a large number of custom events, the data on this screen may load slowly. Iterable refreshes this data once per hour.
- Currently, the data displayed on this screen does not include campaign custom conversion events.
- The Last Seen column describes the most recent time that Iterable saved each event (from an API call, a customer data platform integration, etc.). Events that are Allowed but not Saved (as configured on the Settings > Project Settings screen), do not impact this value.
Selecting a date range
To select a date range from which to display saved events, use the date picker near the top of the screen. Make sure to pay attention to the selected times and time zones.
NOTES
- After you use the date picker to narrow your search, the Custom Event Usage screen still only counts and displays events whose names correspond to the top 1000 all time most collected event names in your project. However, the counts the screen displays only include events which were collected during the specified date range.
- For any given set of dates, Iterable caches the results of the custom events usage query for one hour (for all users of the Iterable project). Because of this, if you make a query, new data arrives, and you make a new query with a different date range, you may see inconsistent counts until the cache refreshes.
Viewing dynamic lists that reference a particular custom event
When defining segmentation queries for dynamic lists, you might select contacts who have particular custom events saved to their Iterable profiles. From the Custom Event Usage screen, you can view the dynamic lists whose segmentation queries reference particular custom events by clicking the numbers in the List References column.
For example, in the above table, clicking the
promoRedeemed event's List References value brings up the following screen:
On this screen, you can navigate to a dynamic list's details by clicking its name, and export the table's data by clicking Export to CSV.
NOTE
Segmentation queries used to define static lists can reference custom events, too. However, when saving static lists, Iterable does retain their segmentation queries—and therefore loses any association with custom events. Because of this, the Custom Events Usage screen only counts and displays dynamic list references.
Viewing workflow nodes that reference a particular custom event
Workflows can reference custom events in trigger and filter nodes. To view these references on the Custom Event Usage screen, click the number found in an event's Workflow Node References column.
For example, in the above table, clicking the
completedOnboarding event's Workflow Node References value brings up the
following screen:
From here, you can view the related workflow node's details by twirling open the arrow in the Nodes column, navigate to a workflow's definition by clicking its name, and export the table's data by clicking Export to CSV.
Comments
0 comments
Article is closed for comments.