Page Comparison

• Go to Data and scroll to 'Events':

Image Modified

• Click on Purchase

❓ Is the event not listed in the overview? ➡ Check the implementation

❓ Why aren't there any additional fields in the event? ➡ Add additional fields to the implementation of the event

❓ Why aren't there any consent fields in the backend event? ➡ In the events no consent fields are shown which are received via the backend API. When you want to validate the forwarding of the consent fields it's recommended to send a backend event to a profile without consent and then check in the profile aPI if the consent fields have been changed.

• Go to: https://squeezely.tech/data/audience/new

• Click on custom

• Set the following rules:

  • Events = purchase

  • Name = Test backend purchase

  • Retention = 1

• Save the audience and wait until the status is 'Live

• Go to Audiences

• Click on 'Inspect

Image Modified

• Click on an event ID

Image Modified

• Check the following fields in the event:

  • Created at: is this a time after the implementation of the API Call? If not select another event ID.

  • Api inserted & api verified: does one of these fields contain 'yes'? Then the event has been implemented correctly. If not, check the implementation.

Image Modified

Please note that the frontend and backend purchase are merged based on the order id. When you only send a backend purchase the consent fields are not visible in the event. A change in the consent can be checked in the profile of the event.

Because of the following situations, both the front-end and backend purchase are recommended:

• The frontend purchase is not always triggered because the thank you page is not loaded

• Some Adblockers do not accept cookies and therefore do not send frontend events to Squeezely

In the example below the advantage of sending both is shown: