Pages

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 14.7

...

  • Page code (meaning directly from your the site source code)
  • Shared code

...

Testing transaction tracking

To For instructions on how to test that transactions are correctly tracked with the data layer:

...

Select Advanced > Events.

Testing transaction trackingImage Removed

Go to a page where transactions are tracked. If transaction events are successfully triggered with the data layer, Frosmo Preview shows the following messages for each event:

  • conversion (contains the transaction data parsed from the transaction object)
  • product.purchase (contains the ID and price for a single purchased product item)
  • dataLayer (contains the object passed to the data layer)
  • trigger.event (contains information about the triggered event, including the object passed to the data layer)

Testing transaction trackingImage Removed

Info

Transaction events log a dedicated product.purchase message for each individual purchased item. For example:

  • If a transaction contains three copies of one product, the transaction event logs three product.purchase messages.
  • If a transaction contains three copies of one product and two copies of another product, the transaction event logs five product.purchase messages.

...

To verify that the correct transaction data was sent, check the conversion message.

Testing transaction trackingImage Removed

If you want more details on a data layer call, select the Advanced > Requests view in Frosmo Preview, and check the transaction request to the Optimizer API.

...

on a site, see Testing data tracking.