Client-side (tag-to-tag) integration follows a 1:1 logic:
1 incoming request → 1 outgoing request → 1 response. No auction or request multiplication is involved.
End-to-End Flow
Step 1 - Incoming Request (Ad Request)
The process starts when the system receives a request on the Source.
At this stage, the system counts all incoming traffic.
e.g.s.adtelligent.com/?vast_version=2&aid=11111&app_name=test_app_name&app_bundle=test_app_bundle&width=1920&height=1080&ua=Mozilla%2F5.0%20%28webOS%3B%20Linux%2FSmartTV%29%20AppleWebKit%2F537.36%20%28KHTML%2C%20like%20Gecko%29%20WebAppManager%2F2.0%20Safari%2F537.36%20webOS.TV%2F6.3.0&ip=11.11.111.111&device_type=3&app_store_url=https%3A%2F%2Ftest.page.com%2Fmain%2Ftvapp%2Fdetail
Step 2 - Request Validation
The system validates required parameters:
In-App: bundle or app name
Web: domain
Invalid requests are filtered out and do not proceed further.
Step 3 - Supply-side Targeting and Limits
The request is checked against:
- Global lists (account level)
- Channel settings
- Source settings
If the request does not match targeting rules, it is filtered out.
Step 4 - Demand Matching
If the request passes all checks, the system evaluates campaigns.
Checks include:
- Advertiser & campaign targeting
- Bid floor / pricing rules
- Limits: QPS / Daily, Hourly Request /Opportunity / Daily, Hourly Impression limits.
Step 5 - Campaign Selection
The system selects the campaign most likely to respond.
This is based on performance signals (e.g., fill rate), while still allowing other campaigns to participate.
Step 6 - Outgoing Request (metric Ad Request)
In client-side logic: 1 incoming request → 1 outgoing request to a campaign.
Ad Request with the demand-related slices (Advertiser/Campaign/ Campaign type of integrations, and etc.)
Step 7 - Response to Publisher (with Wrapper VASTAdTagURI)
The system:
- Takes the demand tag
- Replaces macros with actual values
- Wraps the response into a VAST wrapper
- Returns it to the publisher
The publisher receives a VAST XML with a wrapper pointing to the campaign.
Step 8 - Wrapper Call
When the publisher calls the wrapper:
- Campaign Request is recorded
- Ad Opportunity is recorded
This means the request successfully send the demand.
Step 9 - External Flow (Out of Scope)
After the wrapper:
The publisher may go through additional wrappers or redirects
The system does not unwrap or track further steps.
Step 10 - Impression
An Impression is counted when: The impression tracker is triggered.
Common Issues
- Inbound Ad Request ≠ Ad Opportunity
This happens when requests are filtered before reaching campaigns:
-Validation failures
-Targeting mismatch
-Floor price not met
-Limits reached
- Ad Opportunity = 0
Possible when publisher does not call the wrapper.