VideoAmp
This integration is currently in beta. Contact your MetaRouter support team to get started.
What Is VideoAmp?
VideoAmp is an advertising measurement platform designed to optimize media planning and buying across digital and TV channels. It helps advertisers and marketers unify audience data, providing insights into cross-channel performance to make more informed media investment decisions. The platform enables measurement and attribution, allowing businesses to see the impact of their advertising campaigns across different devices. VideoAmp's solutions help improve targeting, optimize ad spend, and enhance overall campaign performance by breaking down the silos between digital and linear television data.
Product Type: Advertising
Integration Type: Starter Kit
Event Source Type: Web
Event Scope: Full-Funnel Events
Capabilities
- Cross-Channel Measurement: The integration enables sending event data with parameters like
appId,timestamp,context.ip, andcontext.userAgent, supporting cross-channel audience measurement by tracking user activity across platforms. - Audience-Based Planning: The integration sends data related to user consent, campaign data, and privacy-compliant information (
us_privacy,gpp,gpp_sid), helping VideoAmp build audience segments based on user behavior and privacy requirements. - Real-Time Analytics: The integration facilitates real-time event tracking and sends impression data to VideoAmp, allowing for immediate analysis and reporting of media performance.
- Data Unification: The integration includes context and user data elements such as IP addresses, user agents, and campaign data, supporting the unification of audience insights across multiple touchpoints.
Considerations
- In our testing, requests above ~20,000 characters in the URL began to fail. While this isn't a formally documented limit, it may be a practical constraint to consider when using this integration.
- All values must be URL-encoded and arrays pipe-delimited.
- One request per event; batching not supported.
- Complex lists (e.g., products) must be pipe-delimited.
Limitations
- Attribution and Incrementality: The integration primarily focuses on sending impression data and general event information. It does not explicitly handle conversions, attribution windows, or incremental impact measurement, limiting advanced attribution capabilities.
- Media Optimization: While it sends event and impression data, the integration lacks real-time feedback loops or specific data tailored for optimizing media performance or adjusting ad delivery dynamically.
- Advanced Targeting: The integration primarily covers high-level event data and user context. For more advanced targeting, additional granular data related to user behavior and interests would be necessary, which is not fully addressed by the integration.
Starter Kit Setup Guide
1. Gather Credentials
- Reach out to your VideoAmp support team to get your URL tag. The URL typically follows this structure:
https://b.videoamp.com/d2/{URL_ID}/{VPXID}/impression?vpxid={VPXID}&cb={TIMESTAMP}&dnt={OPTOUT}&bwb={BWB}&gpp={GPP_STRING}&gpp_sid={GPP_SID}
- Identify the following values from your URL tag:
- URL_ID: The first alphanumeric string after
/d2/. Example:9aa1ff16-16e0-4e7b-8886-6fe52a742ae3. - VPXID: This value appears twice in the URL. Example:
5464. - BWB: The value after the
bwbparameter in the query string. Example:35.
- URL_ID: The first alphanumeric string after
2. Add a VideoAmp Integration
- From the integration library, add a VideoAmp integration. Then, fill out the Connection Parameters:
| Connection Parameter | Description |
|---|---|
URL_ID | The first alphanumeric string that comes after /d2/. A unique identifier for the URL tag. |
VPXID | This value appears twice in the URL tag. |
BWB | The value after the bwb parameter in the query string. |
3. Configure Event Mapping
- MetaRouter provides all of the event mappings that VideoAmp integrations typically require. You may add custom events, parameters, or mappings in accordance with VideoAmp's API documentation.
4. Deploy to Pipeline
- In the Pipelines tab, add your VideoAmp integration.
- Select the correct integration revision.
- Click Add Integration to finalize deployment.
Event Mappings
Global
Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.
| Output Key | Description | Expected Input |
|---|---|---|
cb | String: The timestamp when the event occurred. | timestamp |
dnt | String: Indicates whether the user has opted out of tracking (Do Not Track). | context.consent |
vpxid | String: A static identifier for the specific video or ad impression. | $$VPXID$$ |
bwb | String: A static batch or workflow identifier for tracking purposes. | $$BWB$$ |
cevt | String: Specifies the type of event being tracked. | Expression – returns input.event, or input.type when the event name is empty |
app | String: The unique identifier for the app. | appId |
ip | String: The IP address of the user. | context.ip |
user_agent | String: The User-Agent string from the user's browser or device. | context.userAgent |
cp1 | String: Campaign-related data tied to the event. | context.campaign |
us_privacy | String: US privacy string, used for privacy compliance (e.g., CCPA). | properties.us_privacy |
gpp | String: Global Privacy Platform (GPP) string for user consent. | properties.gpp |
gpp_sid | String: GPP string for site-specific consent. | properties.gpp_sid |
Required & Recommended Identifiers
These identifiers must be mapped to VideoAmp in order for successful user matching to occur. Without these IDs, any events sent to VideoAmp may not be accurately reflected in reporting. For your convenience, required IDs are mapped as Global parameters to ensure they are added to every event.
| Attribute | Example | Sync Injector Required? |
|---|---|---|
ip | 192.168.1.1 | No |
user_agent | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 | No |
Integration Validation
Coordinate with your VideoAmp representative to confirm that events are being received and processed correctly on their backend.
Updated 9 days ago