This journey would attempt to convert readers into subscribers. Content sites have a critical KRA of increasing their subscriber base. Converting the process into journey would give you an edge in conversion tracking, testing, creating control messaging based on cross channel behavior etc.
Overview- This journey attempts to convert readers into subscribers. Content sites have a critical KRA of increasing their subscriber base. Converting the process into journey would give you an edge in conversion tracking, testing, creating control messaging based on cross channel behavior etc.
Industry- Blog/content website
Use-case- List building
Problem Statement- This journey would attempt to convert readers into subscribers. Content sites have a critical KRA of increasing their subscriber base. Converting the process into journey would give you an edge in conversion tracking, testing, creating control messaging based on cross channel behavior etc.
Events
a. Time spent > 5 mins
WebEngage.Track(‘time_spent_greater_5_mins’, {
/*String*/
Page url : dummypage.com
Referring URL : dummyreferralurl.com
/*Number*/
Number of pages viewed : 3
}
Step by step introduction to the journey
-
The journey is triggered when the user spends more than 5 minutes in a session.
-
Since we would want to convert only those visitors to subscribers who are not one already we would do the user’s attribute check in this step.
-
If the condition doesn’t meet then we would show the newsletter signup form to the user.
-
If he doesn’t submit the form, for app based companies there is another way to seek user’s consent and contact- mobile push. So, in this step we check if the user is reachable on mobile or not and if he does then we send him a link to opt-in form via push.
-
Once the user submits the form, we would make the API call and update the CRM with the form details.