Database triggers

If you store derived events in your database, such as an Abandoned Cart or Refund, you can choose to run triggered marketing campaigns off of these events directly from your database.

With Database Triggers (aka DB Triggers), we can scan your database every 30 minutes to pull in and ingest new events to run event triggered flows off of. The custom properties associated with this event will be pulled in alongside the event that can be used to personalize your communications.

To use these triggers in a flow:

  1. Create a Complex Events Processor Trigger dataset.
  2. Contact your account manager to have an event triggered dataset created.
  3. Once your account manager confirms that event triggered dataset is created, continue on to configure a flow:

If you have any questions with regards to cadence, requirements, or you just simply want to get started - please reach out to your account manager.

153153

Complex Events Processor Trigger

🚧

Required fields in your Database trigger

The fields outlined in the prompt are required for Simon to process your database trigger.

SELECT
    event_timestamp,
    sd_processed_timestamp,
    event_type,
    identifier,
    identifier_type
FROM your_table
WHERE event_timestamp > {cursor_start_time} AND event_timestamp <= {cursor_end_time};

Explanation of sample query structure

Column Name

Data Type

Example

event_timestamp

timestamp (must be in epoch time)

1624637867

sd_processed_timestamp

timestamp (must be NOW() in epoch time)

1624637867

event_type

string

add_to_cart

identifier

string

[email protected]

identifier_type

string

'email'

❗️

Accepted Identifiers

We currently only accept 'email' as identifier_type or 'user_id' as identifier_type for DB triggers


Did this page help you?