We kind of know who you are
An email ID is a lead and only way to get the email ID, is to ask for it. But how should you do it?
Overview:
Users, both anonymous and registered, show similar behaviour on your web/mobile app. Just the lack of contact details limits the business to reach out to these users when you need to. Businesses like content, media, entertainment where reachability across channels impact retention and finally conversion rate, it gets critical to convert such anonymous users to registered contacts and further nudge them to become paid customers.
It’s necessary to engage with new users while they are on the website to convince them to sign-up, so that different channels of communication can be used later. Only way to get the email ID, is to ask for it. However, you don’t talk about the customer’s email address upfront. Instead, focus all your persuasion power on what they, the customer will receive in exchange.
This journey looks to trigger an user registration flow for engaged anonymous users. Engagement for content may have a direct correlation with scroll % till which the reader has read the content. Anonymous users are tracked from the user profile having PII data associated with them.
Industry:
Content/OTTs
Use Case:
Onsite Lead Generation
Segments:
Anonymous User: Have no PII associated with user profiles such as contact no., email_id etc.
Events:
page_scrolled
Webengage.Track(“page_scrolled”, {
/*String*/
“Name” :
“Email” :
“Contact” :
“Page URL” :
“Occupation” :
“Gender” :
/*Date*/
“Date_Of_Birth” :
"Date_Of_Contact_Creation" :
/*Number*/
“Scroll percent” :
/*Boolean*/
“Logged_in” : 0
“Newsletter_subcribed” : 0
})
Step-by Step Explanation:
1. Journey gets triggered for a user enters anonymous user segment.
2. If the user scrolls 60% of a page, workflow triggers an onsite notification, asking users to complete their registration, to help share latest news updates and offers.
3. On form submit, end the journey for that user. As long as the user does not submit the form, user stays in this journey. This way user does not get the same push every time he scrolls a page.
Pro tip:
- Set an exit trigger for user entering 'known user segment'. Workflow checks if the user's profile has any PII details. If the user is found to be registered, the workflow gets over for that user.
- You can make separate journeys for different kinds of on site items to get user’s contact details. Eg: There can be a journey anonymous users who have page viewed>3.