Meta tags:
description= Data-driven segments are groups of profiles that you automatically populate when they meet certain conditions. Profiles enter the segment when they match the conditions and leave the segment when they stop matching the conditions. These kinds of segments help you group profiles according to real-time activities.;
Headings (most frequently used words):
segment, segments, conditions, with, based, data, using, in, on, timestamps, driven, how, can, and, customer, io, use, triggered, automations, your, we, make, it, better, create, edit, delete, duplicate, or, json, arrays, special, characters, object, relationships, messages, bounce, latest, features, at, you, criteria, to, join, past, future, new, names, for, familiar, parts, of, see, which, email, clients, recipients, manage, all, accounts, single, login,
Text of the page (most frequently used words):
the (159), and (129), #segment (125), you (108), messages (84), app (80), your (79), push (77), for (70), profiles (69), #conditions (66), data (62), events (53), with (52), segments (50), started (44), email (43), use (43), track (42), set (40), notifications (38), create (37), customer (36), can (36), automation (36), that (35), when (35), this (34), automations (30), metrics (30), how (29), identify (29), get (29), message (28), troubleshooting (27), profile (26), based (25), api (24), event (24), time (23), start (23), timestamp (23), add (23), from (22), match (22), tracking (22), not (21), using (21), send (21), they (21), triggered (20), trigger (20), links (20), click (18), new (18), objects (18), account (18), multiple (17), mobile (17), changelog (17), edit (16), one (16), anonymous (16), getting (16), page (15), condition (15), what (14), driven (14), want (14), attribute (14), any (14), test (14), but (13), have (13), messaging (13), manage (13), listeners (13), deep (13), activity (13), object (12), options (12), example (12), group (12), relationship (12), custom (12), quick (12), guide (12), inbox (12), google (12), integrations (12), update (11), emails (11), person (11), users (11), authentication (11), capture (11), subscription (11), delete (10), timestamps (10), relationships (10), join (10), enter (10), workspace (10), webhooks (10), array (10), works (10), inline (10), android (10), channels (10), screen (10), lifecycle (10), privacy (9), support (9), our (9), will (9), characters (9), then (9), their (9), date (9), attributes (9), people (9), billing (9), handling (9), providers (9), configuration (9), migrate (9), advanced (9), content (9), transactional (9), editor (9), journeys (8), future (8), json (8), all (8), more (8), out (8), like (8), has (8), link (8), sms (8), logic (8), groups (8), forms (8), notification (8), liquid (8), features (7), overview (7), need (7), past (7), another (7), could (7), other (7), journey (7), value (7), would (7), addresses (7), gmail (7), build (7), security (7), flutter (7), packages (7), version (7), design (7), studio (7), integration (7), introduction (7), components (7), service (6), about (6), help (6), special (6), actions (6), find (6), may (6), instead (6), include (6), within (6), after (6), true (6), does (6), only (6), legacy (6), specific (6), calculus (6), passed (6), least (6), these (6), javascript (6), sending (6), settings (6), ios (6), react (6), native (6), amazon (6), inbound (6), pipelines (5), make (5), copy (5), duplicate (5), criteria (5), choose (5), broadcast (5), don (5), joined_club (5), signed (5), single (5), days (5), same (5), someone (5), instance (5), option (5), whether (5), are (5), contain (5), target (5), slack (5), twilio (5), course (5), two (5), accounts (5), contains (5), names (5), access (5), segmentation (5), best (5), practices (5), whatsapp (5), updates (5), location (5), earlier (5), rules (5), reference (5), frequently (5), asked (5), questions (5), hubspot (5), code (5), syntax (5), broadcasts (5), welcome (5), css (5), analysis (5), policy (4), company (4), platform (4), part (4), arrays (4), active (4), workflow (4), workflows (4), where (4), membership (4), name (4), values (4), lets (4), tab (4), 2023 (4), march (4), because (4), until (4), before (4), information (4), which (4), birthday (4), meet (4), evaluate (4), creating (4), who (4), customers (4), them (4), ever (4), server (4), both (4), url (4), human (4), search (4), matches (4), class (4), image (4), represents (4), performed (4), city (4), shipping_addresses (4), index (4), drop (4), drag (4), website (4), personalize (4), 2026 (4), understand (4), builder (4), rich (4), apis (4), conversions (4), snowflake (4), reporting (4), storage (4), bigquery (4), redshift (4), webhook (4), client (4), understanding (4), tests (4), recipes (4), branches (4), opt (4), filters (4), statuses (4), preferences (4), global (4), component (4), faq (4), styles (4), layouts (4), domain (4), style (4), docs (4), documentation (3), team (3), feedback (3), address (3), bounce (3), sql (3), import (3), form (3), won (3), under (3), also (3), select (3), changes (3), description (3), try (3), between (3), some (3), first (3), created (3), historical (3), here (3), now (3), should (3), save (3), see (3), soft (3), issues (3), bounces (3), containing (3), clicks (3), last (3), change (3), separate (3), failed (3), courses (3), certain (3), non (3), equals (3), results (3), regex (3), either (3), com (3), character (3), work (3), store (3), complex (3), leave (3), display (3), there (3), devices (3), view (3), requests (3), matching (3), longer (3), right (3), list (3), exit (3), activities (3), releases (3), login (3), conversion (3), workspaces (3), sign (3), assign (3), roles (3), standard (3), performance (3), upgrade (3), expo (3), implementation (3), certificates (3), visual (3), salesforce (3), mixpanel (3), facebook (3), ads (3), cohorts (3), triggers (3), map (3), reverse (3), etl (3), beta (3), live (3), common (3), compliance (3), deliverability (3), goals (3), errors (3), web (3), multi (3), types (3), why (3), center (3), templates (3), surveys (3), phone (3), integrate (3), preview (3), smtp (3), export (3), via (3), csv (3), mcp (3), agent (3), clients (3), status (2), contact (2), resources (2), pricing (2), parcel (2), soon (2), provide (2), improve (2), close (2), better (2), icon (2), might (2), place (2), means (2), recipient (2), referenced (2), sure (2), usage (2), manually (2), leverage (2), times (2), individual (2), called (2), whose (2), 2028 (2), joins (2), generate (2), implementing (2), while (2), last_online (2), following (2), backfilled (2), walkthrough (2), most (2), gains (2), type (2), added (2), decide (2), specify (2), consider (2), audience (2), building (2), still (2), bounced (2), delivery (2), failures (2), mailbox (2), hard (2), includes (2), clicked (2), been (2), note (2), opened (2), machine (2), opens (2), define (2), behavior (2), onboarding (2), case (2), setting (2), refine (2), related (2), online (2), associate (2), regular (2), seek (2), hide (2), sink (2), cases (2), treat (2), however (2), functions (2), property (2), favorite_foods (2), pizza (2), shipping (2), call (2), against (2), item (2), down (2), left (2), items (2), determine (2), handle (2), each (2), boolean (2), must (2), pages (2), key (2), etc (2), takes (2), initial (2), process (2), basic (2), just (2), automatically (2), stop (2), updated (2), browser (2), cookies (2), expiration (2), members (2), plan (2), tasks (2), audit (2), logs (2), verification (2), provisional (2), sound (2), sdks (2), html (2), comparing (2), pixel (2), sendgrid (2), marketing (2), rudderstack (2), azure (2), blob (2), cloud (2), audiences (2), braze (2), amplitude (2), connections (2), mode (2), servers (2), deleting (2), services (2), postgresql (2), mysql (2), microsoft (2), filter (2), incoming (2), csp (2), proxying (2), management (2), disconnect (2), backend (2), lead (2), video (2), semantic (2), directory (2), dashboard (2), personalization (2), zone (2), reusable (2), flow (2), batch (2), concepts (2), sends (2), reminders (2), upcoming (2), trial (2), book (2), nps (2), frequencies (2), aren (2), library (2), files (2), brand (2), adding (2), parameters (2), localization (2), line (2), respond (2), feature (2), adoption (2), promotions (2), number (2), sender (2), validate (2), senders (2), headers (2), adapting (2), template (2), own (2), relay (2), collaborate (2), connected (2), review (2), accessibility (2), shortcuts (2), collections (2), survey (2), suggestions (2), setup (2), cli (2), academy (2), structured (2), learning (2), demo (2), 2024, peaberry, software, inc, terms, 9450, gemini, suite, 43920, beaverton, oregon, 97008, 7105, win, startup, program, partners, careers, guides, competitors, community, blog, release, notes, possible, appreciate, bot, please, valid, optional, yes, helpful, download, copied, clipboard, confirm, choice, starting, archived, unsent, depends, let, break, removed, locations, driving, describe, pencil, changing, cause, rebuild, affect, dates, range, present, even, imagine, january, officially, club, remember, necessarily, joined, creates, caveats, scenario, ensures, inadvertently, experience, relevant, starts, makes, easier, predict, finish, specified, dec, 2022, jan, day, since, 1669965166, assume, ago, practice, exception, causes, typically, brief, explain, exists, recorded, different, manner, enters, loses, performs, actually, calculate, always, used, learn, identifying, already, seeing, editing, menu, foundational, subscribed, rewriting, helps, reuse, across, included, didn, expect, had, point, qualifies, temporary, full, too, large, permanent, doesn, exist, permanently, blocked, august, 2025, began, capturing, tracked, someurldata, segmenting, attributed, chose, engaged, suit, every, english, rather, than, refining, differently, above, took, three, others, member, relate, things, companies, base, provides, way, everybody, connection, admins, entity, expressions, equal, yield, statement, wanted, write, few, person2, wild, card, sun, lesson, string, reside, function, literal, perform, expression, look, patterns, escape, otherwise, referencing, belonging, itself, evaluator, operator, trying, fries, burgers, simply, notation, blank, below, spent, minimum, dollar, amount, purchase, bubbles, logical, difference, additional, layers, needs, reflect, respectively, nest, side, rearrange, move, into, nested, fit, condition1, condition2, condition3, specifying, requiring, screens, snippet, directly, filled, pair, were, determining, received, those, bit, monitor, clicking, upper, corner, going, task, top, selecting, untitled, explains, steps, apply, well, working, check, series, populate, kinds, according, real, july, complete, llms, txt, har, file, qualifications, respecting, gdpr, allowlist, session, sensitivity, timezone, enable, experimental, regions, sso, factor, credentials, customize, canceling, payment, problems, reducing, overages, credits, bill, sdk, channel, swift, zendesk, yandex, wisepops, optimizer, vwo, twitter, engage, tiktok, talon, sprig, saleswings, sent, ripe, qualtrics, playerzero, pipedrive, pinterest, moengage, metronome, meta, logrocket, livelike, launchdarkly, koala, intercom, heap, tag, manager, gtm, sheets, analytics, gtag, gainsight, fullstory, friendbuy, criteo, cordial, commandbar, clevertap, bing, attio, algolia, insights, adobe, actable, predictive, resend, filtering, mapping, database, warehouse, action, zoho, zapier, mparticle, classic, platforms, python, node, calculator, scheduled, syncs, invalid, transform, utility, methods, identity, managing, identities, method, frameworks, wordpress, wpforms, webflow, unbounce, typeform, squarespace, jotform, formstack, sources, backfill, playback, chat, ecommerce, fields, alias, source, specs, attempted, conclusive, reports, home, composer, reusing, snippets, limits, supported, formats, zones, recommended, geolocation, queue, draft, default, direct, mail, lob, configure, receive, randomized, delay, wait, window, delays, blocks, false, random, split, control, reformat, fix, inconsistent, holdout, llm, decisions, examples, format, inactive, trips, rss, feed, cohort, optimize, words, double, cart, abandonment, anniversary, recipe, grace, periods, tickets, syncing, sync, stripe, follow, responses, receiving, entering, troubleshoot, state, schedule, tags, requirements, assets, outside, language, preference, faqs, unsubscribes, https, universal, checking, translations, translate, languages, milestones, achievements, promote, offers, localize, step, compose, telehealth, weight, hipaa, regulations, kind, campaign, registration, compliant, register, numbers, keyword, smart, encoding, keywords, shortening, mms, payloads, registering, device, tokens, provider, trustpilot, reviews, fake, bcc, preheader, text, avatar, logo, mailchimp, column, foundation, amp, pre, processing, archive, customizing, basics, editors, consent, open, oracle, dyn, sparkpost, postmark, mandrill, mailjet, mailgun, verify, deliverable, kickbox, anonymized, authenticating, apple, private, unsubscribe, rfc, 8058, postmaster, tools, suppression, lists, suppressions, spamhaus, blocklist, listings, shared, dedicated, warming, attachments, transitioning, history, submit, teammates, stylesheet, loop, through, conditionals, directives, modifiable, placeholder, scratch, publish, connect, quality, mso, emmet, fixes, variables, cleanup, formatting, inlining, mjml, framework, transformers, responsive, dark, keyboard, convert, purposes, manual, activate, waitlist, awareness, announce, drive, upsell, monetize, power, tutorials, external, merging, know, available, storing, suppress, ids, visited, field, resolve, cursor, ides, claude, chatgpt, command, routines, skills, ask, guest, section, breaks, tells, recipients, navigation, labels, think, campaigns, familiar, parts, latest, request, log,
Text of the page (random words):
gmentation logic like condition1 and condition2 or condition3 there is a handle on the left side of each condition or group that you can use to drag and rearrange conditions after you create your segmentation conditions use the handle to move conditions into nested groups that fit your specific logic using and and or conditions in a segment when you create a segment you determine whether a profile needs to match all conditions or at least one condition these reflect and and or logic respectively you can use the group condition to add additional layers of and and or logic within your segment items within the group use the same and or logic here s a walkthrough of using these conditions in a segment while you select the logic when you add a group new groups add another drop down that you can use to change logic within the group note that groups only display their logic the and and or bubbles to the left of the group after you add at least two conditions because you ll need at least two conditions before there s any logical difference between and and or for example the segment below contains profiles that have performed the purchase event and are either new customers created within the last 30 days or spent a minimum dollar amount using json arrays in segments attributes and events can contain complex json arrays objects and arrays of objects you can use json notation to access json in your segment however when you access an array you can provide an index to access a specific item in the array or leave the index blank to match any item in the array for example if you store a profile s shipping addresses in an array of objects call shipping_addresses you could match the city in the first shipping address using shipping_addresses 0 city if you want to match a city value against any object in the array you could use shipping_addresses city if you want to match a value against any property in any value or object in the array you could simply use shipping_addresses when referencing an array of values not a property belonging to an object in an array but the array itself array the equals evaluator works like a contains operator for example if you have an attribute called favorite_foods containing the values pizza fries burgers trying to create a segment where favorite_foods equals pizza would evaluate to true segments with special characters event names and other data you may want to create segments from can include special characters in most cases we ll treat special characters as literal characters is however the following special characters perform regular expression regex functions that look for patterns of characters to treat them as characters not search functions you can escape them with for example 1 otherwise this is how they work special character regex function this is a wild card it represents any character for example s n matches event names sink sun and lesson if you don t place any characters after it ll match the string up to for example si matches reside and sink this represents and it matches both values in a statement you can use it with attribute conditions and event conditions but not event names for example if you wanted to find a profile whose email address contains person and gmail you could write email contains person gmail a few emails this would match on include person gmail com person test gmail com or person2 gmail com because these addresses contain both person and gmail this represents or it lets a person who has performed or not performed either event to enter the segment for example a segment based on hide seek events lets a person who has performed either the hide or seek events to enter the segment use the conditions with contain to use regex to use regular expressions you need to use the contains or does not contain conditions using equals or does not equal will yield no results segments based on object relationships you can relate profiles to objects an object is a non person entity that you can associate with one or more people like a company account or online course things like companies accounts or online courses then you can base segments on these relationships the connection between an object and a person in your workspace for instance if you have account objects people could have relationships to an account if they re admins this provides a way to trigger an automation for everybody at a company or in certain courses when you create a segment use the relationship option to target profiles based on their relationship to one or more objects then you can refine the condition with object or relationship attributes image 1 passed any calculus class in the image above profiles join the segment when they have at least one relationship to a calculus course they ve passed if someone took three calculus courses and passed one but failed the others they are a member of this segment now if you added two separate relationship conditions rather than refining the one we d evaluate the segment differently image 2 in any calculus class and passed any course in this example profiles join the segment when they re related to any calculus course and related to any course they ve passed if someone passed an english class but failed a calculus class they ll still join the segment if you want to evaluate object and relationship attributes for a single object refine the relationship don t separate the conditions to trigger an automation based on every relationship change create relationship triggered automations instead relationship based segments trigger an automation for the first relationship that matches not all relationships that match if that does not suit your use case consider setting up a relationship triggered automation instead segments based on messages you can create a segment of profiles that have engaged with emails slack messages twilio sms webhooks and in app messages when you create your segment you ll select the message type then define your criteria for instance if you chose email you can then include any email in your workspace or search for a specific email to use then you define the behavior you want to target here it s onboarding email 1 has ever been opened by a human note that last part opened by a human we track human and machine metrics for email opens and clicks when creating a segment that includes this data you choose whether to target any data human and machine or only data attributed to profiles segmenting on link clicks containing specific url data if you segment on a message with has ever been clicked on tracked link containing someurldata your segment will only contain profiles that clicked that link after august 9 2025 this is when we began capturing url data from links profiles click bounce based conditions the has ever bounced condition for segments includes both hard and soft bounces hard bounces permanent delivery failures recipient mailbox doesn t exist or is permanently blocked soft bounces temporary delivery failures full mailbox server issues message too large if you see profiles included in your segment that you didn t expect they may have had a soft bounce at some point which still qualifies them for the has ever bounced condition segments based on segments when creating a segment you can include other segments as conditions this helps you reuse the same conditions across multiple segments to save time building them for instance consider who your foundational audience is like profiles that are subscribed and active customers you can create a segment for this group and add it instead of rewriting all the conditions to another segment when creating a new segment click the overview tab under profiles click segment and decide whether profiles should be in or not in a segment you specify when editing a segment click edit then click add condition or group choose segment from the menu and decide whether profiles should be in or not in a segment you specify not seeing the option to add segment conditions you can only add segments as conditions if the segment you want to use as a condition is not referenced in another segment for instance if you already added the segment signed up to another segment s conditions then you can t add segment conditions to signed up used as a trigger for a legacy segment triggered automation learn more about identifying this trigger type using timestamps you can create data driven segments based on timestamps but we evaluate match time for segments with timestamps in a different manner from other segments a match time is when someone enters a segment for most segment conditions this is when someone gains an attribute loses an attribute performs an event and so on but for segments with timestamp conditions we can actually calculate the match time based on a date time so the match time might not always be for instance when someone gains a timestamp attribute to help explain this you could have a segment condition where a profile attribute birthday exists profiles would join this segment as soon as you recorded their birthday attribute but if your segment is birthday is a timestamp 15 days from now profiles will only join your segment when they meet that condition here s a brief walkthrough of using timestamps in segments for more information on implementing timestamp conditions in a segment go to timestamp conditions segment triggered automations with past timestamps customer io typically does not trigger automations based on historical data customer io as a practice does not trigger automations based on backfilled or historical data the exception is with backfilled events for segment triggered automations this means you can create a profile with a past timestamp that causes the profile to join a segment but that profile will not trigger an automation based on that same segment for example assume you created a data driven segment with the following condition last_online is a timestamp before 30 days ago you use this segment to trigger a new automation on march 30 2023 you add a new profile with the attribute last_online 1669965166 dec 2 2022 at 12 12 46 am this profile would enter the segment but the match time would be jan 1 2023 at 12 12 46 am 30 days after the profile s timestamp which is the first day the segment condition is true while this profile would enter the segment it would not trigger an automation on march 30 2023 since the match time is in the past for more information on implementing past timestamp conditions in a segment go to timestamp conditions segment triggered automations with future timestamps try out date triggered automations instead if you trigger automations using a timestamp based segment you may want to try date triggered automations instead with date triggered automations profiles won t trigger an automation until the time specified in the trigger conditions this makes it easier to predict when profiles will start and finish journeys remember that for segments with a condition that starts with a timestamp the match time is the time when the condition is true not necessarily when the profile joined the segment this creates some caveats for segment triggered automations based on future timestamps in this scenario a profile will trigger the automation but not start a journey until the timestamp this ensures that profiles don t inadvertently experience the journey before it s relevant for example imagine that you have a segment called signed up with a single condition joined_club is a timestamp on january 1 2023 you add a profile whose joined_club value is a timestamp for march 17 2028 this profile joins the signed up segment because their joined_club attribute is a timestamp if you use the signed up segment as an automation trigger this profile will generate an automation journey but they won t start the journey until march 17 2028 the date and time value for their joined_club attribute because that s when the profile officially joins the club you can find journeys with future start times on the automation s journeys tab or under an individual profile s journeys tab with a started time in the future if you want profiles to start their journey based on future timestamp values you may want to try out date triggered automations instead but if you need to use a segment triggered automation based on a future date you can set the automation s trigger conditions to include dates and times within a range of the present the is a timestamp between or after conditions this lets profiles with a timestamp like our joined_club example start their journey even when they have a future value edit a segment you can edit the name description and conditions for your segment changing a data driven segment s conditions will cause the segment to rebuild and may affect active automations go to segments click the segment you want to update click the pencil icon to edit the name or description of the segment click describe changes to leverage ai to improve the segment criteria click edit to manually edit the conditions driving membership in the segment delete a segment go to segments click the segment that you want to delete click and choose delete segment you can also select one or more segments on the segments page then click delete if one of your workflows depends on the segment we won t let you delete the segment so your automations and other actions don t break find where your segment s referenced under usage and make sure it s removed from all locations an automation unsent one time send or api triggered broadcast your segment could be part of the trigger recipient conditions or other workflow conditions a form a sql import another active segment active means it s not archived duplicate a segment you might want to copy a data driven segment as a starting place for the conditions in a new segment go to segments click the segment that you want to duplicate click the options icon then choose duplicate segment and confirm your choice copied to clipboard create a data driven segment segment conditions data you can use in segment criteria how to join conditions using and and or conditions in a segment using json arrays in segments segments with special characters segments based on object relationships segments based on messages bounce based conditions segments based on segments using timestamps segment triggered automations with past timestamps segment triggered automations with future timestamps edit a segment delete a segment duplicate a segment copy page copy page download md is this page helpful how can we make it better close do you need help from customer io support no yes what part of customer io do you need help with how can we improve this page email optional please provide a valid email address i am not a bot we appreciate your feedback our support team will contact you as soon as possible platform platform overview platform features journeys data pipelines parcel pricing resources documentation release notes blog community co...
|
