Layout

It helps you arrange basic elements, such as text, images, or buttons, in a visually appealing way. Refer to the table below for the various layouts for your web message.

You can drag and drop any layout on the canvas. The right pane has two sections: General and Style, each offering different options.

Refer to the table below to learn more about General options.

Refer to the table below to know more about Style options.

Basic Elements

You can start your template with basic elements like text, image, divider, spacer, and so on.

Refer to the table below to know the description of basic elements.

Forms

Web message forms let you collect data and engage users directly within your web messages. You can customize forms to suit different needs, whether for collecting simple data, scheduling appointments, gathering feedback, or meeting other requirements.

Drag and drop the Form into the template. A configuration panel appears on the screen, allowing you to set up the form details.

The Unified Content Editor (DIY) provides five types of forms:

1. Basic

This form has one field for quick data collection, such as email addresses or phone numbers. It is used to collect basic information from users.

2. Simple

With multiple fields, this form gathers more detailed information, such as names and addresses, while staying easy to fill out.

3. Appointment Form

An Appointment Form allows users to schedule meetings or appointments by selecting dates and times from a calendar. It may include fields for personal details and appointment preferences.

4. Multi-Step Form

You can break down a longer form into multiple steps or pages. It guides users through the data entry process in a structured manner, often including progress indicators.

Form Step Configuration

The Form Step Configuration feature lets you control how users move through multi-step forms. You can change the default step order. For example, skip directly from Step 1 to Step 3 if needed. Define conditions to direct users based on their answers. You can create up to two conditions for each step. This feature helps you guide users through a more personalized form experience based on their responses.

📘

Note

Form Step Configuration applies to NPS, Emoji, Dropdown, Radio button, and Upvote/Downvote questions.

💬

Examples

Example 1: Custom Step Progression

If you want users to skip Step 2 if they select a specific answer. Configure the form so that users who choose this answer move directly from Step 1 to Step 3.

Example 2: Adding conditions based on answers

Question: What is your preferred mode of transport?
Options: Car, Bike, Bus

Step Configuration:
If the answer is Car, direct users to Step 4.
If the answer is Bike, direct users to Step 5.
If the answer is Bus, direct users to Step 6.

5. Feedback Form

You can gather users' opinions, ratings, and comments. It typically includes fields for rating scales, comment boxes, and specific questions related to user experience.

Click the icon to add more steps to your form. You can add up to 10 steps, with the 11th step being the success message (confirming that your response has been recorded).

Refer to the table below for other functionalities available when editing form elements.

Function	Description
Duplicate Element	Creates a copy of the selected element.
Move Up	Shifts the selected element one position higher in the order.
Move Down	Shifts the selected element one position lower in the order.
Delete Element	Removes the selected element from the layout.
Select Date	Allows the user to choose a date from a calendar.
Select Time	Allows the user to choose a time from a time picker.

Response Collection

When users submit a form, sync this data to the Netcore CE dashboard. This updates your Contact Master with new information.

Follow the steps given below to set up the Form Response Collection.

1. On the right pane of the Editor, under the General section, click Form Setup next to Response Collection.
2. A window titled Select an App to Integrate With will open. Click Configure.
3. Map the form submissions to the user attributes as needed. Click Save to apply the mappings. Netcore’s Contact Master has now been successfully attached.
4. Click Save Configurations to finalize the setup. You can edit the configuration later if necessary.

📘

Important Points to Remember

• Response Collection is a mandatory step.
• Responses on email will directly update user attributes. This might impact existing segments, campaigns and journeys.
• You don’t need to map the primary key (like email or mobile) to attributes.
• Anonymous users (those who don’t provide identifiable info) can’t be stored in attributes.
• Ensure your form includes a primary key (like an email) because it’s required for Lists.
• You can add form responses to existing lists by selecting the preferred segment from a dropdown menu.

Form Elements

You can start customizing your form with form elements like a radio button, star rating, heading, input, dropdown, and so on.
Refer to the table below to learn about the form elements available in the editor.

The right pane has two sections, General and Style, each offering different options for customizing your form elements.

Refer to the table below to learn more about General options.

Refer to the table below to learn about Style options.

This feature will be available soon. Stay tuned for updates!

Setup

Refer to the table below for the sections under Setup.

Fill in all the required sections and proceed.

The Advanced details have the following features:

1. Google Analytics Tracking

Enable tracking to monitor campaign performance via Google Analytics.

• Source (utm_source): Identify the origin of your traffic, such as a search engine or newsletter.
• Medium (utm_medium): Specify the marketing medium, like email, social, or CPC (cost-per-click).
• Campaign (utm_campaign): Name the specific campaign, like a product launch or a seasonal sale.
• Content (utm_content) (Optional field): Differentiate specific campaign content or links.

📘

GA Tracking Guidelines

• Ensure you're using Netcore Android SDK v3.5.0 and Netcore iOS SDK v3.5.0 for GA tracking.
• Netcore provides personalized values for {CHANNEL} in utm_medium and {CAMPAIGN_NAME} in utm_campaign.
• Personalized values are not supported for utm_source and utm_content.
• Character validation allows only: a-z A-Z 0-9 - _ . @ : ' / { }.
• UTM values auto-populate based on global settings once enabled.

Example: Redirection URL with utm_source = Smartech, utm_medium = {CHANNEL}, utm_campaign = {CAMPAIGN_NAME}, utm_content blank: https://domain.com/collections/payday?utm_source=Smartech&utm_medium=in-app&utm_campaign=25Jan_TRIWellSale.

2. Conversion goals

Add conversion goals to monitor key business metrics and measure the success of your web message campaign. You can track one conversion goal per campaign. Select any event as a conversion goal activity according to your objectives.
For example, if you want to track the number of customers who have purchased shoes after your campaign was sent. (Event - Product Search, Product - Shoes).

• Specify payload parameters: You can define criteria for the conversion event payload. You can add up to 5 parameters that are available for customization.
  For example, specify a Purchase event when the product price exceeds 10,000.
• Conversion Window: Select this option to define the time frame for successful actions after interacting with your campaign.
• Revenue Parameter: Select this option to assign a value to each successful action for tracking financial impact.

3. Control group

These are the number of users you intentionally exclude when sending campaign content. They serve as a reference point for evaluating the effectiveness of your campaign.

📘

NOTE

Setting up a conversion goal is mandatory when using the Control Group feature.

To exclude users in the control groups, do the following:

1. Toggle on the control group to exclude the users in the control group from the campaign's target segment.
2. Specify the percentage of users you want to exclude from the campaign using the scroller/ slider.

Audience

The Audience section allows you to select who to target your web messages. It has the following sections:

• Trigger
• Filters
• Select Contacts
• Exclude Contacts

A Trigger determines when to display the in-app message based on specific user actions or conditions. Trigger events in this section activate in-app message displays to users. When a user performs any defined event, the message appears. You can add up to five triggers in a campaign.

Refer to the table below for the Triggers available when creating an in-app message.

Set a trigger event as follows:

• Event: Choose from the dropdown menu (e.g., Add to Wishlist, App Launch).
• Geofence Events Support: Choose a User Exited, User Entered, or User Dwelled geofence. Select geofence criteria like name or group as payload parameters. You can also select criteria such as geofence name and geofence group as payload parameters. For geofence setup instructions, refer to this document.

Refer to the table for descriptions of geofence events.

• Delay: Introduce a delay (up to 120 seconds) between the triggering event and message display.
• Specify Parameters: Further refine payload parameter criteria for the event.
  Add multiple trigger events and delays to display the same in-app message across different app sections.

📘

Minimum SDK version requirements

To utilize multiple trigger events, update to Netcore Android SDK v3.1.23 and Netcore iOS SDK v3.1.10 or newer.
For delay functionality, update to Netcore Android SDK v3.5.0 and Netcore iOS SDK v3.5.0 or newer. Older SDK versions only use the first added event as the trigger.

Select Contacts

Choose a specific segment or list to define the audience for the in-app message after the trigger event. Pick up to five user segments or lists. Use for targeting based on historical behavior captured by server-side user segments.

📘

Note

Select list/segment from your saved segments because you cannot create a new segment in this section.

Exclude Contacts

After the trigger event, select the list or segment of users to exclude from the in-app campaign. The multi-select dropdown allows you to choose up to 5 lists or segments. Once you have made 5 selections, multi-select will be turned off for additional lists.

📘

SDK Requirements for Features

List & Segment Selection and Multi-event Conditions: Available on Android SDK v2.2.19 and iOS SDK v2.5.5. Ensure you migrate to the AndroidX library if not already done.
Event Filter Criteria: Only the last 200 events stored locally on the device are considered.
Exclude Contacts Functionality: Available on Android SDK v3.5.0 and iOS SDK v3.5.0 or newer.

Content

After the basic setup and defining the target audience, Content is the section where you can create your template. In this section, you can create your in-app message using various template positions and editing options to make your template stand out.

Refer to the table to learn about the template positions for creating an in-app message.

Once you have selected the in-app position, proceed to create the template.

Click Create New under the Select template option. This lists all the templates for the in-app message channel based on the selected layout. You can create a template from scratch with these three options:

1. Text only: A message that consists solely of text.
2. Image only: A message that includes only an image without any accompanying text.
3. Custom HTML

Refer to the table below, which outlines the various features and their specifications for different types of in-app message templates.

Text-only

Select the Text only option to create the content for your in-app message. As you proceed, you see these options on the left pane and its preview on the right pane.

1. Text

   1. Title: The main heading or headline of your message.
   2. Message: The detailed text or body of your in-app message.

2. Background

   1. Color
      Solid: Choose a single color for the background.
      Gradient: Select a gradient color scheme for a more dynamic background.
   2. Image
      URL: Use an image from a web link.
      Upload Image: Upload an image from your device.

3. Action button

   1. Action title: The text appearing on the action button.
   2. Call to action: Define what happens when clicking the button. Refer to the table to learn about the actions available here.
   
   

   Call to action	Description
   Open a URL	Directs the user to a specified web address.
   Send SMS	Opens the SMS app with a pre-filled message.
   Call this number	Initiates a phone call to a specified number.
   Deep Link	Redirects to a specific section within the app.
   Whatsapp	Opens a conversation in WhatsApp.
   Email	Opens the email client with a pre-filled email.

   3. Enter URL here: Provide the URL for the action.

📘

Note

The supported file formats are JPEG, JPG, and PNG, with a maximum size of 100 KB and a2:1 resolution.

Image only

Select the Image only option to create the content for your in-app message. As you proceed, you see these options on the left pane and its preview on the right pane.

1. Image
   1. Choose type
      URL or Upload Image

Media URL: Add the direct link to the media file or image.
Redirection URL: The URL that users will be taken to when they click on a link.

2. Action button
   1. Action title: The text appearing on the action button.
   2. Call to action: Define what happens when clicking the button. Refer to the table to learn about the actions available here.

📘

Note

• Image size restrictions are recommended for optimal user experience and apply to images uploaded on the Netcore CE dashboard. To use larger images, use the self-hosted image URL feature.
• Personalize in-app messages using event payload parameters to provide a tailored experience for your customers.

As you compose your in-app message, preview it in real time. The Send Test Message feature helps you preview the final message that your user will receive. You can view how your In-app messages look on different devices and screen sizes. Make adjustments on the spot to ensure clarity and engagement. This way, your message is consistent, appealing, and effective before you send it out.

Follow the steps below to test your in-app message.

1. Click the Send Test Message button on the right pane of the Content screen.
2. Choose the device on which you want to preview the in-app message. There is no limit to the number of devices you can select. Refer here to learn how to add a test device.

The Reset option clears previously chosen devices. It allows you to select new devices or prevent unintended recipients from receiving test messages.

3. Click Send Test Message to test and view your In-app message.
4. Click Done to complete the process.

Schedule

Finish creating and previewing your web message, then schedule your campaign.

• Under Start campaign, select Send Now to send immediately or select Send later to send it on your desired date and time.
• Under Campaign frequency, you can control how often a user views your campaign. Under Select the frequency, you have three options.
  • Time per session: Number of times a web message is shown per session.
  • Time per day: Number of times a web message is shown in a day.
  • Time per campaign: Number of times a web message is shown per campaign.
    Fill in the required fields according to your preference. Before saving your campaign, you can also select Additional Settings.