You’re offline. This is a read only version of the page.
20
Hello,
I want to know what the possibilities are of the query editor in a segment. We have very eager database marketeers who wants to build more complex queries.
So does it provide for more advanced users possibilities then the designer? if yes, what are supported query languages? Or is it just a textual representation of the designer and it doesn't provide more then the designer does..
Hello,
the textual representation in the Query Language for segmentation is really the master and the UI is a graphical way to build and visualize queries in that language.
The language is based on the Customer Insights query language. But the marketing application processes the query and finds the result from the marketing data, which is a both the data from CRM configured to be available to customer insights and all the interaction data which the marketing app gathers.
When we extend the query capabilities - like multi select option set fields for spring release and soon also filtering on lookup attributes, then we extend as needed as well the query syntax. So you can assume that the capabilities in the UI and in the query language are more or less on the same level.
It may be that certain backend capabilities develop a bit faster than what is available on the UI, but you should not count on dramatically more advanced query capabilities that the query language offers and that are not available in the UI.
If you like to reach out with your query requirements which you do not see covered today, I am happy to take them back into future enhancement planning.
Share
Report
All responses (
Answers (
