-
Relational Table Interface Revamp
I think everyone who uses relational tables know what I'm talking about when I say that we need a revamp to allow more functionality via the UI. Here are some of the updates I'd love to see that will make this relational tables easier to use: * Ad...4 Future consideration
-
Autocomplete in Queries
It would be great if after typing a couple of characters a list of the top 10 closest values from the DB, Behavioural Data or RT were shown to be selected via mouse click or keyboard shortcuts in order to make the Query creation more efficient and...0 Future consideration
-
Allow use of wildcards in "has viewed web page" behavior query URLs
It would be really helpful to be able to use wildcards i.e. mywebsite.com/category/* would return results for anyone who visited a URL that stared with that string and then had anything in place of the *3 Future consideration
-
Ability to delete fields without having to delete sent mailings/queries
At the moment if you want to delete a field you need to delete all sent mailings, contact lists and queries that reference that field. This makes it near impossible to do. It would be great if you could delete a field without this dependency.1 Future consideration
-
Modify and copy Relational Tables
The feature to change the name of Relational Tables, to add columns and to copy the Relational Tables for reuse.With the current implementation of WCA, users have to recreate the Relational Table and import for such purposes.0 Future consideration
-
query "link name contains” or "template name contains" for queries or scoring models
instead of adding each individual link from each individual mailing template, allowing a query to search the link name would allow to query on types of links (provided you named your links with this in mind) -
Random Sample in Queries
having the possibility to restrict a query result to a sample of rows. For example my query gives me 10000 people and I just need to send 1000 emails (because of my number of coupons or for winners of a game). It could be great if I can restrict t...0 Future consideration
-
Query that can reference several databases, instead of just one
Currently: A query can only reference one database. ex: If i want to send to subscribers in our main database, but also import a custom list of a few people, I have to do this all as separate databases & query. Proposing: It would be more effi...0 Future consideration
-
Dynamic Content Based on Child Relational Tables
Currently there is no way to trigger Dynamic Content based on product specific purchases in Child Relational Tables. We need to create a different email template for every scenario, which is inefficient and - based on the number of possible produc...0 Future consideration
-
Web forms for Relational Tables
Allowing web forms on landing pages to populate data into relational tables would allow for much better data management. Personal information could easily be maintained in the main database and additional information could be enetered into a conne...2 Future consideration