Open jessevondoom opened 11 years ago
We may also want to consider the same thing for transactions. It's a duplication, but would save expensive table lookups for analytics...
+1 to have an optional element_id as a part of an order
Yeah. Didn't need it before because analytics tied it all together, but with the aggregated analytics option it basically made it all a big question mark. It'll be a big help.
Should also bring through a referral URL along with the element ID for orders so we are aware of where the user ordered from.
Good call. We already grab the URL where the element was embedded so if we included that along with the ID there's some serious intelligence we can capture.
Current behavior: We associate orders with a specific session, but do not directly associate them with an element id. This doesn't affect fulfillment or behavior, but makes it hard to measure the impact of one element over another.
Desired behavior: We add an optional element_id column to the order, and pass the element id to set when creating an order.