Below are the fields for the Ecommerce Pipeline OneView dataset. While the only web tracking data source that can be used in this solution is Google Analytics, the Paid Media sources that populate a OneView can be customized to your data specifications and data sources. The datasets that are available in the standard Ecommerce Pipeline OneView configuration are:
- Google Analytics (v_ga_session_geography)
- Google Ads (v_google_ads_api_ad_group)
- Facebook Ads (v_facebook_ads_standard)
- Bing Ads (v_bing_ad_group)
- Google Campaign Manager (v_gcm_standard)
- Twitter Ads (v_twitter_ads_line_item)
- Google Search Ads 360 (v_google_search_ads_ad_group)
- LinkedIn Ads (v_linkedin_ads_creative)
- Snapchat Ads (v_snapchat_ads)
- Yahoo Gemini (v_yahoo_gemini_performance_stats)
- Traditional Media via Google Sheet (v_gs_traditional_media_and_conversion)
- Digital Media via Google Sheet (v_gs_digital_media_performance_and_conversion)
- Pinterest Ads (v_pinterest_ad_group)
- Reddit Ads (v_reddit_ad_standard)
- MNTN (formerly known as SteelHouse) (v_steelhouse_creative_group)
- El Toro (v_el_toro_creative_performance)
- TikTok Ads (v_tiktok_ad_standard)
- Facebook Social (v_facebook_post)
- Twitter Social (v_twitter_activity)
- Instagram Social (v_instagram_media)
- YouTube Analytics (v_youtube_video_analytics)
- LinkedIn Social (v_linkedin_update)
- Twitter Social (v_twitter_engagement)
- Google Search Console (v_google_search_console_total_queries)
- Campaign Monitor (v_campaign_monitor_summary)
- Bronto (v_bronto_delivery)
- Mailchimp (v_mailchimp)
- Exact Target (v_exact_target_send)
- Pardot (v_pardot_email)
- Act-On (v_act_on_message_statistics)
- Emfluence (v_emfluence_email)
- Hubspot (v_hubspot_event)
- ON24 (v_on24_event_registrants)
- Apple Search Ads (v_apple_search_ads_ad_group)
| Field | Field Type | Description |
| Report Date | Date | Date the activity occurred |
| Data Source |
String |
The data source from where the record originated |
| ChannelMix Type | String | A description of the marketing channel strategy e.g. Paid, Owned, or Earned |
| Platform | String | The platform from where the data originated |
| Account | String | The account name from the platform the data was pulled |
| Campaign | String | The campaign name |
| Ad Group | String | The Ad Group or Placement name |
| ChannelMix Channel | String | A description of the marketing channel unified for consistency |
| Impressions | Integer | Total times the ads were served |
| Interactions | Integer | Total times the ads were clicked |
| Cost | Money | Total cost of ads |
| Stage 1 | Integer | First Stage of the Ecom Pipeline as defined by the client |
| Stage 2 | Integer |
Second Stage of the Ecom Pipeline as defined by the client
|
| Stage 3 | Integer |
Third Stage of the Ecom Pipeline as defined by the client
|
| Stage 4 | Integer |
Fourth Stage of the Ecom Pipeline as defined by the client
|
| Stage 5 | Integer |
Fifth Stage of the Ecom Pipeline as defined by the client (if necessary)
|
| Stage 6 | Integer |
Sixth Stage of the Ecom Pipeline as defined by the client (if necessary)
|
| Stage 7 | Integer |
Seventh Stage of the Ecom Pipeline as defined by the client (if necessary)
|
| Stage 8 | Integer |
Eighth Stage of the Ecom Pipeline as defined by the client (if necessary)
|
| Stage 9 | Integer |
Ninth Stage of the Ecom Pipeline as defined by the client (if necessary)
|
| Stage 10 | Integer |
Tenth Stage of the Ecom Pipeline as defined by the client (if necessary)
|
| ChannelMix Key | String | The ChannelMix Key associated with the campaign metadata |
| Insert Date | Timestamp |
The time in which the record was inserted into ChannelMix
|
| ChannelMix Profile | String |
A descriptive name for the segment of data from each data source
|
Comments
Please sign in to leave a comment.