Triggering Campaigns with BudQL

A campaign's schedule decides when it goes out - not just "now," but potentially "the moment this becomes true for a customer." That's a trigger: a BudQL condition attached to the campaign's schedule, evaluated continuously rather than checked once. It's what makes a campaign feel timely and personal rather than a generic batch send: the customer gets the message right as it becomes relevant to them - the day they cross an income threshold, or the moment they show signs of struggling with a bill - not days or weeks later.

There's no separate Triggers endpoint in Drive - a trigger is just a schedule of a different type, set the same way you'd set { "type": "when_published" } when creating or updating a campaign.

BudQL - the query language triggers are written in - is already documented in full as part of Bud's Custom Insights feature, and that's the canonical reference rather than duplicating it here:

See Custom Insights for BudQL syntax, available fields, and worked examples.