Content Viewed
Content Viewed records a member opening any content the church uploaded. It was previously called Scripture Viewed.
Status: sent today
The mobile app sends Content Viewed. Today it sends content_id, title, and feedId rather than reference, and the section* properties are not sent yet.
Content Viewed
Description: Triggered when the Screen/Page event occurs on any content uploaded by the client (in daily habits or elsewhere) and a successful response is received.
Destinations: BigQuery, HubSpot, Amplitude.
Funnel:
Button Used: content searched, content opened.Content Viewed
| Property | Type | Required | Description |
|---|---|---|---|
content_id | Integer | Yes | The client-provided identifier for the content being viewed. |
reference | String | Yes | The full scripture reference that was viewed (book, chapter, and verse). Effectively the name or "label" of the content. |
sectionId | String | No | ID of the feed Section the item was tapped from (the feature's own ID, e.g. HorizontalCardListFeature:<base64>). Only present when opened from inside a Section; omitted when opened from Search, Tap, or a related/child item. |
sectionLayout | String | No | Feature type of that Section, e.g. HeroListFeature, HorizontalCardListFeature, ActionListFeature. |
sectionTitle | String | No | Display title of that Section, e.g. "Featured". |
user_id | String | Yes | Internal unique identifier for the individual performing the event. |
group_id | String | Yes | Internal unique identifier for the organization of the individual performing the event (church slug). |
email | String | Yes | Email for the individual performing the event. |
phone | String | Yes | Phone for the individual performing the event. |
is_logged_in | Boolean | Yes | If the user was logged in when performing the event. |
Implementation example:
javascript
analytics.track('Content Viewed', {
content_id: 1234,
reference: "Genesis 1:1-10",
...
user_id: "",
group_id: "",
email: "",
phone: "",
is_logged_in: true
});