...
| Expand | ||
|---|---|---|
| ||
Profile fields, unlike event fields, override the values in the profile data. Two examples: Event with profile field A profile subscribes to the newsletter with the email address stan@email.nl. This will result in the following: Event: Data fields:
In Squeezely:
Event with event field A profile is viewing a product. This produces the following: Event: Data fields:
In Squeezely:
|
...
Profile fields are stored with the event and overwrite the existing values of the profile data. The following fields are profile fields:
...
Field label in event | Field content in event | Remarks |
|---|---|---|
orderid | Number | Reference number of order |
campaign | Text | The ID of the campaign. Is this in the url of your landing page as variable sqzl_campaign or utm_campaign? Then you can leave it out. |
source | Text | The source of the profile. Is it in the url of your landing page as variable sqzl_source or utm_source? Then you can leave it out. |
keyword | Text | |
category_id | Id of category | |
objectname | Name of category | |
timestamp | Timestamp of the event | Please note that this field is only usable for API Calls and is used for past events. Allowed formats: unix epocht timestamp or yyyy-mm-dd |
event_date | Date (yyyy-mm-dd) | Please note that this field is only usable for importing a CSV and is used for past events. |
totalvalue | Number | Overrides the total value of the purchase, otherwise it is product price x number. |
...