As the payment/login view can be very different between costumes and modular apps, any standard tracking would be very limited or not posible. Therefore we recommend setting up an Action event that will capture eCommerce data.
To see more general info on the options for the action event see here: Action event documentation.
The general recommendation would be to have an event fire when a user leaves a payment view. That could include these parameters:
- The item id of the purchase
- The date of purchase
- The duration of the purchase, e.g. 3 months subscription.
- The price
- The currency used to pay
- If the purchase was a success or failure. If the user opens and closes the payment page and closes it again, that would result in a failure, making it posible to calculate a drop of rate.
The Action event can also sent the parameters gotten from the newest standard event of a given type or a previous Action event that picked it up. E.g. the last vl_event_module_interaction event had "AvailableIssuexxxxxxxxxe-epapertitlexxxxx" as the ID, which would be the item clicked on to show the payment page.
User parameters can also be added to a user after purchase if desired, e.g vl_value_subscription_type : item id.
Comments