How to use SecuTix Query Engine?

SecuTix Query Engine

SecuTix comprises an engine for the creation of queries called "SecuTixQuery Engine".

These are some explanations and examples that will help you master your contact base and your segmentation.

A: The beginning of the query

The query engine enables you to construct a query as naturally as if you were constructing a sentence. The beginning of your sentence is always the same: "Select the records where all the following conditions apply".

You can choose between 4 different possibilities depending on what you want to do:

All (+ / and): enables to add contacts to the list and to link conditions with an and
At least one (+ / or): enables to add contacts to the list and to link the conditions with an or
At least not one (- / or): allows the exclusion of contacts to the list and to link the conditions with an or
No (- / and): enables to exclude contacts from the list and to link conditions with an and

The modification of this block thus allows you to create queries with the operator OR and/or "negative" operators. In other words:

Link conditions with:

and

Link conditions with:

or

Add contacts

(+)

All

(+ / and)

At least one

(+ / or)

Exclude contacts

(-)

No

(- / and)

At least not one

(- / or)

B: The list of conditions

Here, you will be able to determine the conditions of your query. The component "Add new condition" allows you to add one condition in a click.

C: Add/handle the conditions of a query

These four buttons will allow you to:

+ Add a new condition / sub-conditions
{+} Add a sub query
O Momentarily deactivate a condition
x Delete a condition

D: Execute the query and view the resulting volume

A simple click on "Search" allows you to see the volume of contacts that meet the conditions laid down and to gain access to the sample of some contacts.

Most used queries

The "SecuTixQuery Engine" has a notable innovation, when you click on "Add new condition", you can choose in the first instance among the most used queries in SecuTix.

You can also simply construct your conditions on all other data made available. Let's take a closer look at these different possibilities with some examples.

The "Predefined" entry contains the list of the conditions mostly used by SecuTix customers.

This is a description that explains in more detail the meaning of each of these predefined conditions.

Contact has not printed print@home ticket for - contacts who have not printed their print@home ticket for the event X

Contact is a member of - contacts being subscribers of the X organization (the indicator Member shows yes for the organization X).

Contact is season ticket holder of - contacts who are subscribers of the organization X (The Subscriber indicator is yes for the organization X)

Contact used advantage - contacts who have used the advantage X and who have not been reimbursed.

Contact didn't use advantage - contacts who have not used the advantage X (buyers contacts that have been subsequently reimbursed are excluded from the result).

Contact has bought more than - contacts having bought for an amount exceeding X over all seasons.

Contact has bought less than - contacts having bought for an amount lower than X over all seasons.

Contact has paid for product - contacts having paid for the product X (buyer contact/financial history).

Contact is in static target - contacts being members of the static target X.

Entities

The SecuTixQuery Engine enables you to combine these conditions together. Let's now take a closer look at the available data/entities to create your queries.

For each entity below, you will find a typical example of use. We have selected the most interesting data for you to provide an intuitive and natural experience in the creation of your queries.

Individual / Structure

The main Information of your contact forms are available here, that is, the email, the anniversary date, the source sales channel or the presence of a login. You have general information for the creation of your targets.

In the same way, when you choose to create a structure target, you will have the structure entity here to construct your query.

The example to the right presents a query combining several operators and several fields of the individual entity. This query