{"id":77811,"date":"2026-01-13T19:18:05","date_gmt":"2026-01-13T19:18:05","guid":{"rendered":"https:\/\/www.bloomreach.com\/?post_type=library&#038;p=77811"},"modified":"2026-02-26T16:56:47","modified_gmt":"2026-02-26T16:56:47","slug":"campaign-agents-why-loomi-ai-changes-the-game","status":"publish","type":"library","link":"https:\/\/www.bloomreach.com\/en\/blog\/campaign-agents-why-loomi-ai-changes-the-game","title":{"rendered":"From AI Assistants to Autonomous Marketing: Why Loomi AI Changes the Game"},"content":{"rendered":"\n<p>Most \u201cAI for marketers\u201d behaves like a helpful intern: it can draft content and campaigns, but you still have to select audiences, choose variants, set timing, and keep tuning as the business shifts. That creates slow learning loops and a permanent execution backlog.&nbsp;<\/p>\n\n\n\n<p><strong>Campaign agents powered by <\/strong><a href=\"https:\/\/www.bloomreach.com\/en\/products\/loomi-ai\"><strong>Loomi AI<\/strong><\/a> change the unit of work from <em>drafts<\/em> to <strong>outcomes<\/strong>. It\u2019s a <strong>multi-agent<\/strong> system that turns a plain-English goal into a complete, end-to-end, brand-safe journey \u2014 and then <strong>keeps optimizing it<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Problem Behind the Hype<\/strong><\/h2>\n\n\n\n<p>Drafts aren\u2019t the bottleneck; orchestration is. Marketers lose time stitching together audiences, decisions, content, channels, timing, and constant experiments. Without a system that learns in production, even great drafts decay into static workflows.<\/p>\n\n\n\n<p>If orchestration is the real blocker, the solution can\u2019t be a better draft. It has to be a system that <em>runs<\/em> the work. That\u2019s the gap campaign agents are built to close.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What We Mean by \u201cCampaign Agents\u201d<\/strong><\/h2>\n\n\n\n<p>At Bloomreach, <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/what-is-agentic-ai\">agentic AI<\/a> takes initiative, makes decisions, and acts toward goals \u2014 completely autonomous, adaptable, self-optimizing, and resourceful. In practice, campaign agents work as a team; they use your customer data to coordinate tasks and finish the work (not just suggest it).<\/p>\n\n\n\n<p>Simply put: Prompts create drafts, while agents create outcomes.<\/p>\n\n\n\n<p>Brands like <a href=\"https:\/\/www.bloomreach.com\/en\/case-studies\/sideshow-affinity\">Sideshow<\/a> and <a href=\"https:\/\/www.bloomreach.com\/en\/case-studies\/revolution-beauty-affinity\">Revolution Beauty<\/a> are already seeing material gains, from <strong>5x revenue per email<\/strong> to <strong>double-digit revenue growth from Loomi AI-built campaigns.<\/strong><\/p>\n\n\n\n<p>Definitions are helpful, but outcomes are better. Here\u2019s how campaign agents use Loomi AI to turn a goal into a live journey that keeps learning.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Campaign Agents Work<\/strong><\/h2>\n\n\n\n<p><strong>1) Goal \u2192 Options<\/strong>&nbsp;<\/p>\n\n\n\n<p>You set an objective (e.g., \u201cIncrease first-to-second purchase rate\u201d). Instead of jumping straight to a plan, Loomi AI surfaces several ways to get there, with pros and cons, channels, and effort.<\/p>\n\n\n\n<p>Example paths it might offer:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Post-purchase nurture<\/strong> (education + cross-sell) via email + on-site<\/li>\n\n\n\n<li><strong>Time-boxed incentive<\/strong> for high-intent cohorts via email\/SMS<\/li>\n\n\n\n<li><strong>Reengage with relevance<\/strong> (recommendations based on last viewed\/bought)<\/li>\n\n\n\n<li><strong>Loyalty nudge<\/strong> (points\/status unlock to drive the 2nd order)<\/li>\n<\/ul>\n\n\n\n<p>You can simply pick a path (or combine a couple) and tweak constraints.<\/p>\n\n\n\n<p><strong>2) Options \u2192 Plan<\/strong><\/p>\n\n\n\n<p>Based on your selection, Loomi AI returns an editable campaign brief: who to target, what to say, where and when to deliver, plus brand and budget guardrails.<\/p>\n\n\n\n<p><strong>3) Plan \u2192 Build<\/strong>&nbsp;<\/p>\n\n\n\n<p>A lead\/orchestrator agent delegates to specialist agents (e.g., audience, content, personalization, channel\/timing, optimizer) and assembles the journey. Specialists can call sub-agents for schema\/queries, recommendations, and template injection.<\/p>\n\n\n\n<p><strong>4) Build \u2192 Preview<\/strong><\/p>\n\n\n\n<p>Before anything runs, Loomi AI renders a customer journey preview showing who\u2019s included, which variants will run, decision points, and timing windows. Expand any node to see rationale, tweak copy and targeting, adjust test windows, or toggle decisions. It\u2019s a clear, editable, brand-safe draft.<\/p>\n\n\n\n<p><strong>5) Preview \u2192 Run&nbsp;<\/strong><\/p>\n\n\n\n<p>On approval, Loomi AI publishes the journey to your existing marketing stack so it uses your current channels, policies, and limits. Sends, delays, branches, and guardrails behave exactly as they do today \u2014 now assembled for you and fully auditable.<\/p>\n\n\n\n<p><strong>6) Run \u2192 Learn<\/strong><strong><br><\/strong>After launch, the system introduces tests (A\/B or <a href=\"https:\/\/documentation.bloomreach.com\/engagement\/docs\/contextual-personalization-2\" target=\"_blank\" rel=\"noopener\">contextual<\/a>), retires weak options, adjusts timing and variants, and keeps moving the KPI \u2014 continuously, not quarterly.<\/p>\n\n\n\n<iframe class=\"vidyard_iframe\" title=\"_How Campaign Agents Work_ (Execution) - Affinity video\" src=\"\/\/play.vidyard.com\/dqu12PUmkQDwo2qZL623rR.html?\" width=\"640\" height=\"360\" scrolling=\"no\" frameborder=\"0\" allowtransparency=\"true\" allowfullscreen referrerpolicy=\"no-referrer-when-downgrade\"><\/iframe>\n\n\n\n<p>That smooth sequence isn\u2019t <em>magic <\/em>\u2014 it\u2019s a team. Under the hood, specialized agents share context, divide the work, and hand results back to the orchestrator.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Beyond the Chatbot: How the Multi-Agent Architecture Actually Works<\/strong><\/h2>\n\n\n\n<p>Most marketing \u201cAI\u201d is a single bot you chat with. Helpful, but it thinks and acts like one person. Our campaign agents are built differently. It\u2019s a <strong>multi-agent system<\/strong>, which is more like a well-run team where each member has a job, the right tools, and shared context. That\u2019s how we go from a vague goal to a working, brand-safe journey in minutes.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Specialists with real jobs. <\/strong>Think audience builder, analytics expert, email architect, and more. Each agent owns a narrow responsibility, so it can go deep. For example, one is great at finding the right people, another is great at writing within your brand voice, and another knows when and where to deliver.&nbsp;<\/li>\n\n\n\n<li><strong>Shared context, scoped on purpose. <\/strong>Agents don\u2019t rummage through everything. Each one sees only what it needs. The copy\/email agent can read brand voice, tone, and approved templates, while the <strong>a<\/strong>udience or timing agents can\u2019t. Analytics agents get schemas and performance history, while content agents only get the insights they should use. This \u201cleast-access\u201d model keeps outputs on-brand while protecting sensitive assets and speeding up decisions.<\/li>\n\n\n\n<li><strong>Tools they can actually use. <\/strong>This isn\u2019t free-form text generation. Agents call concrete tools: They\u2019ll query customer and product data, generate or validate Jinja logic, choose the right recommendations, and produce copy under brand constraints. Output isn\u2019t \u201cAI text,\u201d it\u2019s assets your stack can run.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"670\" height=\"1024\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Campaign-Agents_multiagent-architecture-670x1024.jpg\" alt=\"Bloomreach Campaign Agents multi-agent architecture\" class=\"wp-image-77832\" srcset=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Campaign-Agents_multiagent-architecture-670x1024.jpg 670w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Campaign-Agents_multiagent-architecture-196x300.jpg 196w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Campaign-Agents_multiagent-architecture-768x1173.jpg 768w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Campaign-Agents_multiagent-architecture-1005x1536.jpg 1005w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Campaign-Agents_multiagent-architecture-1340x2048.jpg 1340w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Campaign-Agents_multiagent-architecture.jpg 1432w\" sizes=\"(max-width: 670px) 100vw, 670px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What This Looks Like in Practice<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Orchestrator (canvas agent)<\/strong>: This is your project manager. You say \u201claunch a birthday program.\u201d The orchestrator turns that into a plan: trigger (birth date), audience (people with birthdays coming up), experience (email + optional weblayer), and then assigns work to the right specialists.<\/li>\n\n\n\n<li><strong>Validation loop (analytics + schema)<\/strong>: Before anyone builds, the AI checks reality. Do we actually have a birth_date field? If not, it doesn\u2019t hallucinate; it suggests a fix (e.g., add a collection touchpoint), so the program is grounded in data you own.<\/li>\n\n\n\n<li><strong>Builder agents<\/strong>:\n<ul class=\"wp-block-list\">\n<li><strong>Audience agent<\/strong> composes the segment using approved queries against your schema \u2014 no hand-wavy targeting.<\/li>\n\n\n\n<li><strong>Content\/email agent<\/strong> writes <em>inside<\/em> your brand rails. Layouts use locked HTML blocks (header, footer, hero) so design stays pixel-perfect, and the AI only fills content slots (copy, product picks, dynamic snippets) where variation belongs.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Assembly (Jinja and logic)<\/strong>: Personalization often needs code. A Jinja expert agent adds the right logic (\u201clast viewed product,\u201d \u201cdays since purchase\u201d), the analytics agent supplies the data source, and the content agent stitches together the final asset. Finally, the <strong>o<\/strong>rchestrator drops it into the journey, ready to run.<\/li>\n<\/ul>\n\n\n\n<p>The result isn\u2019t just a pretty draft \u2014 it\u2019s a finished, deterministic flow your team can approve, launch, and watch improve.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"395\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/image-5-1024x395.png\" alt=\"Marketing flow created autonomously by Bloomreach Campaign Agents\" class=\"wp-image-77827\" title=\"Screenshot 2025-11-11 at 9.09.31\u202fPM.png\" srcset=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/image-5-1024x395.png 1024w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/image-5-300x116.png 300w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/image-5-768x296.png 768w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/image-5-1536x592.png 1536w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/image-5.png 1600w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Once you see the team in action, the gap with \u201cassistants\u201d becomes obvious: assistants hand you parts; <strong>agents ship the whole program<\/strong>.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why This Is Categorically Different From \u201cAssistants\u201d<\/strong><\/h2>\n\n\n\n<p>Most \u201cAI assistants\u201d help you start. Campaign agents help you ship. Here are the practical differences you\u2019ll feel:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>From prompts to outcomes. <\/strong>An assistant hands you a draft asset and leaves the wiring to you. <strong>Loomi AI<\/strong> assembles the <em>whole<\/em> campaign \u2014 who to target, what to say, which channel to use, and when to send \u2014 so you\u2019re approving a live journey, not collecting files.<\/li>\n\n\n\n<li><strong>Continuous optimization, not set-and-forget. <\/strong>Static flows decay. Agents watch campaign performance and keep adjusting delays, variants, and even structure. If a timing window cools off or a variant stalls, the AI pivots without waiting for a quarterly refresh.<\/li>\n\n\n\n<li><strong>Personalization at the system level. <\/strong>Real personalization isn\u2019t giving some recommendations; it\u2019s giving different people different paths through the journey. Agents make per-person decisions across steps \u2014 timing, channel, offer \u2014 so \u201cbest\u201d can vary by user and moment.<\/li>\n\n\n\n<li><strong>Data-native, not URL-native. <\/strong>Some tools will just crawl your website to guess brand voice, products, and recommended campaigns. It\u2019s fast, but shallow. It doesn\u2019t know your unified profiles, order history, inventory, or existing system emails, so it can suggest duplicative or off-base programs. <strong>Loomi AI is data-native.<\/strong> It works <em>inside<\/em> your first-party data and execution engine: customer attributes, events, catalog, and the deterministic blocks that actually send messages. That\u2019s how it respects your defaults (e.g., avoids duplicating order confirmations) and optimizes for outcomes you care about.<\/li>\n\n\n\n<li><strong>Enterprise guardrails by design. <\/strong>Brand-locked templates keep layouts consistent. Policy checks and approval thresholds gate high-impact changes. Budgets and frequency caps protect audiences. Every decision is traceable, so you can explain what happened and why.<\/li>\n<\/ul>\n\n\n\n<p>Shipping once is table stakes. The edge comes from shipping smarter every day, which is where decisioning and contextual personalization kick in.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Decisioning That Learns \u2014 Contextual Personalization Inside Journeys<\/strong><\/h2>\n\n\n\n<p>Most teams still crown a single \u201caverage winner.\u201d Campaign agents don\u2019t. They learn who needs what (and when), and apply those decisions inside your journeys across email, SMS, push, and web.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Start with a clear objective. <\/strong>Point the system at real outcomes (conversion, revenue, margin). Use higher-volume proxies (clicks, micro-conversions) where you need faster feedback to get the loop moving.<\/li>\n\n\n\n<li><strong>Decide where to experiment. <\/strong>Not every node needs testing. Pick the high-leverage spots \u2014 send-time windows, creative variants at key touchpoints, or channel choice when there\u2019s a real trade-off (e.g., push vs. email for time-sensitive offers).<\/li>\n\n\n\n<li><strong>Explore, then exploit (and repeat). <\/strong>Begin with a few sensible options. Let Loomi AI learn quickly, retire weak performers, and add new contenders. As it gathers signals, it shifts from one-size decisions to contextual personalization, where the \u201cwinner\u201d can differ by person and moment.<\/li>\n\n\n\n<li><strong>Use the signals that matter. <\/strong>Decisions are informed by attributes, demographics, real-time behavior, location, purchase history, campaign activity, and loyalty status. This means that \u201csend now\u201d for a high-intent browser might become \u201cwait until evening\u201d for a casual window-shopper.<\/li>\n\n\n\n<li><strong>Keep it inside the journey. <\/strong>These choices aren\u2019t one-off tests; they\u2019re embedded as a node, so the whole flow can optimize message + channel + timing end-to-end.<\/li>\n\n\n\n<li><strong>Stay within guardrails. <\/strong>Budget and frequency caps protect audiences, brand\/policy checks keep outputs on voice, and human-in-the-loop approvals gate high-impact changes. You get speed without losing control.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Contextual-personalization-1024x538.jpg\" alt=\"Campaign Agents using contextual personalization to deliver individual variants based on preferences\" class=\"wp-image-77835\" srcset=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Contextual-personalization-1024x538.jpg 1024w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Contextual-personalization-300x158.jpg 300w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Contextual-personalization-768x403.jpg 768w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Contextual-personalization.jpg 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>A key characteristic of agents is their ongoing learning. That\u2019s why we treat tracing, evaluations, and approvals as first-class parts of the product.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Quality, Observability, and Control<\/strong><\/h2>\n\n\n\n<p>Agentic systems aren\u2019t \u201cset and forget.\u201d We treat quality and tracing as top priorities:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Tracing:<\/strong> Inspect agent and tool calls, inputs and outputs, and latencies. Think of this as an <em>agentic system debugger<\/em> for visibility and root-cause analysis.<\/li>\n\n\n\n<li><strong>Evaluations:<\/strong> End-to-end and per-agent checks (generation success, ready-to-use, editability, build time, consistency), with automated scoring and human review.<\/li>\n\n\n\n<li><strong>Brand safety:<\/strong> Locked templates, policy checks, and auditability. Humans still approve high-impact changes.<\/li>\n<\/ul>\n\n\n\n<p>These choices land where customers actually experience them. And because Loomi AI works inside your existing systems, each decision is grounded in reality \u2014 not guesswork.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Built Where Decisions Happen<\/strong><\/h2>\n\n\n\n<p>Loomi AI doesn\u2019t guess from the sidelines \u2014 it works inside the systems you already use to run marketing (where profiles, events, catalog, consent, and automations live). That\u2019s why agent decisions are grounded, brand-safe, and easy to audit: journeys compile to the same primitives your team trusts (segments, waits, decisions, sends).<\/p>\n\n\n\n<p>This is different from URL-native tools that crawl a website to infer brand and campaigns. They offer a quick start, but they\u2019re often shallow: They don\u2019t see unified identities, purchase history, inventory, or which system emails already go out, so they might suggest duplicative or off-base programs.<\/p>\n\n\n\n<p><strong>What marketers get:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>No duplicate or off-base communications.<\/strong> Agents are aware of the confirmation\/receipt flows your ESP already sends and will avoid recommending lookalike messages that create noise or confusion<\/li>\n\n\n\n<li><strong>Decisions grounded in reality.<\/strong> Targeting, offers, and timing are informed by actual behavior, SKU availability, margin constraints, and returns patterns \u2014 not just what\u2019s visible on your homepage<\/li>\n\n\n\n<li><strong>Consent and brand safety by default.<\/strong> Journeys inherit your consent states, opt-outs, frequency caps, and policy rules, while generated content stays within locked templates and approved voice guidelines<\/li>\n\n\n\n<li><strong>Faster iteration with clean handoffs.<\/strong> Because journeys compile to the same primitives your team trusts, marketers can jump in to edit, approve, and roll back without special tooling<\/li>\n\n\n\n<li><strong>Closed-loop learning.<\/strong> Performance writes back to the same source of truth, so agents learn from real outcomes (clicks, conversions, revenue) and improve the next decision automatically<\/li>\n<\/ul>\n\n\n\n<p>Bottom line: URL-native tools can draft something that looks on-brand. <strong>Loomi AI ships programs that are on-brand, on-policy, and aligned with how your business actually runs.<\/strong><\/p>\n\n\n\n<p>Put it all together and here\u2019s what a real day looks like: one goal, a working plan, and continuous improvement without the usual rebuilds.<\/p>\n\n\n\n<iframe class=\"vidyard_iframe\" title=\"_Built Where Decisions Happen_ - Affinity video\" src=\"\/\/play.vidyard.com\/Jeqy8gMtK7B3sYCWDLjASc.html?\" width=\"640\" height=\"360\" scrolling=\"no\" frameborder=\"0\" allowtransparency=\"true\" allowfullscreen referrerpolicy=\"no-referrer-when-downgrade\"><\/iframe>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>A Day in the Life of a Marketer<\/strong><\/h2>\n\n\n\n<p><strong>Goal:<\/strong> \u201cIncrease repeat purchases from first-time buyers this month.\u201d<\/p>\n\n\n\n<p><strong>1) Brief<\/strong><strong><br><\/strong>You describe the outcome you want. Loomi AI returns a short plan you can edit: who to target, what to say, and a safe timing window (e.g., test 2-6 hours after first purchase). It feels like a creative brief you didn\u2019t have to write.<\/p>\n\n\n\n<p><strong>2) Build<\/strong><strong><br><\/strong> Behind the scenes, agents split the job:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The audience agent composes the segment against your real schema (with no guesswork)<\/li>\n\n\n\n<li>The content agent drafts on-brand variants and slots in recommendations<\/li>\n\n\n\n<li>The channel\/timing agent chooses where and when the message should land<\/li>\n<\/ul>\n\n\n\n<p><strong>3) Approve and launch<\/strong><strong><br><\/strong>You tweak copy, adjust the test window, and hit publish. Everything compiles to the same building blocks your stack already uses (segments, waits, decisions, sends), so it\u2019s familiar and auditable. And most importantly, you\u2019re still in control of the process.<\/p>\n\n\n\n<p><strong>4) Optimize<\/strong><strong><br><\/strong>As results come in, Loomi AI adjusts the flow as needed: retiring weak variants, leaning into what works, and adapting timing per context. You see performance improve without the usual rebuilds.<\/p>\n\n\n\n<p>Zooming back out, this is the day-to-day impact: faster launches, more programs, and personalization that finally touches who\/what\/where\/when \u2014 not just subject lines.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Proof It Moves the Needle&nbsp;<\/strong><\/h2>\n\n\n\n<p>Early pilots show the same pattern in the wild. For example, <a href=\"https:\/\/www.bloomreach.com\/en\/case-studies\/sideshow-affinity\"><strong>Sideshow<\/strong><\/a> saw roughly <strong>2x value per email delivered<\/strong> after moving key lifecycle programs to agent-assembled flows. At the same time, iteration cycles sped up because tests ship as part of the work, not as a separate project.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.bloomreach.com\/en\/case-studies\/sideshow-affinity\"><img decoding=\"async\" width=\"1024\" height=\"630\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Sideshow_CTA-1024x630.png\" alt=\"Sideshow creates campaigns in under 15 minutes with Bloomreach's Campaign Agents\" class=\"wp-image-78114\" srcset=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Sideshow_CTA-1024x630.png 1024w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Sideshow_CTA-300x185.png 300w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Sideshow_CTA-768x473.png 768w, https:\/\/www.bloomreach.com\/wp-content\/uploads\/2026\/01\/Sideshow_CTA.png 1462w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>As agents take on execution, the marketer\u2019s job shifts from wiring journeys to setting goals, taste, and constraints the AI can run with.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why Choose Bloomreach for Agentic Marketing<\/strong><\/h2>\n\n\n\n<p>Loomi AI isn\u2019t an AI panel bolted onto the side. It\u2019s an <strong>agentic brain<\/strong> that sits inside the systems you already use to run marketing \u2014 where customer profiles, events, product data, consent, and automations actually live.&nbsp;<\/p>\n\n\n\n<p>That\u2019s why it can use your real context, assemble complete programs, and finish the work with guardrails and explainability. The result: teams move from sporadic, rules-driven personalization to continuous, goal-driven engagement. <a href=\"https:\/\/www.bloomreach.com\/en\/products\/affinity\"><strong>See campaign agents in action<\/strong><\/a> and start transforming your marketing.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most \u201cAI for marketers\u201d behaves like a helpful intern: it can draft content and campaigns, but you still have to select audiences, choose variants, set timing, and keep tuning as the business shifts. That creates slow learning loops and a permanent execution backlog.&nbsp; Campaign agents powered by Loomi AI change the unit of work from [&hellip;]<\/p>\n","protected":false},"author":126,"featured_media":78121,"template":"","ew-regions":[],"ew-solutions":[],"library_type":[513],"library_blog_tag":[362,363,365,364],"industry":[],"channel":[],"topic":[283,546,291],"class_list":["post-77811","library","type-library","status-publish","has-post-thumbnail","hentry","library_type-blog","library_blog_tag-ai-and-innovation","library_blog_tag-loomi","library_blog_tag-marketing-automation","library_blog_tag-personalization","topic-ai","topic-personalization","topic-team-efficiency"],"acf":{"library_blog_banner_content":"","library_blog_banner_cta1_text":"","library_blog_banner_cta1_href":"","library_blog_banner_cta1_new_tab":false,"library_blog_banner_cta2_text":"","library_blog_banner_cta2_href":"","library_blog_banner_cta2_new_tab":false,"library_blog_banner_bg_color":"#EAF7FE","library_blog_banner_cta_text_color":"#FFF","library_blog_banner_cta_bg_color":"#019ACE","library_blog_banner_cta2_text_color":"#000","library_blog_banner_cta2_bg_color":"#FFF","library_blog_chatgpt_content":"","library_blog_chatgpt_cta_href":"","library_blog_chatgpt_cta_text":"Ask ChatGPT"},"_links":{"self":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library\/77811","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library"}],"about":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/types\/library"}],"author":[{"embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/users\/126"}],"version-history":[{"count":4,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library\/77811\/revisions"}],"predecessor-version":[{"id":80753,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library\/77811\/revisions\/80753"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/media\/78121"}],"wp:attachment":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/media?parent=77811"}],"wp:term":[{"taxonomy":"ew_regions","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/ew-regions?post=77811"},{"taxonomy":"ew_solutions","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/ew-solutions?post=77811"},{"taxonomy":"library_type","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library_type?post=77811"},{"taxonomy":"library_blog_tag","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library_blog_tag?post=77811"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/industry?post=77811"},{"taxonomy":"channel","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/channel?post=77811"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/topic?post=77811"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}