The "Periodic Data Filter" node operates on the contents of data tables. While the "New Data Event" node starts a session every time there's a new record in the data table, this one performs a periodic filter on the data table.
How does it work?
You can use two configuration modes: simple and advanced.
Simple Mode
Configure the node in simple mode:
- First, select the association field that links the contact to the data table. For example, for a trigger on the orders table, you would select the contacts field that connects the contact to their ordered items.
- Filter the data table elements to only consider certain records, rather than all records indiscriminately. For example, you may want today's orders for hoodies.
- Choose the data table fields you want to use within the automated flow (e.g., in conditions or content personalization elements). For each selected field, an automated flow variable will be created that contains that information.
- Configure the execution frequency of the filter in the same way and with the same parameters as you configure the "Periodic Filter" node.
Advanced Mode
The advanced mode allows for handling more complex data models. Be sure to specify the necessary fields in the query (SELECT) and the field that contains the contact; you can filter the desired records directly in the query by adding a clause such as (WHERE).
Use Cases
The fundamental difference between the more classic "Periodic Filter" node and this new "Periodic Data Filter" node is that the automated flow is started based on the data from the data tables rather than the contact data.
Order History
The data table contains the order history of an eCommerce.
Filter only the products, quantities, or contacts that interest you, and you can use all the information present in each order's individual rows to activate a repurchase flow for the same product.
Insurance policies
Insurance policies registered to a contact are stored in the data table. Activate an automated flow a few days before the expiration of each policy, and obtain the policy's data as session variables to personalize the communications sent to the contact. For example, include the policy number, the insured item, the car's license plate, and specific clauses.