Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

On ticket shop, when exposing sale data to datalayer, also pushing reservation amount to datalayer when configured.


Problem

With our current way of exposing data to datalayer on Ticket Shop, only sale order are exposed.

In some business cases, for example prepayment, when contact chooses payment method prepayment for their ticket (which they will pay it later), a reservation order will be created for this kind of payment. Therefore, the amount of the order is not push to datalayer, and the report at Google Analytic is not accurate.

Solution

Introduce a new key at Point Of Sale configuration, and expose the reservation amount to datalayer when the new key is turned on.

Getting started




A new key (config.datalayer.alsoPushReservationAmount) is introduced  for each point of sales that allowing the operator to decide if the reservation amount should also be sent to datalayer.



And on the corresponding ticket shop, when the key is turned on, the reservation amount is push to datalayer at the confirmation page.




  • No labels