New Features

⚠️ Implementation of Exclusion Logic (EXCLUDE) in Segments and Automations - AdTech Standard (Meta/Google Ads)
🔴 The Current Problem (Efficiency Gap) Currently, the creation of audiences on edrone is based almost exclusively on the logic of inclusion. For a CRM Analyst seeking precision, the lack of a direct “Delete” button in the filter interface requires the creation of multiple “auxiliary” segments to arrive at a simple result. This creates visual pollution on the dashboard and an unnecessary waste of operational time. 🎯 Benchmarking (How AdTechs Operate) In the Brazilian market, CRM managers come mostly from Paid Media. Platforms such as Meta Ads and Google Ads use Boolean logic natively: Include: [People who visited the site] DELETE: [People who converted in the last 30 days] Technical Tip: Add a “Condition” selector next to each filter, allowing you to toggle between “Match” and “Does not match (Exclude)”, or a global “Add Exclusion Group” button. 💼 Business Case Example (Impact on ROI) Imagine a margin recovery campaign: I want to: Filter customers who abandoned their cart (Added to cart). Necessary Exclusion: Exclude those who purchased products from the “Outlet” category (so as not to give a coupon on top of a discount). Today at edrone: It's complex and error-prone. With the Improvement: The analyst does this in 2 clicks, guaranteeing the e-commerce profit margin. 🇧🇷 Nuance of the Brazilian Market Brazil has one of the most competitive e-commerce ecosystems in the world. Agencies like Propulse manage dozens of accounts where the agility in segmentation dictates whether the customer will have a positive ROI in the week. Facilitating this logic will attract more performance agencies to edrone.
2
·
CRM
Load More