How do I create a complex `devices_filter` for the `createTargetedMessage` API to target users within an Application Group based on multiple app-specific tags?

When using the /createTargetedMessage API call, you might need to create complex filters (devices_filter) that target users within a specific Application Group based on tags that are set individually for each application (app-specific tags).

To achieve this, you need to construct the devices_filter string using specific functions and operators:

1. Specify Applications: Use the A("APP_CODE") function for each application within your target Application Group. Combine these using the + operator (logical OR).
2. Specify App-Specific Tags: Use the AT("APP_CODE", "TAG_NAME", OPERATOR, VALUE) function to target devices based on a tag set within a specific application.
   • APP_CODE: The code of the specific application.
   • TAG_NAME: The name of the app-specific tag (e.g., "AccountID", "NotificationCategories").
   • OPERATOR: The comparison operator (e.g., IN, NOTIN, EQ, NOTSET). Make sure to use the correct operator for the tag type (e.g., IN or NOTIN for List tags, EQ for String/Integer tags). NOTSET checks if the tag has never been set for the device in that specific app.
   • VALUE: The value to compare against. For IN/NOTIN, this should be an array (e.g., ["value1"]). For NOTSET, a value is not typically needed or used in the same way, check documentation for exact syntax per operator.
3. Combine Conditions:
   • Use the * operator (logical AND) to combine different tag conditions.
   • Use the + operator (logical OR) to combine alternative conditions for the same tag (like checking if a tag is IN a list OR NOTSET) or to combine checks across different apps.
   • Use parentheses () to group conditions correctly.

Important: You must explicitly list the conditions for each application within the group when dealing with app-specific tags. You cannot simply reference the Application Group code within the tag condition itself.

Example Structure:

Let's say you have an Application Group containing APP_CODE_1, APP_CODE_2, and APP_CODE_3. You want to target users where:

• The app-specific List tag AccountID contains "user_account_value"
• AND the app-specific List tag NotificationCategories either does NOT contain "category_to_exclude" OR the NotificationCategories tag is NOTSET.

The devices_filter would look like this:

"devices_filter": "(A(\"APP_CODE_1\") + A(\"APP_CODE_2\") + A(\"APP_CODE_3\")) * (AT(\"APP_CODE_1\", \"AccountID\", IN, [\"user_account_value\"]) + AT(\"APP_CODE_2\", \"AccountID\", IN, [\"user_account_value\"]) + AT(\"APP_CODE_3\", \"AccountID\", IN, [\"user_account_value\"])) * ((AT(\"APP_CODE_1\", \"NotificationCategories\", NOTIN, [\"category_to_exclude\"]) + AT(\"APP_CODE_1\", \"NotificationCategories\", NOTSET)) * (AT(\"APP_CODE_2\", \"NotificationCategories\", NOTIN, [\"category_to_exclude\"]) + AT(\"APP_CODE_2\", \"NotificationCategories\", NOTSET)) * (AT(\"APP_CODE_3\", \"NotificationCategories\", NOTIN, [\"category_to_exclude\"]) + AT(\"APP_CODE_3\", \"NotificationCategories\", NOTSET)))"

Explanation of the example:

1. (A(\"APP_CODE_1\") + A(\"APP_CODE_2\") + A(\"APP_CODE_3\")): Targets devices in any of the three apps.
2. *: AND condition.
3. (AT(...) + AT(...) + AT(...)): Checks if AccountID matches in any of the apps (OR logic between apps for the same condition).
4. *: AND condition.
5. ((AT(...) + AT(...)) * (AT(...) + AT(...)) * (AT(...) + AT(...))): This part is slightly complex. It ensures the NotificationCategories condition (NOTIN the excluded category OR NOTSET) is met within the same app where the AccountID matched. The outer * operators here effectively act like an AND across the apps for this combined condition check, ensuring the device meets the criteria within at least one app context fully.

Remember to replace placeholders like APP_CODE_1, TAG_NAME, OPERATOR, and VALUE with your actual application codes, tag names, desired operators, and values. Ensure proper escaping of quotes (\") if the filter string is part of a JSON payload.