Campaign API

The Campaign API makes it easy to send a message or send an announcement to a large group of users and/or channels. You can personalize the message using templates. For small campaigns of less than 1000 users, you can directly send the campaign. If you need to maintain larger segments of users or channels that’s also supported. The potential applications of this feature are virtually limitless, yet here are some specific examples:

The Campaign API runs with administrative privileges and does not validate permissions - any valid user ID can be used as the sender_id. Be sure to implement appropriate access controls in your application code.
  • Marketing Campaigns : Send promotional messages or announcements to a targeted audience.

  • Product Updates : Inform users about new features, bug fixes, or enhancements to your product.

  • Event Reminders: Send reminders about upcoming events, webinars, or conferences to registered attendees.

  • Customer Surveys : Engage with your user base by sending out surveys or feedback forms to gather feedback.

  • Announcements : Broadcast important company news, policy changes, or updates to stakeholders.

  • Campaign Scheduling : Plan and schedule campaigns in advance to ensure timely delivery and maximize impact

Under the hood, campaigns send messages to the specified target audience and do so on behalf of a designated user ( sender ). If there are no existing channels to deliver messages to the target users, campaigns can automatically create them. Additionally, campaigns might generate more events for creating channels and sending new messages. These events can be sent as In-App messages and/or Push Notifications to the end users, and as Webhook calls to your backend server.

The Campaigns API is designed for backend-to-backend interactions and is not intended for direct use by client-side applications.

By default we have rate limits in place to ensure that campaigns don’t cause stability issues. The throughput supports sending campaigns with tens of millions of messages. Be sure to reach out to support to collaborate with our team and raise your limits.

All paid plans include 3 times the procured MAU volume in message capacity. Ex: if you have a 100,000 MAU plan you can send 300,000 campaign messages each month. If you need to send more messages than this limit reach out to our sales team

Sending a Campaign

Here’s a basic example of how to send a campaign. Note that the sender_id can be any valid user ID since the Campaign API bypasses normal permission checks.

You can send the campaign immediately or schedule it to start at a later time. You can also stop the campaign at any time.

segment_id = "<segment-id>" # segment_id is optional
# Create a dynamic user segment based on the filter provided.
# e.g., following segment will include all users created after 2020-01-01
segment = client.segment(SegmentType.USER, segment_id, {
  "name": 'New App Users Segment (optional)',
  "filter": {
    "created_at": {
      "$gte": "2020-01-01T00:00:00Z",
    }
  }
})
segment.create()

campaign_id = "<campaign-id>" # campaign_id is optional
campaign = client.campaign(campaign_id, data={
  # Users targeted by following segment will receive the message
  "segment_ids": [segment_id],
  # Alternatively, instead of segment_ids, you can also provide user_ids to send the message to specific users
  # user_ids: ["<user-id-1>", "<user-id-2>"],
  "sender_id": "<user-id-of-sender>", # mandatory
  "name": "Campaign name", # optional
  "description": "Campaign Description", # optional
  "message_template": {
    "text": "Hello {{receiver.name}}!", # mandatory, message text template
    "attachments": [], # Optional, message attachments
    "poll_id": "poll-id", # Optional, send a poll with message
    "custom": { "promotional": True }, # Optional, custom fields will be added to message object received by the receiver.
  },
  "create_channels": True, # Optional, create channel between sender and receiver if not already present
  # channel_template is required if create_channels is true
  "channel_template": {
    # mandatory, channel type
    "type": 'messaging',
    # Optional, template for channel id for channel creation
    # if not provided, channel id will be generated on server side
    "id": "{{receiver.id}}-{{sender.id}}",
    # Optional, custom fields will be added to channel object
    "custom": { "promotional": True },
    # Optional, if provided (and multi tenancy is enabled), you can limit accessibility to the channel only to a team
    "team": "kansas-city-chiefs",
    # Optional, if provided following members will be added to each of the newly created channel
    # if not provided, only sender and receiver will be added to the channel
    # You can use this to add e.g., moderator or admin to each newly created channel
    "members": ["user-id-1", "user-id-2"]
  }
})

campaign.create()

# Start sending messages to targeted users
campaign.start()

# Alternatively you can also schedule the campaign to start at a later time and stop at a specific time
campaign.start(
  scheduled_for=datetime.datetime.now() + datetime.timedelta(hours=48),
  stop_at=datetime.datetime.now() + datetime.timedelta(hours=72),
)

The campaign exposes methods to create, get, update, start, stop delete and query campaigns.

campaign.create() # create a campaign based on data passed above
campaign.get() # check the status of the campaign
campaign.update({
  "segment_ids": ["a869fc0f-2e7e-4fe0-8651-775c892c1718"],
  "sender_id": 'Updated-user-id-of-sender', # mandatory
  "name": 'Updated name (optional)',
  "message_template": {
    "text": "Updated Hello {{receiver.name}}!",
  }
}) # updates the campaign data

# You can start a campaign immediately, which will start sending messages to the users in the segment(s) immediately.
campaign.start()

# Or you can schedule a campaign to start at a later time.
campaign.start(
  # start campaign in 48 hours
  scheduled_for=datetime.datetime.now() + datetime.timedelta(hours=48), # optional, campaign will start running after this time
  # automatically stop the campaign after 72 hours
  stop_at=datetime.datetime.now() + datetime.timedelta(hours=72) # optional, campaign will stop running after this time
})

campaign.stop() # stops it
campaign.delete() # delete the campaign

filter = {
	"segments": { "$in": ["<segment-id>"] }
}
sort = [{"field":"created_at", "direction": SortOrder.DESC}]
options = {
  "limit": 25,
  "next": "<encoded_next>",
}
result = client.query_campaigns(filter, sort, options) # query campaigns
# result.get("campaigns", []) is a list of campaigns
# result.get("next", None) is a cursor for the next page of results

Creating a Campaign

Here are the supported options for creating a campaign:

nametypedescriptiondefaultoptional
idstringSpecify an ID for your campaign-
namestringThe name of the campaign-
descriptionstringThe description for the campaign-
segment_idsstringA list of segments to target. Max 25. Use either segment_ids or user_ids to target your campaign. The campaign will automatically remove duplicates if users are present in more than 1 segment.-
user_idsstringA list of user ids to target. Max 1000 users, for bigger campaigns create a user segment first. Use either user_ids or segment_ids to target your campaign.-
sender_idstringThe user id of the user that’s sending the campaign. Note: The sender_id is not checked against the permission system - any valid user ID can be used.-
message_templatestringA message template-
create_channelsbooleanIf true then channels will be created if they don’t exist yetfalse
channel_templatestringThe template to use when creating a channel-
skip_pushbooleanDo not send push notifications for events generated by this campaign, such as message.new or channel.createdfalse
skip_webhookbooleanDo not call webhooks for events generated by this campaign, such as message.new or channel.createdfalse

Note that campaigns can only be sent once. If you want to repeate the same campaign you have to create a new campaign object with the same template and segment ids.

Message Template

The message template uses Django/Jinja style variables. So you can use {{ myvariable }} to customize the message. The following fields are available:

VarIABLEDescription
SenderUser object that’s sending this campaign
ReceiverThe person receiving the message. This is only available in 1-1 channels, and not when sending to a group
ChannelThe channel the message is being sent to

So for example you could use a template like: “Hi {{ receiver.name }} welcome to the community”. Messages sent by the campaign API will automatically contain the campaign_id custom field and will have type set to regular.

{
  "text": "{{ sender.name }} says hello!",
  "custom": {
   "campaign_data": {{ custom }},
  },
  "attachments": [{
   "type": "image", "url": "https://path/to/image.jpg"
  }],
  "poll_id": "poll-id",
}

Channel Template

Here’s an example channel template. It enables the campaign API to find the right channel for a recipient and sender.

{
  "type": "messaging", // channel type is required
  "id": "{{receiver.id}}-{{sender.id}}",
  "custom": {
    // optionally add custom data to channels (only when creating)
  }
}

Querying Campaigns

You can query campaigns based on extensive set of filters and sort options

# Query campaigns with which are scheduled or in progress
filter_options = {"status": {"$in": ["scheduled", "in_progress"]}}
sort = [{"field": "created_at", "direction": SortOrder.DESC}]

# query first page
options1 = {"limit": 10}
page1 = client.query_campaigns(filter_options, sort, options1)

# query next page
options2 = {"limit": 10, "next": page1["next"]}
page2 = client.query_campaigns(filter_options, sort, options2)

Following code sample provides various examples of filters:

filter_status = { "status": { "$in": ["scheduled", "in_progress"] }}
filter_id = { id: { "$in": ["campaign_id_1", "campaign_id_2"] }}
filter_by_segments = { "segments": { "$in": ["segment_id_1", "segment_id_2"] }}
filter_by_name = { "name": { "$in": ["campaign_name_1", "campaign_name_2"] }}
filter_by_sender = { "sender_id": { "$in": ["sender_1", "sender_2"] }}
filter_by_created = { "created_at": { "$gte": "2021-01-01T00:00:00Z" }}
filter_by_updated = { "updated_at": { "$gte": "2021-01-01T00:00:00Z" }}

Segments for Campaigns

Segments enable you to target large groups of users. You can either specify a large list of user ids, channel ids, or filters that search the user database. There is no limit on how many users you can have in a segment.

User Segments

type = <SegmentType.USER | SegmentType.CHANNEL> # mandatory
id = "<segment_id>" # optional
data = {
	"filter": {
		"team": "commonteam"
	},
	"name": "segment_name",
	"description": "segment_description"
} # optional

segment = client.segment(type, id, data)

You can create, update or delete segments. You can also add users to the segment. The above approach specified a filter to query the users. Alternatively you can also manually provide a list of user ids.

segment_type = SegmentType.USER # mandatory
segment_id = "<segment_id>" # optional
data = {
	"filter": {
		#...
	}
} # optional
user_segment = client.segment(segment_type, segment_id, data)

user_segment.create()
user_segment.get()
user_segment.add_targets(user_ids) # a max of 10,000 users can be added in 1 API call
user_segment.remove_targets(user_ids) # no error if doesn't exits
user_segment.target_exists(user_Id) # checks if target exists in the segment
user_segment.query_targets(
	filter_conditions={ "target_id": {"$gte": "<user_id>"} },
	sort=[{"field": "target_id", "direction": SortOrder.DESC }],
	options={
	 "limit": 10000,
	 "next": "<encoded_next>", # or prev
	}
) # queries targets in the segment
user_segment.delete() # deletes segment

The example below shows how to create a segment with all users :

data = {
	"name": "everyone",
	"all_users": true
}
user_segment = client.segment(SegmentType.USER, data=data)
user_segment.create();

User segment supports following options as part of data :

nametypedescriptiondefaultoptional
namestringName for the segment-
descriptionstringDescription of the segment-
filterjsonFilter criteria for target users of this segmentnull
all_usersbooleanIf true, segment will target all the users of the appfalse

Channel Segments

You can also create segments of channels to target. If you target a channel the “receiver” message template variable will not be available.

# note: channel template is not required for channel segment
segmentType = SegmentType.CHANNEL
segmentId = "segmentId"
data = {
	"name": "segment_name",
	"description": "segment_description",
	"filter": {
		"team":"commonteam"
	}
}
channel_segment = client.segment(segmentType, segmentId, data)
channel_segment.create()
channel_segment.get()
channel_segment.addTargets(channel_cids)
channel_segment.removeTargets(channel_cids)
channel_segment.targetExists(channel_cid)
channel_segment.delete()

The example below shows how to create a segment which targets all the channels where sender is member of

data = {
	"name": "All my existing chats",
	"all_sender_channels": true
}
channel_segment = client.segment(SegmentType.CHANNEL, data=data)
channel_segment.create();

Channel segment supports following options as part of the data :

nametypedescriptiondefaultoptional
namestringName of the segment-
descriptionstringDescription for the segment-
filterjsonFilter criteria for target channels of this segmentnull
all_sender_channelsbooleanIf true, segment will target all the channels where sender is member offalse

Getting Segment

For getting a specified segment you may use the following code snippet:

segment = client.segment(segment_type, segment_id)
response = segment.get()

The received response will contain the segment data:

nametypedescriptiondefaultoptional
idstringID of the segment-
typestringType of the segment (“user” or “channel”)-
namestringName of the segment""
descriptionstringDescription of the segment""
filterobjectFilter criteria for target users or channels of this segmentnil
all_usersbooleanIf true, then segment targets all the users of the appfalse
all_sender_channelsbooleanIf true, then segment targets all the channels where sender is member offalse
sizeintegerNumber of the targets for this segment0
created_atstringDate when the segment was created-
updated_atstringDate when the segment was update-
deleted_atstringDate when the segment was deleted-

Please, take into account that:

  • Parameters filter, all_users and all_sender_channels are mutually exclusive.

  • The size is calculated asynchronously when either filter or all_users is set.

  • The size is calculated in place if you add targets manually using segment.addTargets(...) function

The size won’t be calculated at all if all_sender_channels is set to true. If you want the size to be calculated for the channel segment types, please provide the filter instead.

Sending a Campaign to Segments - Full example

The example below shows you how to create a segment and send a campaign to it

Create a segment for user’s in the USA

data = {
	"name": "People in the USA",
	"filter": {
		"country": "USA"
	}
}
segment = client.segment(SegmentType.USER, data=data)
segment.create()

Message the above segment

Remember that the Campaign API allows using any valid user ID as sender_id regardless of permissions. Make sure to validate in your application code that the requesting user has appropriate permissions to send campaigns on behalf of other users.
campaign = client.campaign(data={
  "segment_ids": [segment["segment"]["id"]]
  "sender_id": "user-id-of-sender", # mandatory
  "name": "Campaign name (optional)",
  "description": "Optional description",
  "message_template": {
    "text": "Hi {{ receiver.name }} I\'m {{ sender.name }}!",
  }
})
campaign.create()
campaign.start()

# Alternatively you can schedule the campaign to start at a later time.
# Also you can stop the campaign at a specific time. E.g.,
campaign.start(
  scheduled_for="2021-12-31T23:59:59Z",
  stop_at="2022-01-01T23:59:59Z"
)

Check the status of the campaign

res = campaign.get()
print(res["campaign"]["status"]) # "draft" | "scheduled" | "stopped" | "completed" | "in_progress"

Campaign status have following possible values:

  • draft - Campaign has been created but not scheduled

  • scheduled - Campaign has been scheduled

  • stopped - Campaign has been stopped manually or using stop_at option

  • completed - Campaign has succesfully completed

  • in_progress - Campaign is running at the moment

Sending campaigns is fast but not realtime. It can take several minutes for your campaign to complete sending. A campaign with 60,000 users typically takes ~1 minute to send.

Campaign Stats

The campaign API returns stats when you call campaign.get.

# campaign.get()
{
 "id": "...",
 "stats": {
  "started_at": "2021-02-01 00:00:00",
  "completed_at": "2024-23-02 00:00:00",
  "messages_sent": 1000,
  "channels_created": 10,
  "stats_progress": 0.97
 }
}

Webhooks

Your app will often want to know when a campaign API starts or stops. Your server hooks will receive an event when the campaign starts and another when the campaign is completed.

Both events include the full campaign object with its status and stats.

{
	"type": "campaign.started",
	"campaign": {
  "status": "running",
  "stats": {...},
  ...
	},
 "created_at": "2024-23-02 00:00:00"
}

{
	"type": "campaign.completed",
	"campaign": {
  "status": "completed",
  "stats": {...},
  ...
	},
 "created_at": "2024-23-02 00:00:00"
}

Updating a large Segment

client.querySegments allows you to paginate over a large segment with up to 10,000 results per page.

filter = {
	"name": "<name>"
}
sort = [{"field":"created_at", "direction": SortOrder.DESC}]
options = {
	"limit": 30,
	"next": "<encoded_next>"
}
response = client.query_segments(filter, sort, options)

The list of users is sorted by ID ASC. This means that you can easily compare it to your internal list of users in this segment, and call segment.addTargets/addTargets as needed.

Page updated Feb 20th 5:42

© Getstream.io, Inc. All Rights Reserved.