All actions are currently stored as post meta data inside the user profile. I would like to see us migrate our 'Activity' into it's own table. This will make it easier to discover action data by either content id or lead id rather than lead id alone.
For example, if a form submission was stored in it's own table with a lead id and a page id associated to it then we would be able to easily discover all submissions related to a piece of content. We could also use metrics like datetime and event type to run more advanced reports than currently available with the current system.
[x] Create events table.
[x] Store form submissions,
[x] tracked content clicks (don't think we track clicks outside of calls to action do we? let's check wpl-track-me class) (doesn't look like it)
[x] tracked cta clicks
[x] tracked email clicks
[x] tracked email unsubscribes
[x] sent emails? (why did I write this?) (this can be pulled directly from mandrill using meta data lookups)
[x] Provide room for custom events
[x] Build batch importer and data migration system
[x] [activity tab] pull cta clicks from inbound_events table
[x] [activity tab] pull form submissions from inbound_events table
[x] [activity tab] pull email clicks from inbound_events table
[x] [activity tab] pull email unsubscribes from inbound_events table
[X] [Lead Listing][Lead Profile] calculate conversions from inbound_events table
[X] Sunset cta clicks' legacy method
[X] Sunset conversion calculation legacy method
[X] Sunset email clicks' legacy method
[x] Sunset email unsubscribe legacy method
This issue is not priority, but it is something that will improve our data archetecture in the future. It should not be hard to implement either. Data migration to the new system would be the hardest part of implementation.
All actions are currently stored as post meta data inside the user profile. I would like to see us migrate our 'Activity' into it's own table. This will make it easier to discover action data by either content id or lead id rather than lead id alone.
For example, if a form submission was stored in it's own table with a lead id and a page id associated to it then we would be able to easily discover all submissions related to a piece of content. We could also use metrics like datetime and event type to run more advanced reports than currently available with the current system.
tracked content clicks (don't think we track clicks outside of calls to action do we? let's check wpl-track-me class) (doesn't look like it)sent emails? (why did I write this?)(this can be pulled directly from mandrill using meta data lookups)This issue is not priority, but it is something that will improve our data archetecture in the future. It should not be hard to implement either. Data migration to the new system would be the hardest part of implementation.