Batch update

A batch update lets you apply data to a group of up to 1000 people matching your criteria. For each person your batch update matches, you can update attributes or send events (to trigger a message campaign, for example).

How it works

You can perform a batch update in any campaign, but you’re most likely to use it in a webhook-triggered campaign, which starts with arbitrary data from an incoming webhook. This data isn’t associated with anybody, and it can take any shape. A batch update lets you associate this data with one or more people—either as attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. Attributes are analogous to traits in Data Pipelines. or eventsSomething that a person in your workspace did. Events can trigger campaigns, add people to segments, etc. You can access event properties in liquid with {{event.<property>}}.

For example, if you support multiple users in a single account, you might send a campaign that triggers (via webhook) when an account state changes—it’s cancelled, or upgraded. In your webhook-triggered campaign, you can use a batch update to set attributes for everybody belonging to the account, so that you can reflect their account’s status at an individual level. You can also trigger campaigns based on the account status change, sending a message to everybody involved with the account! This process makes it easy to message or update a group of people based on a single piece of incoming data—a true one-to-many interaction.

flowchart LR a[incoming webhook]-->g subgraph g [Webhook-Triggered campaign] direction LR c[batch update] c-.->|send event or
update attributes|d[matching person 1] c-.->|send event or
update attributes|e[matching person 2] c-.->|send event or
update attributes|f[matching person n] end

 You can perform multiple batch updates

In a single batch update action, you can update attributes or send events, but you can’t do both. If you want to update attributes and send events, you can add two batch updates to your workflow

Set up a batch update

If you’re using a batch update in a webhook-triggered campaign, you may want to send a test webhook before you begin. We’ll display your incoming test webhook in your batch update, to help you understand the data that you can use in your batch update.

  1. In the workflow step of your campaign, drag Batch Update into your workflow.
  2. Give the batch update a Name and click Add Details.
  3. Select whether you want to Update profile attributes or Send an event.
  4. Set criteria for the people you want to update.

    You can set multiple conditions for people you want to match. These conditions are ANDed together, meaning that a person has to match all of your conditions to be included in the update.

     Your criteria must match fewer than 1000 people

    If your batch criteria ever matches more than 1000 people, the batch update will not run.

  5. Set your attributes or event data. You can use liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}. to set attributes or event properties.
  6. Click Save.

Update attributes

When you use the Update profile attributes option, your batch update sets or updates attributes for every person matching your conditions. You can trigger campaigns or segment membership based on your attributes.

You can use liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}. to set properties from your incoming webhook—the trigger—as attributes.

set attributes for multiple people with a batch update
set attributes for multiple people with a batch update

Send events

When you use the Send an event option, your batch update sends an event to every person matching your conditions.

You can use liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}. to set properties from your incoming webhook—the trigger—as attributes.

send events to multiple people with a batch update
send events to multiple people with a batch update

Matching people in your batch update

When you perform a batch update, you set criteria matching the group of people you want to update. It’s like setting up a segmentA segment is a group of people in your audience that you want to target with campaigns, messages, etc. You can join groups of people manually, or by attribues and event data., but you can only match on attributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. Attributes are analogous to traits in Data Pipelines. conditions. You can set multiple conditions for people you want to match. These conditions are ANDed together, meaning that a person has to match all of your conditions to be included in the update.

A batch update is limited to 1000 people. Anytime your batch update criteria matches more than 1000 profiles, we won’t run the update—we’ll skip it, report the Failed Action in your activity log, and your workflow will continue. When you set up a your batch update, we’ll warn you if your criteria matches more than 1000 profiles, but you should monitor your audience to make sure that your batches don’t exceed the limit when your campaign is live.

set criteria for the people you want to update
set criteria for the people you want to update
Copied to clipboard!
  Contents
Is this page helpful?