Maileon icon

Maileon

Interact with Maileon API

Actions3

Send Contact Event

AI-generated

Overview

This node operation sends a contact event to the Maileon API. It is useful for tracking specific events or actions related to a contact, such as user interactions or transactions, by associating event data with the contact's email. For example, it can be used to log a purchase event or a subscription confirmation for a contact in a marketing automation workflow.

Use Case Examples

  1. Sending a 'purchase' event with details like product ID and price for a contact's email.
  2. Logging a 'webinar registration' event with custom fields for a contact.

Properties

Name Meaning
Email The email address of the contact to associate the event with.
External ID The external ID of the contact, used alternatively to email for identification.
Source The source of the contact, providing context about where the contact originated.
Permission The permission level of the contact, indicating opt-in status.
Sync Mode Specifies how to synchronize if the contact already exists (ignore or update).
Send Double Opt-In Whether to send a double opt-in email, required only when permission is set to none.
DOI Key Key required when double opt-in is enabled and permission is none.
Contact Field Mapping Mapping of contact fields to values, allowing custom and standard fields to be set for the contact.
Event Type Name or ID The type or ID of the event to send, specifying the kind of event being logged.
Event Field Mapping Mapping of event fields to values, allowing custom data to be sent with the event.

Output

JSON

  • json - The response from the Maileon API after sending the contact event, including transaction reports and status.

Dependencies

  • Maileon API with authentication credentials

Troubleshooting

  • Ensure the email or external ID is correctly provided; missing or invalid identifiers will cause errors.
  • Verify that the selected event type exists and is accessible via the API; otherwise, the event cannot be sent.
  • Check that the field mappings for contact and event fields are valid and match the expected types to avoid data casting errors.
  • If the API returns an error about queuing the transaction, verify the event data and permissions.

Links

Discussion