Segments

An audience decides who gets a push. Push and in-app cards use the same audiences.

Built-in audiences#

Every app has four:

The first three also appear as saved segments in Segments and in the push composer. Test devices is not a saved segment. In the push composer, send to test devices from the Test devices window. An in-app card and the REST API can name it as an audience.

A push goes only to subscribed installs, whichever audience you pick.

Saved segments#

In Segments, a saved segment starts from Subscribed, Opened in the last 7 days or Not opened for 30 days, and adds filters one row at a time:

• Language, from the device language setting
• Country, from the device region setting
• App version
• Tag, one key and value on the person. See Tags.
• Spend in a window: the last 24 hours, the last 7 days, the last 30 days, or all time. Inside the window, pick people who spent, people who did not, or people who spent at least an amount in one currency. Currencies are not converted.
• Sessions in the same windows: at least a number of sessions, at least a number of minutes, or both.

The segment editor shows how many installs match before you save. A saved segment can be renamed, changed or deleted.

See Purchases and sessions for how spend and sessions are counted.

Using a segment#

• In the dashboard, choose the audience when you write a push.
• From the REST API, name one segment in included_segments, either a built-in name or the name of a saved segment. See Targeting.

How many devices one send reaches#

A push sent now or at a set time goes to every subscribed install in the audience. A push sent At the same local time goes to the whole audience of each time zone, sent in the background when the clock in that time zone reaches the chosen time. A device with no time zone is not sent to, and it is not counted as skipped. The push composer shows how many devices the chosen segment matches.

From the REST API, one segment or tag send reaches at most 1,000,000 devices. See Targeting.