Default Events

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

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

The 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

The 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

The Default Mobile App Events are fired by the mobile app campaigns, and 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, and dismiss type.
• Push Delivered: Camp ID, camp type, deep links, dry run, image URL, message, title, and variant ID.
• Mobile Social Proof Seen: No event parameter
• App Push Opened (push_session): Variant ID, camp type, and camp ID.
• Mobile App Opened (session_start): No event parameter
• Survey Result (survey_result): camp_id, variant_id, answer, crea, and question.

Email Events

The Default Email Events are fired by the Email campaigns, and 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: Campaign ID, campaign name, variation ID, subject, user agent, and IP address.
• Email Open: Campaign ID, campaign name, variation ID, subject, user agent, IP address, machine open, and human open.
• Email Click: Campaign ID, campaign name, variation ID, subject, user agent, IP address, URL, URL offset index, and URL offset type.
• Email Bounce: Campaign ID, campaign name, variation ID, subject, IP address, reason, type.
• Email Block: Campaign ID, campaign name, variation ID, subject, IP address, reason, type.
• Email Spam Report: Campaign ID, subject, user agent, and IP address.
• Email Group Unsubscribe: Campaign ID, campaign name, variation ID, subject, user agent, IP address, and group ID.
• Email Group Resubscribe: Campaign ID, campaign name, variation ID, subject, user agent, IP address, and group ID.
• Email Unsubscribe: Campaign ID, campaign name, variation ID, subject, user agent, and IP address.
• Email Resubscribe: Campaign ID, campaign name, variation ID, subject, user agent, and IP address.

Architect Events

The Default Architect Events are fired by the Architect journeys, and 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 to the journey as one unified user.
  • User A becomes eligible to enter a journey, 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 enter 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

The Default Web Push Events are fired by the web push campaigns, and 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
• Web Push Click: Variant ID

WhatsApp Events

The Default WhatsApp Events are fired by the WhatsApp campaigns, and based on users' interactions with these campaigns. For example, if a user replies 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 Reply: Variant ID
• WhatsApp Click: Variant ID
• WhatsApp Delivered: Variant ID
• WhatsApp Reply First Button: Variant ID
• WhatsApp Reply Second Button: Variant ID
• WhatsApp Reply Third Button: Variant ID
• WhatsApp Reply Auto Reply: Variant ID
• WhatsApp Reply Other Reply: Variant ID
• WhatsApp Unsubscribe: Variant ID

SMS Events

The Default SMS Events are fired by the SMS campaigns, and 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
• SMS Delivered: Variant ID
• SMS Unsubscribe: Variant ID