Platform Deep Dive
How the optimization engine works
A technical walkthrough of how Brandpathio reads conversion signals across your connected DSPs, reconciles attribution overlap, and writes budget changes back via API every 4 hours. No new buy-side contracts. No change to your DSP relationships. Just a coordination layer above your existing stack.
System Architecture
Three-tier optimization architecture
DSP API connectors pull campaign pacing and conversion data up to the engine every cycle. The engine reconciles attribution overlap across platforms, scores creative-audience pairs by deduplication-adjusted ROAS, then writes budget changes back to each DSP via their campaign management APIs.
What You Measure
Every metric that matters for performance teams
ROAS by Creative-Audience Pair
Return on ad spend broken down by which specific creative is running to which audience segment — across every connected DSP.
Cross-DSP Frequency Score
Composite frequency count per user across all connected platforms — not just per platform. The number that matters for reach efficiency.
Incremental Conversion Lift
The marginal conversion lift each DSP contributes above the baseline rate — statistically modeled from holdout cell comparisons, not from platform-reported attribution.
Budget Utilization by DSP
How much of your allocated budget is actually spending on each platform versus being throttled or pacing conservatively.
Audience Overlap Coefficient
The share of your target audience reachable on more than one connected DSP simultaneously — your cross-platform duplication exposure and a direct input to frequency deduplication.
Reallocation Velocity
The average dollar-per-hour rate at which budget moves between DSPs during a rebalancing cycle — a signal of optimization aggressiveness.
Onboarding Timeline
Live in 5 business days
No migration, no new buy-side contracts, no changes to your DSP seat agreements. We connect to your existing accounts via their campaign management APIs and start reading impression and conversion data within 24 hours of credentialing.
Day 1: API credential review and secure connection setup.
Days 2–3: DSP connections verified, conversion signal mapping configured.
Day 4: First 48-hour optimization run, baseline ROAS established.
Day 5: Kickoff review with your media team.
"The setup took three days from first API call to first rebalancing cycle. We were watching budget move automatically by the end of the week."
Performance Marketing Director, retail brand
Managing $1.8M/month across 6 DSPs
Next Step
Ready to see it with your actual DSP data?
We'll walk through the architecture with your team and show you what the first rebalancing cycle would look like on your current spend.
Request Demo