How can I get Clay to segment my list based on account location and group it into 3 new tables all with the same data as the original table apart from location split into US, EU or Middle East?
To segment your list based on account location into three new tables, you can use our "write to table" feature. Here's how: 1. Create three new tables in your workspace for US, EU, and Middle East. 2. Use the "write to table" feature for each new table: • Select your Clay account • Choose the destination table (US, EU, or Middle East) • Map the columns from your original table to the new table • Set a condition in the "Only run if" setting to filter by location 3. Repeat this process for each new table, adjusting the location condition each time. This will create three new tables with the same data as the original, segmented by location.
What if i have a contact location that is outside the US, EU or Middle East? Can I set a rule that says if the location is NOT US, EU or Middle East to put it into the one closest in terms of timezone?
Unfortunately, Clay doesn't have a built-in feature to automatically assign contacts to tables based on timezone proximity. However, we can use the "write to table" feature to achieve a similar result. Here's a workaround: 1. Create four tables: US, EU, Middle East, and Other. 2. Use the "write to table" feature for each table. 3. For the US, EU, and Middle East tables, set conditions to filter by their respective locations. 4. For the "Other" table, set a condition that excludes US, EU, and Middle East locations. 5. In the "Other" table, include the "Contact Time Zone" data point. You can then manually review the "Other" table and reassign contacts to the closest region based on their time zone. To improve this process, would you like to know about any specific data points or integrations that might help with location-based segmentation?
Does Clay know which countries are in the middle east? do I have to write out every country in the middle east or is it enough to say just middle east and united arab emirates would meet that requirement? And for the "contact timezone" - how do I add that in? Does Clay come up with that based on the contact location?
Clay doesn't automatically recognize countries in the Middle East as a group. You'll need to list each country individually when setting up your "write to table" feature. For the "Contact Time Zone" data point, Clay can provide this information, but it doesn't automatically determine it based on location. You'll need to add it as a separate data point when setting up your table. To add the "Contact Time Zone" data point: 1. Use the "write to table" feature 2. Select your data source (e.g., Apollo.io) 3. Choose "Contact Time Zone" from the available data points 4. Map it to the appropriate column in your new table This will help you discover the local time zone of your contacts for better scheduling.
My contact location is by city e.g. "Los Angeles, California" - if I put in the write to table to base it off locations in North America, will "Los Angeles, California" meet the criteria?
Yes, if your contact location is listed as "Los Angeles, California," it should meet the criteria when you set the "write to table" feature to filter by locations in North America. However, to ensure accuracy, you might want to use the Normalize Location with Mapbox action in your workflow. This action can help standardize location data, making it easier to filter by broader regions like North America. When setting up your "write to table" feature, you'll need to create a condition that includes cities or states in North America. For more precise filtering, consider using the Contact Location - Country data point, which can help you specifically target North American countries.
Hi Spencer, thanks for your message! Here's a video showing you how you can route records to different tables based on specific conditions, exactly like you're describing here: https://www.loom.com/share/b4de518008194fd1b2026f5cb4122ba3?sid=fda9bcc4-65d7-48af-a003-a40253e01397 Let me know if this makes sense!
.png){kind=logo}
