VAST FAQ
This FAQ is intended to address the most common questions we receive from suppliers integrating with Audiohook via VAST. It complements the official VAST Tag Integration Guide and focuses on practical implementation details, common pitfalls, and how to interpret bid responses.
1. What VAST versions does Audiohook support?
Audiohook supports VAST 4.0 and higher.
Specify in the VAST tag with the parameter vspec=4
2. What is the correct way to implement the Audiohook VAST tag?
Suppliers should use the Audiohook-provided VAST tag exactly as issued. The base URL and required query parameters must not be altered.
Common best practices:
- Use the full VAST tag provided by Audiohook
- Do not hardcode values that are meant to be passed dynamically
- Ensure macros are populated correctly by your ad server or player
Altering the base URL or restructuring the tag often results in bid requests not reaching Audiohook.
3. Can we modify the VAST tag to fit our internal requirements?
In general, no. The base VAST endpoint and required parameters are non-negotiable, as they are required for request validation, auction participation, and reporting accuracy.
You can pass additional parameters to improve bidding and reporting.
If your platform has technical constraints, reach out to Audiohook before making changes so compatibility can be reviewed.
4. How does Audiohook return pricing in the VAST response?
Audiohook includes pricing information directly in the VAST response.
Key points:
- The VAST response contains a pricing element
- The price provided represents the net value of that ad for the supplier
- This is the amount the supplier should expect to receive for the delivered impression
Suppliers may use this value for internal reconciliation or reporting, but Audiohook reporting remains the source of truth for billing.
5. Should we rely on the VAST price for billing and reconciliation?
Audiohook reporting is authoritative for billing purposes. While the VAST response includes net pricing, suppliers are encouraged to use Audiohook reports to reconcile impressions and revenue, especially in cases of discrepancies caused by caching, retries, or player-side behavior.
6. What parameters are required in the VAST request?
Audiohook requires specific parameters to be passed in the VAST request in order to validate traffic, bid correctly, and report accurately.
Required data:
- User IP address
- User User-Agent (UA)
- Inventory or feed type
vspec=4(to explicitly indicate VAST 4+)
- Placement
Additional requirements for podcast inventory:
- Feed URL
- Episode URL
Cache-busting macros are not required.
While only the parameters above are required, passing additional contextual information where supported (for example, device, app/site identifiers, or content signals) can improve bidding performance and reporting quality.
Missing or improperly populated required parameters are a common reason Audiohook does not return bids.
7. My VAST requests are being sent — why am I not seeing any bids??
Common causes include:
- Modified or truncated VAST tag URLs
- Missing required macros or parameters
- Incorrect publisher or supplier identifiers
- Requests not being sent to the Audiohook endpoint at all
- Requests failing validation due to formatting or encoding issues
Audiohook may still see requests arriving, but invalid requests will not be bid on.
8. Do you support VAST wrappers?
Yes, Audiohook supports VAST wrappers, provided the wrapper ultimately resolves to a valid Audiohook VAST request and does not strip required parameters. Excessive wrapper depth or timeout constraints may impact fill.
9. What audio-specific considerations should we be aware of?
- Ensure the player supports audio-only VAST responses
- Verify that impressions, quartiles, and completion tracking pixels fire correctly
- Confirm that autoplay, user-initiated playback, and background playback behaviors align with your platform’s policies
10. How can we test our VAST integration?
Audiohook recommends:
- Testing in a staging or test environment first
- Sharing sample VAST requests and responses for validation
- Confirming impression and completion tracking before scaling traffic
Reach out to Audiohook support with example requests if validation is needed.
11. Who should we contact if something isn’t working?
For any issues with VAST integration, suppliers can reach Audiohook support at supplier@audiohook.com or publisher@audiohook.com.
When contacting support, please include:
- The actual VAST tag you are using
- The system or platform you are set up on
- Any recent changes made on your side
12. Can Audiohook’s VAST endpoint be used for client-side ad requests?
Yes — Audiohook can support client-side VAST calls, though some setup is required on the backend to ensure requests are properly processed. Server-side ad requests remain the default and quickest way to integrate, and client-side support can be enabled once the necessary setup is complete. Notify publisher@audiohook.com if you will be sending client-side requests.