How to Use Audience Packages to Target Release Populations

I. Use Cases

The audience package feature supports delivering tasks to users with specified identifiers. You can select audience package rules in conditions and choose created audience packages. The correspondence between identifiers and SDK fields is as follows:

• Configuration SDK: guid passed during SDK initialization
• Resource SDK: ResHubParam.qimei passed during SDK initialization
• Gray Release Upgrade SDK: identifier set via setUserIdentifier

Large audience packages are currently supported, handling tens of millions of identifiers.

II. How to Use

2.1 Create an Audience Package

On the [Global Features & Settings] - [Conditions & Audience Packages] - [Audience Packages] page, click New Audience Package to create one. Audience packages support two creation methods: Manual input: Separate different identifiers with English commas File upload: Supports txt files only; each line represents one identifier

2.2 Edit an Audience Package

After creating an audience package, if no tasks reference it, you can modify the package.

If an audience package is already in use, it can still be modified, but editing the package will update all historical tasks using this audience package, potentially expanding the delivery scope of all historical tasks.

If you do not want to affect historical tasks, create a new audience package for use in new tasks.

2.3 Download an Audience Package

Created audience packages can be downloaded as txt files.

2.4 Use an Audience Package

In delivery conditions, select "User Audience Package" and choose a created audience package to deliver tasks to users in that package. You can also use the "not in" rule to exclude users in a specified audience package from receiving the task.