The current state of the timeline event.

Constructors

Properties

createdAt?: Date
domain?: string

The event domain (often paired with utk).

email?: string

The email address used for contact-specific events. This can be used to identify existing contacts, create new ones, or change the email for an existing contact (if paired with the objectId).

eventTemplateId: string

The event template ID.

extraData?: any

Additional event-specific data that can be interpreted by the template's markdown.

id: string

Identifier for the event. This should be unique to the app and event template. If you use the same ID for different CRM objects, the last to be processed will win and the first will not have a record. You can also use {{uuid}} anywhere in the ID to generate a unique string, guaranteeing uniqueness.

objectId?: string

The CRM object identifier. This is required for every event other than contacts (where utk or email can be used).

objectType: string

The ObjectType associated with the EventTemplate.

timelineIFrame?: TimelineEventIFrame
timestamp?: Date

The time the event occurred. If not passed in, the curren time will be assumed. This is used to determine where an event is shown on a CRM object's timeline.

tokens: {
    [key: string]: string;
}

A collection of token keys and values associated with the template tokens.

utk?: string

Use the utk parameter to associate an event with a contact by usertoken. This is recommended if you don't know a user's email, but have an identifying user token in your cookie.

attributeTypeMap: {
    baseName: string;
    format: string;
    name: string;
    type: string;
}[] = ...
discriminator: undefined | string = undefined

Methods

  • Returns {
        baseName: string;
        format: string;
        name: string;
        type: string;
    }[]

MMNEPVFCICPMFPCPTTAAATR