Skip to content

How our agents work

The agent dashboard: 24/7 operation, transparent and with human approval

Every service runs in the background through an orchestrator with specialised agents. You see live what they execute – and everywhere that carries risk, the operation pauses at exactly one right place: the approval queue.

78

agents in 24/7 operation

12

orchestrators (per service)

23

A/B tests currently live

156

rules in the learning cycle (30 d)

4

approval queues per client

< 24 h

average approval time

Live KPI board – what the orchestrator checks hourly

Four metrics steer the entire stack. Deviations land automatically in the alert panel or as a new rule in the learning cycle – no one has to ask.

ROAS (blended, 7 days)

↑ 12 %

4.3×

target ≥ 4.0×

CPA per conversion (7 days)

↓ 16 %

32 €

target ≤ €35

Conversions per day

↑ 24 %

418

target ≥ 400/day

Budget pacing (spent vs. plan)

↑ 3 %

98 %

band 95–105%

Alerts & critical events

What needs attention: anomaly and specialist agents report here with context, cause and next step. “Acknowledge” confirms without acting.

critical Tracking & attribution 40 minutes ago

server-side event “lead_form” broken

event missing in 3.1% of sessions; ROAS attribution is skewed.

event-audit agent

roll out tag-container deployment (v22.4) – no approval needed (patching policy).

warning Paid social 2 hours ago

pacing 22% under plan

ad set “D2C 25–44” running below target since 3 h; CPM normal.

pacing agent

daily budget +15% or widen audience – in the approval queue.

warning Search (Bing) yesterday 10:15 p.m.

impression share 41% (target 55%)

campaign “lead form (Bing)” losing visibility; CPC stays low.

anomaly agent

bids +12% on 3 ad groups – executed autonomously, result monitored for 24 h.

info Email marketing yesterday 8:00 a.m.

deliverability in top range

inbox placement 96.8% across 4 consecutive sends.

deliverability guardian

send volume can be raised by up to 10% – in the learning queue.

Agents are an offer, not a must – manual work stays first choice when you want it

Our operational team delivers every service on this website fully manually as well: setup, operation and reporting personally – without an agent stack, with maximum control. You decide per service and at any point in time how much automation makes sense. All three modes use the same systems architecture, and switching costs you neither setup work nor results.

Fully manual

Classic service: our operational team executes every action personally. The same quality, fully human operation.

most chosen

Hybrid

Agents take routine, monitoring and 24/7 continuous testing; your team and our operational team decide and fine-tune.

Autonomous with approvals

The agent stack runs fully through – critical actions only after your approval in the dashboard.

Active orchestrators

Each card shows the orchestrator of one service. “Live” means: the agent stack is running continuously; “waiting” means: one action is pending in the approval queue.

live · 24/7

Performance Orchestrator

6 agents + orchestrator

live
  • ROAS per channel
  • CPA / CAC trend
  • Budget utilisation (pacing)

SEA Orchestrator (Google & Bing Ads)

6 agents + orchestrator

waiting for approval
  • Impression share (Google + Bing)
  • Search-volume drift per ad group
  • Quality score trend

Bidding strategy switch (e.g. to tROAS)

SEO Orchestrator

4 agents + orchestrator

live
  • Rankings top-10/top-3 per cluster
  • Organic traffic (trend)
  • Core Web vitals

Paid Social Orchestrator

6 agents + orchestrator

live
  • CAC per audience
  • CPM & frequency trend
  • Creative fatigue score

CRO Orchestrator

4 agents + orchestrator

live
  • Conversion rate per landing page
  • Running tests (significance)
  • Drop-off per form step

Affiliate Orchestrator

4 agents + orchestrator

waiting for approval
  • Partner ROI per partner
  • New partners / onboarding status
  • Fraud flags (open)

Payouts above threshold

Marketplace Orchestrator

4 agents + orchestrator

live
  • TACOS per ASIN
  • Feed suppressions (count/reasons)
  • Sponsored ads ROAS

Social Orchestrator

4 agents + orchestrator

live
  • Reach & engagement per channel
  • Follower growth
  • Response times (comments/DMs)

Automation Orchestrator

4 agents + orchestrator

live
  • Qualified leads per week (MQL→SQL)
  • Lead score distribution & drift
  • Workflow error rates

CRM Orchestrator

4 agents + orchestrator

waiting for approval
  • Pipeline value per source
  • Lead-to-deal rate
  • Sync status per integration

Routing rule changes sales ownership

Email Orchestrator

4 agents + orchestrator

live
  • Inbox placement / domain reputation
  • Bounce & spam complaint rate
  • Send volume vs. limit

Tracking Orchestrator

4 agents + orchestrator

live
  • Event validation (error rate per event)
  • Consent consistency (CMP vs. server-side)
  • Attribution drift per model

RevOps Orchestrator

4 agents + orchestrator

live
  • Revenue vs. forecast (per channel)
  • Pipeline coverage
  • Attribution deviation per source

Status is a sample state – with real clients the queue always shows the live pending approvals.

Agent status matrix

All ~78 agents at a glance: status, current load and the last executed action – filterable by status.

Search (Google & Bing Ads)

4 agents
  • Keyword agent

    Last action: took in 312 negatives from search terms

    live 74 %
  • Budget agent

    Last action: Bing daily budget +6% (CPA 18% under target)

    live 61 %
  • Ads agent

    Last action: new headline variants in approval queue

    waiting for approval 45 %
  • Anomaly agent

    Last action: no outliers in 6 h

    live 38 %

Paid social (Meta)

3 agents
  • Creative agent

    Last action: generated 2 new 9:16 video variants

    live 82 %
  • Audience agent

    Last action: lookalike 1% → 2% (CPM −9%)

    live 57 %
  • Pacing agent

    Last action: ad set “D2C 25–44” running 22% under plan

    alert 90 %

Marketing automation

3 agents
  • Scoring agent

    Last action: re-calibrated 4 weights (deal analysis)

    live 49 %
  • Data-hygiene agent

    Last action: merged 1,240 duplicates, removed 380 bounces

    live 66 %
  • Journey agent

    Last action: onboarding journey step 4: open rate +11%

    live 58 %

Email marketing

2 agents
  • Deliverability guardian

    Last action: inbox placement 96.8% (green)

    live 42 %
  • Send-window agent

    Last action: win-back to 12,400 contacts in approval queue

    waiting for approval 51 %

CRM marketing

2 agents
  • Sync agent

    Last action: shop↔HubSpot: 0 conflicts in 24 h

    live 35 %
  • Pipeline agent

    Last action: sent 3 stall alerts to sales

    live 47 %

Tracking & attribution

2 agents
  • Event-audit agent

    Last action: server-side event “lead_form” missing in 3.1% of sessions

    alert 88 %
  • Attribution agent

    Last action: weekly recalibration: 2 channel weights adjusted

    live 55 %

Approval queue (human-in-the-loop)

These actions are prepared by the agents – they only run once you or your team approves them. Everything below this line is autonomous; autonomy ends deliberately here.

Interactive example: approve or reject an action below – this is exactly what your specialists will see.

4 pending approvals

Ordered by risk × budget impact

SEA (Google & Bing Ads) medium #4200

Bidding strategy switch: ad group “Lead form” from tCPA to tROAS 4.2

ROAS trend stable above target for 14 days; CPA stays in line.

Impact: ± €1,800/month budget Model confidence: 92% Approval due: tomorrow 9:00 a.m. Data sources: GA4, Google Ads API, Bing Ads API
Email marketing high #4201

Win-back send to 12,400 inactive contacts (segment: 90+ days)

Segment meets re-activation profile; domain reputation green; send volume < 20% of list.

Impact: Domain reputation, unsubscribe risk Model confidence: 88% Approval due: today 6:00 p.m. Data sources: ESP metrics, domain-reputation feed
Paid social (Meta) medium #4202

Scale ad set “IT B2B 25–54” from €400 to €900 daily budget

CAC below target for 10 days, frequency in the green, creative fatigue low.

Impact: Budget + €500/day Model confidence: 86% Approval due: tomorrow 12:00 p.m. Data sources: Meta CAPI, frequency report
Marketing automation low #4203

Lead scoring rule: weight “demo request” from 15 to 25 points

Deal analysis: 83% of closed-won deals had a demo request before score > 60.

Impact: Qualified leads/day (routing) Model confidence: 95% Approval due: by Friday Data sources: CRM pipeline, journey log

Activity feed

live

Every agent action is traceable: what, why, with what result.

  • today 9:42 a.m.

    Keyword agent: 128 new negative keywords planned (ad group “agency”), auto-apply from 10:00.

  • today 8:15 a.m.

    Performance agent: ROAS PMax 3.8 → 4.1 (7 days). Rule “budget +8% to PMax” executed, autonomous.

  • today 7:05 a.m.

    Approval granted (SEA): tCPA → tROAS switch for ad group “Lead form” – the budget agent has taken over.

  • yesterday 10:03 p.m.

    Anomaly agent: feed error rate 1.2% detected, 14 ASINs fixed, alert sent to specialist.

  • yesterday 6:30 p.m.

    Email stack: subject-line A/B test done – variant B wins (open rate 41% vs. 33%), adopted.

  • yesterday 4:10 p.m.

    Orchestrator (CRM): scoring calibration done – 4 weights adjusted, 2 rules sent to the approval queue.

  • 3 days ago

    Audience agent: lookalike “Demo bookers” (3%) beats the original by 18% CPA – adopted across all campaigns.

  • 6 days ago

    Pacing agent: weekly budget would have been 14% under-utilised on Friday – distribution automatically shifted to Saturdays.

  • 12 days ago

    Learning log: bid modifier “Mon–Fri 6–9 a.m.” re-weighted from +5% to −10% (CPA 22% cheaper in that window).

Decision log

Every approval – approved, rejected or handled automatically – is logged with decision maker and outcome. That is the answer to “who is responsible?”: a traceable record.

#4197

yesterday 5:42 p.m.

approved
SEA

tCPA → tROAS 4.2 for ad group “lead form”

Decided by: M. Weber (head of automation)

Outcome

CPA −9% in 48 h, volume +14%

#4194

yesterday 11:05 a.m.

rejected
Paid social

scale ad set “IT B2B 25–54” to €900/day

Decided by: client (CFO)

Outcome

agent kept €400; scaling waits for Q4 budget

#4189

2 days ago 2:20 p.m.

safe fallback
Email marketing

win-back send to 12,400 inactive contacts

Decided by: SLA exceeded (24 h)

Outcome

safe variant: 4,800 contacts (top quartile), rest waits

#4181

3 days ago 9:12 a.m.

approved
Marketing automation

scoring weight “used pricing calculator” 10 → 18 points

Decided by: client (head of sales)

Outcome

qualified lead rate +7% in 1 week

#4176

4 days ago 4:48 p.m.

approved
SEO & AI search

restructure: consolidate 3 thin-content URLs into 1 pillar

Decided by: client (CMO)

Outcome

pillar impressions +21% after 5 days

A/B tests – set up automatically, evaluated automatically

The test agent creates variants itself, reads them for statistical significance, stops losers and promotes winners into the live operation. These are the latest examples – continuously, without anyone setting up a test manually.

SEA (Google Ads) running

Headline: “24/7 optimisation” vs. “ROAS 4.2 in 14 days”

Variant A

CTR 3.1% · CPA €48

Variant B

CTR 4.4% · CPA €41

Confidence: 94% Sample: 18.4k clicks
Paid social (Meta) running

Creative: 9:16 video vs. carousel with KPI screenshot

Variant A

CPM €14.2 · CTR 1.9%

Variant B

CPM €15.8 · CTR 2.7%

Confidence: 81% Sample: 9.1k views
Email marketing completed

Send window: Tue 10:00 vs. Thu 08:30 (segment: decision-makers)

Variant A

Open rate 33% · 2.1% CTR

Variant B

Winner adopted

Open rate 41% · 2.8% CTR

Confidence: 97% Sample: 24.7k recipients
Marketing automation running

Journey trigger: score > 60 vs. score > 60 + “demo page ×2”

Variant A

2.3 qualified leads/day

Variant B

3.1 qualified leads/day

Confidence: 90% Sample: 1.8k leads

A/B test leaderboard

The most successful running tests, ranked by lift at achieved significance – the test agent promotes winners into live operation automatically.

1

SEA

headline with time promise (“visible in 14 days”)

41,200 clicks · 6 days

Lift

+18 % variant B (time promise)

Significance

97 %

2

Paid social

hook: question vs. claim in video opener

112,800 impressions · 9 days

Lift

+14 % variant A (question)

Significance

94 %

3

Email marketing

send window 9:30 vs. 3:30 p.m. (win-back)

24,800 slots · 4 days

Lift

+11 % variant B (3:30 p.m.)

Significance

91 %

4

Content & CRO

landing page: KPI band vs. testimonial on top

9,400 sessions · 12 days

Lift

+8 % variant A (KPI band)

Significance

76 %

Learning log: new rules from the self-learning loop

This is what learning looks like in practice: the orchestrator evaluates results, writes new rules into the agent policies and documents every change. Your team sees exactly what changed – and why.

2 hours ago

SEA

New rule

Bid modifier “Bing mobile, Mon–Fri”: +15% → 8% (Bing CPA there 21% above target).

Basis

48 hours of CPA data across both search networks

9 hours ago

Paid social

New rule

Fatigue threshold for 9:16 videos lowered from frequency 3.8 to 3.2 (reach drop of 11%).

Basis

3 weeks of frequency/reach trend per ad set

yesterday

Email marketing

New rule

Win-back segment: inactivity threshold moved from 90 to 75 days (re-activation rate +34%).

Basis

A/B test across 2 sends + unsubscribe rates

2 days ago

Marketing automation

New rule

Lead scoring: weight “used pricing calculator” 10 → 18 points (87% of closed-won deals).

Basis

Deal analysis: 214 closed-won deals of the last 12 months

4 days ago

Performance marketing

New rule

Channel weight LinkedIn: 12% → 16% of paid budget (pipeline value 2.3× above Meta).

Basis

Attribution over 8 weeks (GA4 server-side, primary = pipeline value)

Self-learning progression

This is how learning is measured: four metrics with start and current values over recent weeks. No rule is adjusted by hand – these values emerge from the loop.

bid accuracy (Google & Bing)

71 % 85 % +14 %

6 weeks · bid modifiers learn from 96 campaign-weeks

creative fatigue early warning

−12 % −4 % −8 %-Punkte

8 weeks · fatigue thresholds adapt per ad set

lead scoring accuracy (vs. closed-won)

64 % 79 % +15 %

10 weeks · weights learn from 214 deals + rejections

send-window optimization (email)

+0 % +11 % Open-Rate +11 %

5 weeks · windows re-planned per segment

The self-learning loop

The stack gets better every week without anyone adjusting rules: results become new rules, new rules become better results.

01

Measure

All agents deliver data continuously: bids, sends, rankings, conversions – standardised per channel.

02

Analyse

The orchestrator compares results against targets, spotting trends, drifts and anomalies early.

03

Learn

From won and lost tests, deals and deviations, the rule base is re-weighted – automatically.

04

Apply

The new rules go into agent policies: bid modifiers, send windows, priorities – no manual fine-tuning.

Channel & budget overview

Paid-budget allocation across channels with ROAS per channel and daily pacing. The budget agent reallocates within the limits; reallocations above 25% need your approval.

ROAS per channel (30 days)

Budget share
  • Google Ads 38 % 4.4× ROAS
  • Bing Ads 8 % 5.1× ROAS
  • Meta (FB/IG) 27 % 3.6× ROAS
  • LinkedIn Ads 13 % 4.9× ROAS
  • Amazon Ads 9 % 3.2× ROAS
  • Display/remarketing 5 % 2.4× ROAS

Daily budgets & pacing

spent today
  • Google Ads 680 €/day on plan
    52 %
  • Bing Ads 145 €/day over plan
    58 %
  • Meta (FB/IG) 480 €/day Scaling: approval needed
    41 %
  • LinkedIn Ads 235 €/day on plan
    55 %
  • Amazon Ads 160 €/day on plan
    50 %

Frequently asked questions about the agent operation

What happens if I do not approve an action?

The agent does not execute, documents the decision and picks a safe fallback – e.g. it keeps the current bidding strategy instead of launching new targeting. The account never continues “in the unknown”; it waits or continues conservatively.

How fast do approvals have to be given?

Standard service level: 24 hours. For time-critical actions (e.g. pausing a campaign) the orchestrator escalates to the responsible person with priority – and until the decision, the agent’s safety rules apply.

Can I define the autonomy limits myself?

Yes. Thresholds (budget increase %, segment size, send volume) are configurable per client and part of the service agreement. You decide what runs autonomously and what always needs the queue.

Who is responsible if an agent does something wrong?

Actions run on documented rules within your limits; everything beyond that lands in the approval queue. For a faulty execution the service agreement applies, and every agent action is traceable in the log (what, why, which data).

Do the agents learn from the approvals?

Yes. When you reject an action, it is read in as a signal: the agent adapts its recommendations so it makes such suggestions less often – the self-learning loop also learns from human decisions.

Agents for your channels – with your limits

In the first call you define what may run autonomously and what needs your approval. The agents take over the rest – 24 hours a day.

Request a call

30 minutes, no strings. No pitch – we look at your data.