Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expanding inbound_events table to record source & conversion path if available #174

Open
atwellpub opened this issue Apr 9, 2016 · 0 comments
Open

Expanding inbound_events table to record source & conversion path if available #174

atwellpub opened this issue Apr 9, 2016 · 0 comments
Assignees
@atwellpub

Comments

@atwellpub
Copy link
Member

atwellpub commented Apr 9, 2016 •
edited

In attempts to prepare for better internal analytics each event entry we record will also record:

  • source is available
  • conversion path if available

People are going to want to start seeing which source types are sending the more active traffic.

We are also going to want to see what our best performing funnels are, and what actions they are driving.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
@atwellpub atwellpub self-assigned this Apr 9, 2016
atwellpub added a commit to inboundnow/retired-cta that referenced this issue Apr 9, 2016
@atwellpub
Expanding inbound_events table
f2468f3 
inboundnow/retired-leads#174
atwellpub added a commit to inboundnow/inbound-pro that referenced this issue Apr 11, 2016
@atwellpub
perfecting funnel & source to inbound events:
ddc8eaf 
inboundnow/retired-leads#174
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@atwellpub atwellpub

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@atwellpub