UserActivityEvent vs Push

[Noel Welsh]

Hi,

Can someone explain to me the distinction between UserActivityEvent and Push? For example, when a user unsubscribes, a UserActivityEvent is created, but when an email is clicked a PushSentEmail is created. However UserActivityEvent has an enumeration that includes email clicks as a value -- though these events are never created afaik.

So why this distinction between saving some events as UserActivityEvents but others under the Push hierarchy? Shouldn't they all be of one type for uniform querying? If not, why does the UAE enumeration include values that aren't saved as UAEs?

Thanks,

N.

--
Noel Welsh
Untyped Ltd                 http://www.untyped.com/
+44 (0) 121 285 2285    in...@untyped.com
UK company number    06226466

[John McCarthy]

Hi, in the original version of the Platform, UserActivityEvent (UAE) stored action-related and email-related user activities. We later broke out email-related activities into the various push_x_emails tables (x = sent | viewed | clicked etc). This was done to improve the performance of the list cutter for large movements.

When an email is clicked, it must have been opened, so an open event is tracked if it doesn't already exist. Email sent activities are only created during blasting.

None of the email-related events are saved to the UAE table. Those methods persist on the UAE model however. Moving this to Push for instance could be a good idea. Please send your suggestions and we'll incorporate them into the work.

Thanks,

John

--
You received this message because you are subscribed to the Google Groups "Purpose Platform dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to purpose-platform...@googlegroups.com.

--

John McCarthy | Lead Developer, Purpose Platform | Purpose | jo...@purpose.com | 631.742.3484