Slot personalized
Learn how to track content served in a slot.
This event tracks which content is served in a slot for a specific user. The delivered content can be fully personalized, part of an experiment or test, or the default static fallback.
The SDK automatically tracks this event when the application fetches content for a slot.
Input properties
This event has no input properties.
Processed properties
These properties are automatically tracked:
- personalizationobject
The available information about the slot.
- slotIdstring
The ID that uniquely identifies the slot.
- slotVersionobject
The assigned version of the slot.
- majorVersionnumber
The major version.
- minorVersionnumber
The minor version.
- majorVersion
- contentIdstring
The ID that uniquely identifies the content.
- experienceId(optional)string
The ID that uniquely identifies the experience.
- audienceId(optional)string
The ID that uniquely identifies the audience.
- assignedVariant(optional)object
The assigned variation of the experiment.
- experimentIdnumber
The ID that uniquely identifies the experiment.
- variantIdnumber
The ID that uniquely identifies the variant.
- experimentId
- slotId
Payload examples
Below are some payload examples for this event:
{ "type": "slotPersonalized", "personalization": { "slotId": "91fccc5b-5661-4ba1-9cec-b8e141c3e13a", "slotVersion": { "majorVersion": 1, "minorVersion": 0 }, "contentId": "e2480d68-b5d1-4d17-b0e4-e5c2e3ded6c2", "experienceId": "e25b205d-0aaa-4db5-9d75-2fa4e3a7e1e7", "audienceId": "77e4bda3-2b25-430a-9d87-5bbb9ff90bb1", "assignedVariant": { "experimentId": "e3e8db14-f4fb-427f-a4a3-cfd763397a83", "variantId": "a0caab39-c71c-4327-85e9-a890fdff9e0c" } }}