About query editor
The query editor is a wizard that allows you to filter data contained in the Adobe Campaign database.
This feature lets you build a population to better target your recipients thanks to the predefined filters and rules.
Several application functionalities use it in order to:
- Define populations inworkflowactivities
Query editor interface
The query editor is made up of a
The palette, located on the left-hand side of the editor, is divided into two tabs, which contain elements divided into thematic blocks. These tabs are:
- TheShortcuts, available by default, or created by the instance administrator. Here you will find fields, nodes, groupings, 1-1 links, 1-N links and other predefined filters.
- TheExplorerwhich allows you to access all available fields in the target resource: nodes, grouping elements, links (1-1 and 1-N).
The elements contained in the tabs must be moved into the workspace in order to be configured and taken into account for the query. Depending on the targeting dimension selected (see Targeting dimensions and resources ), you can:
- Select audiences or profiles one by one
- Use predefined filters
- Define simple rules for fields of your choice
- Define advanced rules that allow you to apply functions to certain fields
The workspace is the central zone in which you can configure and combine rules, audiences, and predefined filters added from the palette.
When you move an element from the palette into the workspace, a new window opens and you can start Creating queries .
The query editor can be used to define an audience or test profile in a message, a population in a workflow and to create a query type audience.
Queries can be defined in the
Audiencewindow while creating a delivery or in a
Queryactivity while creating a workflow.
- Move an element from the palette into the workspace. The window for editing the rule opens.
- For a string or numericalfield, specify the comparison operator and the value.
- For a date or date and timefield, you can choose to define a specific date, a range between two dates, or a period relative to the query's execution date.
- For a Booleanfield, check the boxes linked to the possible values for the field.
- For agroupingfield, select the grouping field on which you want to create the rule, then define the condition in the same way as for the other fields.
- For a1-1link with another database resource, select a value directly from the table targeted.
- For a1-Nlink with another database resource, you can define a sub-query on the fields of this second resource.You do not need to specify a sub-condition.For example, you can only select theExistsoperator on the profile tracking logs and approve the rule. The rule will return all of the profiles for which tracking logs exist.
- For apredefined filter, enter or select the elements you like according to the criteria offered.Administrators can create filters to facilitate complex and repetitive queries. These will appear in the query editor in the form of pre-configured rules and they limit the number of steps needed to be carried out by the user.
- You can specify a name for your rule. This is then displayed as the rule name in the workspace. If the rule is not given a name, an automatic description of the conditions is displayed.
- To combine the workspace elements, interlock them into one another to create different groups and/or group levels. You can then select a logical operator to combine elements on the same level:
- AND: an intersection of two criteria. Only the elements matching each criterion are taken into account.
- OR: a union of two criteria. Elements matching at least one of the two criteria are taken into account.
- EXCEPT: exclusion criteria. Elements matching the first criterion are taken into account unless they also match the second criterion.
- You can now calculate and preview the number of elements targeted by your query using the and buttons from the action bar.
If you would like to modify an element of the query, click on the edit icon. The rule is opened as it was previously configured and you can then carry out any necessary adjustments.
Your queries are now created and defined, this allows you to build a population to better personalize your deliveries.