Default Events

Default events are user events that Insider defines for your account in advance. These events are based on the requirements of Insider’s products and common user actions. In addition to the default events, you can create custom events for actions not covered in this list or for specific custom use cases.

The default events are categorized as:

• Pageview Events
• User Events
• Mobile App Events
• Email Events
• Architect Events
• Web Push Events
• WhatsApp Events
• SMS Events

Pageview Events

Default Pageview Events are fired based on the page type a user is on at that time. For example, if a user is visiting the home page, the Homepage View event is triggered along with the respective event parameters. The default pageview events and their event parameters are as follows:

• Homepage View: Session ID, source, URL, device type, and referrer.
• Listing Page View: Session ID, taxonomy, source, URL, device type, and referrer.
• Product Detail Page View: Product ID, name, taxonomy, currency, unit price, unit sale price, quantity, product image URL, session ID, unit size, source, URL, device type, and referrer.
• Cart Page View: Product ID, name, taxonomy, currency, unit price, unit sale price, quantity, unit size, product image URL, session ID, event group ID, category, source, URL, device type, and referrer.
• Purchase (Confirmation Page View): Product ID, name, taxonomy, currency, unit price, unit sale price, quantity, product image URL, session ID, shipping cost, voucher name, voucher discount, promotion name, promotion discount, event group ID, quantity, unit size, color, source, URL, device type, and referrer.
• Other Pageview: Session ID, source, URL, device type, and referrer.

User Events

Default User Events are fired based on user actions. For example, if a user joins a lead collection campaign, the Lead Collected event is triggered. If they clear their cart, the Cart Cleared event is fired. The default user events and their event parameters are as follows:

• Cart Cleared: Session ID
• Item Added to Cart: Product ID, name, taxonomy, currency, unit price, unit sale price, stock, color, size, product image URL, session ID, shipping cost, voucher name, voucher discount, promotion name, promotion discount, event group ID, source, quantity, URL, device type, and referrer.
• Item Removed from Cart: Product ID, name, taxonomy, currency, unit price, unit sale price, stock, color, size, product image URL, session ID, shipping cost, voucher name, voucher discount, promotion name, promotion discount, event group ID, source, URL, device type, and referrer.
• Signup Completed: No event parameter
• Lead Collected: Campaign ID

Mobile App Events

Default Mobile App Events are triggered by mobile app campaigns and are based on users' interactions with these campaigns. For example, if a user sees an inApp campaign, the InApp Seen event is fired. The default mobile app events and their event parameters are as follows:

• InApp Seen: InApp ID, variant ID, dismiss type, Journey ID, and Journey Name.
• Push Delivered: Camp ID, camp type, deep links, dry run, image URL, message, title, variant ID, Journey ID, and Journey Name.
• Mobile Social Proof Seen: No event parameter
• App Push Opened (push_session): Variant ID, camp type, camp ID, Journey ID, and Journey Name.
• Mobile App Opened (session_start): No event parameter
• Survey Result (survey_result): camp_id, variant_id, answer, crea, and question.

Email Events

Default Email Events are fired by the Email campaigns and are based on users' interactions with these campaigns. For example, if a user clicks a link in an email campaign, the Email Click event is triggered.

The default email events and their event parameters are as follows:

• Email Delivered: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, Journey ID, and Journey Name.
• Email Open: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, machine open, human open, Journey ID, and Journey Name.
• Email Click: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, URL, URL offset index, URL offset type, Journey ID, and Journey Name.
• Email Bounce: Email campaign ID, campaign name, variation ID, subject, IP address, reason, type, Journey ID, and Journey Name.
• Email Block: Email campaign ID, campaign name, variation ID, subject, IP address, reason, type, Journey ID, and Journey Name.
• Email Spam Report: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, Journey ID, and Journey Name.
• Email Group Unsubscribe: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, group ID, Journey ID, and Journey Name.
• Email Group Resubscribe: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, group ID, Journey ID, and Journey Name.
• Email Unsubscribe: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, Journey ID, and Journey Name.
• Email Resubscribe: Email campaign ID, campaign name, variation ID, subject, user agent, IP address, Journey ID, and Journey Name.

Architect Events

Default Architect Events are fired by the Architect journeys and are based on users' interactions with these campaigns. For example, if a user enters a journey, the Journey Enter event is triggered. The default Architect events are as follows:

• Journey Enter: Journey ID, name, and reason.
• Journey Exit: Journey ID, name, and reason.

Journey Enter Reasons

The following can be the value for the reason parameter:

• Unified
  • The same user enters the journey as two different user profiles, gets unified while still in the journey, and continues the journey as one unified user.
  • User A becomes eligible to enter a journey and then gets unified with user B. In this case, user A becomes user B in Insider's Unified Customer Database, which means that user B enters the journey as it is unified.
• Natural: The user was eligible to enter the journey naturally.

Journey Exit Reasons

The following can be the value for the reason parameter:

• Exited: The user fulfilled any of the Exit Criteria and exited the journey.
• Completed: The user reached the end of a path and completed the journey.
• Dropped: The user was unreachable from the channel element and was dropped from the journey.

Web Push Events

Default Web Push Events are fired by the Web Push campaigns and are based on users' interactions with these campaigns. For example, if a user clicks a Web Push notification, the Web Push Click event is triggered. The default Web Push events and their event parameters are as follows:

• Web Push View: Variant ID, Campaign ID, and Campaign Name
• Web Push Click: Variant ID, Campaign ID, and Campaign Name

WhatsApp Events

Default WhatsApp Events are fired by the WhatsApp campaigns and are based on users' interactions with these campaigns. For example, if a user replies to a WhatsApp message with the second button, the WhatsApp Reply Second Button event is triggered.

The default WhatsApp events and their event parameters are as follows:

• WhatsApp Click: Variant ID, Campaign Name, Journey ID, and Journey Name.
• WhatsApp Delivered: Variant ID, Campaign Name, Journey ID, and Journey Name.
• WhatsApp Reply: Variant ID, Campaign Name, Journey ID, and Journey Name.
• WhatsApp Reply First Button: Variant ID, Campaign Name, Journey ID, and Journey Name.
• WhatsApp Reply Second Button: Variant ID, Campaign Name, Journey ID, and Journey Name.
• WhatsApp Reply Third Button: Variant ID, Campaign Name, Journey ID, and Journey Name.
• WhatsApp Reply Other Reply: Variant ID, Campaign Name, Journey ID, and Journey Name.
• WhatsApp Unsubscribe: Variant ID, Campaign Name, Journey ID, and Journey Name.
  Your title goes here

  If only the identifier is used and the user unsubscribes after receiving the latest journey message, the journey parameters are recorded.
• WhatsApp Read: Variant ID, Journey ID, and Journey Name.

SMS Events

Default SMS Events are fired by the SMS campaigns and are based on users' interactions with these campaigns. For example, if a user clicks a URL in the SMS message, the SMS Click event is triggered. The default SMS events and their event parameters are as follows:

• SMS Click: Variant ID, Campaign Name, Journey ID, and Journey Name.
• SMS Delivered: Variant ID, Campaign Name, Journey ID, and Journey Name.
• SMS Unsubscribe: Variant ID, Campaign Name, Journey ID, and Journey Name.
• SMS Subscribe: Variant ID, Campaign Name, Journey ID, and Journey Name.
• SMS Undelivered: Variant ID, Campaign Name, Reason Type, Journey ID, and Journey Name.
• SMS Reply: Variant ID, Campaign Name, Reason Type, Journey ID, and Journey Name.
• SMS Campaigns: Variant ID
• SMS Drop: Variant ID, Campaign Name, Reason Type, Journey ID, and Journey Name.