Feeding data from SnowPlow to Bitdeli sounds like a great idea.
1. It does, although it is an undocumented feature. You can send a list of events instead of a single JSON object to the Events API.
2. Bitdeli doesn't need an event type but it needs a user identifier. The event type is utilized with the data sources that provide it, like Mixpanel, but for instance our integration to the GitHub commits API doesn't expect that events contain a type.
A good starting point would be to create a super simple card that does something with the data from SnowPlow, like
Great stuff Vtuulos - I have signed up. Will probably take us a few weeks to get round to it as we have a few other releases which need to happen first...
Comments
Feeding data from SnowPlow to Bitdeli sounds like a great idea.
1. It does, although it is an undocumented feature. You can send a list of events instead of a single JSON object to the Events API.
2. Bitdeli doesn't need an event type but it needs a user identifier. The event type is utilized with the data sources that provide it, like Mixpanel, but for instance our integration to the GitHub commits API doesn't expect that events contain a type.
A good starting point would be to create a super simple card that does something with the data from SnowPlow, like
https://github.com/bitdeli/bd-rawevents-event-volume/blob/ma...
that just counts the number of events received over time.
Let me know if you want to give it a try - I am happy to extend your trial as long as needed.
Great stuff Vtuulos - I have signed up. Will probably take us a few weeks to get round to it as we have a few other releases which need to happen first...