Hello community!!
We have a project casuistry that we would like to discuss:
On the Smart List, we want to filter through the clients that have not acquired a certain product in order to impact them.
Our actual catalogue has over 8,500 products and as we are aware of how ardous it would be to create 8,500 fields related to each product, we though on:
Creating around 50 to 100 fields per client that would be filled with the products that each client has (we reckon that a client acquires maximum 50 to 100 products).
However, each time we create a smart list we want to avoid creating 50-100 filters through which we would "ask for" clients that haven't acquired a certain product.
That's why our question is if there is any way of creating a "master" filter in which we could ask just once for those clients who haven't acquired a certain product and then this filter could check the info with the 50-100 "subfilters".
Eventually the question is: is there any main filter that can gather subfilters?
An answer anyone?
Hi Nerea Eguia ,
- Option A - You can create 1 master smart list with all the 50-100 filters (one time effort) and reference this smart list in other "smart list" and "Smart campaigns". That way, creating the master filter\smart list would be a one time task. And any time you want to use this master filter, you can use it as shown below.
Also, you can go through the documentation on Saved Smart List Rules in marketo sky. It is again a great way to create a smart list rule (One time effort) and re-use that where ever necessary.
Best Always,
Karan Hari
Thank you for your answer Karan
In those fields we want to ask if none of them is equal to a value that we will insert. For instance if none of those fields is equal to credit cards.
With the very valuable answer you are giving me however, we believe that we need to change the value of those 50-100 fields everytime we want to ask for a different product.
Is there anyway of avoiding this and inserting the value we are asking for one single time instead of 50-100 times?
Thank you!