Intro
Analytical assets are integrated and configured from the Markets and Assets menu. They can be connected to multiple parts of the ROIH platform:
Markets and Assets: Used in all product performance features
Product Insights: Used to create product sets for Meta
Campaign Insights: Used to see performance of your campaigns
Google Product Source: Used to create product sets for Google Shopping
It is necessary to connect them independently to see the analytical data on these parts of the ROIH platform.
Google Analytics 4
GA4 offers several advantages:
It's possible to use separate filers within one GA4 property to filter statistics relevant for selected countries
Includes app revenue
Is supported on all parts of the ROIH platform
In the connection setup to the ROIH platform, you can set up a country filter that allows connection to a market only for GA4 data from selected countries. With this filter, it is possible to connect the same GA4 properties to more markets, as long as each market is used with a different country filter.
Additionally, GA4 includes the possibility to measure app revenue. If you are using GA4 for measuring app revenue in the selected property, it will be automatically downloaded and included in the product performance statistics.
How to Connect Google Analytics 4
Navigate to Settings > Markets and Assets, select a market, then navigate to the Analytical Assets tab and click the "Add Asset" button
Select the relevant GA4 property, optionally specify the country or countries for which revenue should be included on that market, and fill out the rest of the required information
Device name: An optional input which serves to name the source device of statistics and can be used with data filtering by the device.
Ad ID: Important to check and select in order to enable automatic tracking of the ads in the ROIH platform, which is required to calculate product ROAS from DPAs which is often used in Segments.
Click the "Save" button
With this setup, you are configuring that your URL ads parameters contain the ad.id parameter, and with the selection box you can specify whether the ad.id is in the utm_id parameter. It is strongly recommended for everyone to use the ROIH platform tracking so:
The revenue can be correctly connected with the campaign that generated the revenue
Correct product ROAS can be calculated (ROAS is calculated as both revenue from dynamic product ads and spend on dynamic product ads). The most common value is to have the ad.id in the utm_id parameter.
Custom Analytics Data
If you aren't using Google Analytics 4, but some other services or have a custom solution, Custom Analytics is the best option for you. Custom Analytics are any analytical data, exported daily, that can be shared with us in a standard format via online storage. Adobe Analytics or Branch are examples of commonly integrated analytical sources using this approach.
The exports should be available daily, ideally as separate files, in a single folder or directory in the agreed storage location. ROI Hunter downloads these files regularly and connects the data to products to be available in Product Insights.
Including 30-60 days history at the beginning of the integration is recommended, so you can get maximum from ROI Hunter right away.
File Specification
Your analytics data exports should be CSV files with columns described below. Specific column names aren't enforced, as long as they are understandable.
See example. One file should contain data from one day only.
Required Dimensions
These are required to properly connect your analytical data to your products with daily granularity.
Date
Product SKU - corresponding to product IDs in your advertising assets
Recommended Dimensions
Tracking Dimensions
These connect your analytical data to ads and campaigns that generate them. If not provided, ROI Hunter cannot assign your data to individual channels or distinguish data from dynamic ads.
These should correspond to the UTM parameters set in your ads.
Source
Medium
Campaign
Tracking ID
This should be the Ad ID for maximum compatibility. We also support Ad name, if it is unique between all ads.
Alternatively, we can use Campaign or Adset (if available) identifiers, although this may limit the functionality of some ROI Hunter features.
It's highly recommended to set these up as best as possible. Without quality tracking information, ROI Hunter's value is significantly reduced.
Other dimensions (optional)
Currency
one that is used for product revenue
if not present in the file, we use market currency, unless specified by you differently
Filtering dimension
You can include an additional dimension, which can ROI Hunter use for filtering your data for this particular market and asset
The frequent filtering dimension is "country".
Metrics
Product Revenue - Revenue from individual product sales.
Item Quantity - Total number of product units sold. Also known as "purchases", "items sold", "units" or "orders".
Quantity Added to Cart - Number of times a product has been added to cart. Also known as "add to cart" or "cart additions"
Product Detail Views - Number of times users viewed the product-detail page. Also known as "view items", "product views" or "items viewed".
up to three custom metrics - available for additional metrics you wish to use in ROI Hunter.
Supported Storage Methods
(S)FTP
S3 bucket
Google Drive
Our account
data-integration@roihunter.comneeds access to the folder.
Any other way of sharing data can be discussed individually
In case you aren't able to provide the data via your storage, ROI Hunter can provide one.
Technical Details
Technical Details
The file should be encoded using UTF-8, let us know if you are using a different encoding.
The default CSV delimiter is the comma but may be customized if needed.
The file can be compressed using ZIP, GZIP, and TAR formats.
ROI Hunter can use a proxy when accessing your servers if you require whitelisting certain IP addresses:
Whitelist 94.130.136.58 IP address
Make sure to let us know to use the proxy server
App Revenue
Google Analytics 4 has the option to track app revenue.
It is possible to connect campaign-level data from Branch. Branch cannot provide product-level data directly, so the only way to get product-level data from Branch is using the custom data integration method detailed above. If you are able to provide this data, we can connect it to the platform as custom analytics.
Currently, app revenue from any other services like Appsflyer or Adjust is not possible to integrate unless the data is shared in the format described above.
Revenue Tracking Setup
Revenue tracking is an important function that allows you to connect revenue with the ad that generated that revenue. It provides a better picture of your product performance and also allows us to include only the revenue from the product dynamic ads into the calculation of metrics like ROAS, which is used in cases such as the Poor Performers segment preset.