...
In backend custom events the following fields will be sent along as a minimum:
Field label | Field content |
|---|---|
event | the name of the event |
Email address of the profile |
In the following circumstances more fields are required:
Are multiple languages used? → Then also include language in the product array
Are multiple currencies used? → also add currency to the event
Extra
In this event extra data fields from the database can be sent. Maybe there are fields added to the event in the Data Plan /wiki/spaces/SG/pages/1272807432, which are needed to set up use cases
| Expand | ||
|---|---|---|
| ||
An overview of the data fields you can send in the event, can be found here: Data fields |
| Expand | ||
|---|---|---|
| ||
First you need to create the custom data fields in Squeezely Creating custom data fields Next you can send these with the field label: custom_(name of the field). For example, in the case of the custom data field custom_province, custom_province must be sent along. |
...
The following response is incorrect:
...
| Expand | ||
|---|---|---|
| ||
|
...
Go to: https: //squeezely.tech/data/audience/new
Click on custom
Set the following rules:
Events = (the name of the custom event)
Name = Test backend custom event
Retention = 1
Save the audience and wait until the status is 'Live
Go to Audiences
Click on 'Inspect
...
Click on an event ID
...
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.
...