- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
This doesn't seem like a segment to me. I think an evar would be more appropriate.
When you say you want to see how quickly customers make an order, do you mean how long it takes them to go from the shopping cart to an order confirmation page?
Whenever the user begins to make an order, you could set a data element with a time stamp, and have this data element persist for a visit. Then on the order confirmation page you could have a page load rule that calculates the difference between the current time and the data element, and put this value in an evar.
You'll have discrete values for the time it takes to complete an order. If you have less than 500,000 orders a month this would be fine and you can classify it. If you have more order volume, I would consider bucketing the order speed in the JS of the page load rule on the confirmation page before putting into the evar.