Configuring the Engagement Marketing Platform

The following describes the data and events that are used in Contacthub, which are available to Contactsend and Contactplan.


Contacthub Contactsend Contactplan
profile (header) 1 YES YES
profile base 2 Partially Partially
profile extended 3 Partially Partially


1 Integrated attributes: externalD, nodeId, enabled, Id, tags-auto, tags-manual, registratedAt, updatedAt. The tags-auto and tags-manual attributes are processed as a string with the values divided by pipes (|).
2 Unavailable fields: contacts.otherContacts, contacts.mobileDevice, educations, likes, jobs, subscriptions.
3 Attributes defined as object arrays are not available.


  • Campaign – Email events from external sources
Contacthub Contactsend Contactplan
campaignBlacklisted NO NO
campaignBounced NO NO
campaignLinkClicked NO NO
campaignMarkedSpam NO NO
campaignOpened NO NO
campaignSend NO NO
campaignSubscribed NO NO
campaignUnsubscribed NO NO


Email campaign events that take place in Contactsend are natively available in Contactplan, and for selected companies in Contacthub.

  • E-commerce
Contacthub Contactsend Contactplan
abandonedCart NO YES
addedCompare NO YES
addedProduct NO YES
addedWishList NO YES
orderShipped NO YES
removedCompare NO YES
removedWishlist NO YES
removedProduct NO YES
viewedProduct NO YES
viewedProductCategory NO YES
reviewProduct NO YES
  • Classifications attribute objects (array objects) are exported. You can synchronize up to 15 categories (ten text and five data classifications). When synchronizing between Contacthub and Contactplan, the key for the categories to export must be defined. If the categories are not in the order line, Contacthub exports a null field.
  • Category attribute values (array strings) are exported as unique value strings, separated by pipes (|). Categories in Contacthub are a list of values. The other platform applications do not support lists of values. For this reason, Contacthub synchronizes with the other applications by adapting the list of values to a unique field, separating the values with pipes (|). For example, in Contacthub, the propriety “category”: [«Woman”, “Bags for women”, “Bags”] is synchronized in Contactplan in this way: «Woman|Bags for women|Bags”.


  • Event Extra Proprieties
Contacthub Contactsend Contactplan
extra properties NO NO


All event Extra Properties exist as a free data container, where you can insert free-form, non-predefined information. This is useful when saving all the extra information that can be read from every device through the API, based on the data contained in Contacthub. Because of its non-predefined nature, without structural limits, all the information inserted in this property are not synchronized and, as a result, cannot be used in the other Engagement Marketing platform applications. The data contained in this property can only be used in Contacthub for storage and automations (for example, values that are to be passed as the dynamic text in an email, or as customer tagging). The data is not available in Contactsend or Contactplan.

  • Generic Event
Contacthub Contactsend Contactplan
genericActiveEvent NO NO
genericPassiveEvent NO NO
  • Purchase
Contacthub Contactsend Contactplan
completedOrder NO YES
  • Retail
Contacthub Contactsend Contactplan
eventEligible NO YES
eventConfirmed NO YES
eventDeclined NO YES
eventNoShow NO YES
eventInvited NO YES
eventNotInvited NO YES
eventPartecipated NO YES
  • Subscription
Contacthub Contactsend Contactplan
serviceSubscribed NO NO
serviceUnsubscribed NO NO
  • Ticket
Contacthub Contactsend Contactplan
repliedTicket NO NO
closedTicket NO NO
openedTIcket NO NO
  • Web Browsing
Contacthub Contactsend Contactplan
repliedTicket NO NO
closedTicket NO NO
openedTIcket NO NO
repliedTicket NO NO
closedTicket NO NO
openedTIcket NO NO
  • Other
Contacthub Contactsend Contactplan
changedSetting NO NO