Feb 22nd - Churn, Push delivery and De-ghosting

This time around we have several updates to you that focus on: churn analysis using the Look Ahead jobs that can also be used for several other types analysis, updates to push delivery with re-occurring delivery and ability to send push on-demand, and user de-ghosting that combines two different accounts when user starts using a new UID for example from social media, or another global identifier.

Churn Analysis with Look Ahead analytics

Omniata has new type of data processing that allows you to use future user attributes to process historical data. These jobs are called Look Ahead jobs and can be used to answer questions like:

  • Who are my churned (spending) users?
  • What stage of progression did they churn?
  • How long did the spenders retain before churning?
  • How does behavior of non-spenders and spenders differ?

We have created a starting package for you to start working with the Look Ahead analysis. It can be installed under Data > Packages > Look Ahead Template.

More information can be found here.

Re-occurring Push delivery and Push Now

Omniata Push notification delivery has been updated to include options to schedule for a re-occuring delivery. The previous limitation of a single push notification per user per campaign has now been removed and users can receive up to 20 messages during the campaign. The messages can also ne scheduled to be delivered on re-occurring intervals ranging from 1 to 120 days.

In addition, Omniata now allow sending push notifications on-demand. For this you create a push campaign, select a scheduling to be On-demand. Save the campaign and run an On-demand job to identify the segment and to send the messages. Once the job is completed, the messages will be delivered rightaway or according to the campaign schedule.

Find out more about the push notification feature from here.

User De-ghosting

This feature provides support for cases when user’s temporary identifier changes after linking to a previously used account, or a social media account. The events received with the ghost UID are ignored both during nightly and on-demand processing and do not affect any metrics.

Technical details

  • same day jobs do not include de-ghosted processing and users are counted as new
  • in case user receives de-ghosting event and regular events in different days, user will not be de-ghosted in the previous days until the de-ghost event arrives
  • in case user receives event after the de-ghosting event, she will be counted as a new user

More information on this feature can be found here.

This article was last updated on February 22, 2016 23:57. If you didn't find your answer here, search for another article or contact our support to get in touch.

Contact Sales

Add Phone Number