We use cookies to improve your experience and for marketing. Read our cookie policy & privacy policy.

StackUp Support

Stack acting up?
Talk to a human.

Real engineers diagnose your stack issues, demand drops, and integration problems with telemetry data. Same-day response. No tier-1 phone trees. No "have you tried turning it off and on again."

Average first response · under 1 hour during business hours
Incident in progress
14:32 UTC · #TKT-2641

Fill rate drop on /reviews/* P2

Publisherdemosite.com
Symptomfill rate -18% on /reviews/*
Detected14:18 UTC · 14m ago
AssignedSlava K. · ad ops engineer
StatusDiagnosing · root cause likely
youDemand dropped 18% on /reviews/ paths since 12:00. Nothing in the console.14:18
SlavaLooking now. Pulling auction logs. Will report back in 10.14:22
SlavaFound it. Rubicon bidder timeout exceeded after a config push. Pushing rollback.14:30
What we cover

Four kinds of "oh no" we actually solve.

When something breaks, you need a fast triage decision: is this the SDK, the signals, the demand, or something else entirely? Here's what we handle end to end.

01 / SDK

SDK acting up

Performance issues, crashes, init failures, or anything weird happening with the StackUp SDK in your app or web stack.

Common
  • Init / load failures
  • Performance degradation
  • Version conflicts
  • Render or display bugs
02 / CURATION

Curation signals

Signals not passing through correctly via the RTD module, API, or any other integration path. We trace where the data dropped.

Common
  • RTD module not firing
  • Signals missing from bid request
  • API errors or timeouts
  • Wire format issues
03 / DEMAND

Demand drops

Drops in StackUp demand or performance. CPM crashes, fill rate collapses, demand profile shifts. We trace the change back to the bidder, format, or geo.

Common
  • Sudden CPM drop
  • Fill rate decline
  • Bidder dropped out
  • Demand mix shift
04 / ANY OTHER

Anything else

Any issue, question, or weird observation you've encountered and we should know about. No category needed, just tell us.

Common
  • Console or UI bug
  • Account or billing
  • Feature request
  • "This looks weird"
How we help

Three things you won't get anywhere else.

Most ad-tech "support" routes you through a ticket queue, an account manager, and a chatbot before anyone qualified ever sees your problem. We took the opposite approach.

01

Direct line to engineering

The engineer who built the system you're using is the engineer who replies. No account manager translation layer. No "let me check with the team."

no tier-1 phone tree
02

Telemetry-backed diagnosis

We don't ask you to repro the issue. StackUp logs every layer of the platform: auction traces, bidder behavior, SDK calls, signal payloads, API requests. We pull the data, you get the answer.

no "can you screenshot the issue"
03

Same-day human response

Under 1 hour during business hours. Under 4 hours after. Real time on critical incidents. We measure ourselves on this and publish the numbers.

no 5-business-day SLA window
Response targets

By channel. Published, not buried.

We don't hide SLAs in the fine print. Here's what we commit to for every channel, every customer.

Channel
Best for
First response
Hours
Slack (shared)
Active incidents, real-time triage
< 1 hour
Mon–Fri, 24/5
Email
Detailed reports, async discussion
< 1 hour
Mon–Fri, 9am–6pm
Phone (enterprise)
Critical outages, strategic questions
< 15 min
24/7 on-call
Ready to get help?

Got something acting up?
Tell us.

Open a support ticket or email us directly. We'll get back to you within an hour during business hours.