Skip to main content

​
Why does my dashboard show fewer impressions than my render count?

Almost always a tracking implementation issue on API integrations: the impression pixel is being fired with fetch() (fails silently) or from a server (classified as invalid traffic). Work through Tracking and measurement. SDK integrations should track within normal discrepancy automatically.

​
Why can’t my agent integration access CPM demand?

Impression-priced demand requires client-side verification that a real user saw the ad. A headless surface cannot produce that evidence, so those impressions would be classified as invalid and unpayable. Choosing your integration path explains the eligibility model; CPA demand is fully eligible on agent surfaces and is where that inventory monetizes.

​
My fill rate is lower than display advertising. Is something wrong?

No. The Ad Server serves only when intent and demand genuinely match. Support conversations, entertainment turns, and low-confidence classifications intentionally return no fill. Conversational inventory earns on relevance and engagement depth, not on fill rate.

​
Can I style the ad units to match my product?

Styling support depends on the integration. The current Web SDK does not expose a public theme API; style the container around it rather than relying on undocumented options. Disclosure labels (“Sponsored”, “Conversational Ad”) must remain visible and unmodified. See Theming.

​
What user data do I need to send?

Send the conversation messages needed for contextual matching and a stable session_id for the conversation when your integration supports it. Adgentek derives contextual signals and may include standard advertising request fields in the demand path; see Privacy architecture.

​
How do payouts work?

Earnings accrue net to publisher and are visible in the dashboard. Payment timing, thresholds, and adjustments are governed by the Publisher Terms. See Payments or contact hello@adgentek.ai.