My original intent with this was to allow for this to become more of an event tracking framework. I don't see these being as mutually exclusive. Some things should more configuration, though I see where you're coming from as far as burning through ET goals like content. I haven't taken a good look at your patch, how are you making the distinction between entity and bundle?

Comments

jlockhart’s picture

jlockhart
Primary language English
Location PNW Washington
commented

If I understand the Entity system correctly what I've created is a new Entity Type with basically one Bundle type. This allows us to use a lot of the magic sauce of the Entity API. In regards to the tracking framework concept I think that using the Entity system would work really well for that. Especially since there could be different bundles based on use case and data required.

frob’s picture

frob
Primary language English
commented

I am still not exactly following how you separate this up between bundles or why you want fields on these.

I get the concept of using entities for this. Google Analytics only allows for certain fields on its entity tracking. I understand that you want to add more events, but entities seem a bit heavy handed for it. You could use more of a serialized instance store and it would be much lighter.

frob’s picture

frob
Primary language English
commented
Status: Active » Closed (won't fix)

I see no reason to have fields on event tracking. Not doing this. It would make more sense to implement ctools exportables or something.