VideoAmp
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 real-time 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.
What are the benefits of integrating MetaRouter with VideoAmp?
- Seamless Cross-Channel Measurement: The integration allows for easy tracking of user activity across multiple channels, providing a comprehensive view of audience behavior and campaign performance.
- Enhanced Campaign Visibility: The integration provides valuable insights into campaign performance, enabling marketers to make informed decisions and optimize their media strategies.
- Privacy Compliance: The integration supports the transmission of privacy-related information like
us_privacy
andgpp
, ensuring that data sent to VideoAmp is compliant with current privacy regulations.
Capabilities and Considerations
- 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.
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.
Getting Started - From Your VideoAmp Account
To find the URL_ID, VPXID, and BWB values in your own VideoAmp URL tag, follow these steps:
- Obtain the VideoAmp URL Tag:
- Reach out to your VideoAmp support team to get your URL tag. This will be used to track impressions or ad performance.
- Locate the URL Structure:
- The URL will typically follow a structure like this:
https://b.videoamp.com/d2/{URL_ID}/{VPXID}/impression?vpxid={VPXID}&cb={TIMESTAMP}&dnt={OPTOUT}&bwb={BWB}&gpp={GPP_STRING}&gpp_sid={GPP_SID}
- The URL will typically follow a structure like this:
- Identify the Values:
- URL_ID: This is the first alphanumeric string that comes after
/d2/
. It’s a unique identifier for the VideoAmp URL tag. Example:9aa1ff16-16e0-4e7b-8886-6fe52a742ae3
. - VPXID: This value appears twice in the URL. Example:
5464
. - BWB: This is the value after the
bwb
parameter in the query string. Example:35
.
- URL_ID: This is the first alphanumeric string that comes after
Getting Started - From Your MetaRouter Account
Adding a VideoAmp integration.
From the integration library, add a VideoAmp integration. Then, fill out the Connection Parameters:
Connection Parameter | Description |
---|---|
URL_ID | This is the first alphanumeric string that comes after /d2/ . It’s a unique identifier for the URL tag. |
VPXID | This value appears twice in the URL tag. |
BWB | This is the value after the bwb parameter in the query string. |
Event Mappings
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.
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. | Enrichment - VPXID |
bwb | String: A static batch or workflow identifier for tracking purposes. | Enrichment - BWB |
cevt | String: Specifies the type of event being tracked. | N/A - Expression |
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 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 and recommended 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 |
Updated about 2 months ago