If you're planning to use ROI Hunter, and you're using some analytics tool for which we don't have the direct integration, it's important to plan ahead for connecting your analytics data. This will allow you to work with the information about revenue, purchases and detail views of your products and performance of your campaigns.
Whether you're using any internal system or analytics tool, you can still connect your performance data to ROI Hunter through our Custom Analytics integration.
This setup allows you to track revenue, calculate ROAS, and evaluate product performance across campaigns, but it does require some preparation on your side.
🔎 In many onboarding cases, delays happen due to incomplete, missing, or delayed access to analytics data. This article is here to help you evaluate what’s needed and how much time you might need to prepare.
How It Works
ROI Hunter connects with your analytics data via daily exports that you store in an online location accessible to us. We regularly download these files and match them to your products and campaigns.
What you’ll need to prepare:
Export your data daily in a standard CSV format (can be compressed to reduce file size)
Store it in a cloud folder or server (see options below)
Include the recommended tracking info to get the full value from ROI Hunter
We strongly recommend including 30–60 days of historical data at the beginning to unlock meaningful insights from day one.
Is your team currently unable to prepare this on your side? If so, feel free to share access to your analytics tool with us—we’re happy to explore how we can retrieve the data from our end.
Next Steps
Go through this article or share it with your data or BI team
Identify where and how you'll export the data
Align on file format and tracking structure - optionally, send us sample file so we can review the data
Let us know your timeline and access method
We’ll then guide you through the rest of the integration.
File Specification
File Specification
Format: CSV (UTF-8)
Frequency: One file per day
Compression: ZIP, GZIP, or TAR are supported if needed
Delimiter: Comma by default, but customizable
Each file should contain data for just one day.
What to Include in the File
What to Include in the File
Required Columns
Column | Purpose |
date | Date of the event (YYYY-MM-DD format) |
product_sku | Product ID/SKU matching your product catalog in ROI Hunter |
These fields are necessary to match your performance data to your products and show results in Product Insights.
Recommended for Campaign-Level Insights and product and campaign ROAS
Including tracking parameters allows us to show ROAS (from dynamic ads) and tie performance to specific campaigns and ads. This significantly improves the value you get from the platform.
Column | Description |
source | UTM source (e.g., facebook, google) |
medium | UTM medium (e.g., cpc, social) |
campaign | UTM campaign name |
tracking_id | Ideally the Ad ID (or uniquely named ad, campaign, or ad set) |
Without this tracking info, we can’t link revenue to your campaigns — meaning no ROAS insights or ad-level performance data.
Optional Fields
Column | Purpose |
currency | Revenue currency (if missing, market default is used) |
filtering_field | To filter data for a specific market (e.g., country) |
Metrics To Include
Metric | Description |
product_revenue | Revenue from each product sold |
item_quantity | Number of units sold |
quantity_added_to_cart | How often users added the product to cart |
product_detail_views | Page views of the product |
custom_metrics_1–3 | Optional custom metrics (if relevant for your setup) |
Supported Storage Methods
Supported Storage Methods
You’ll need to provide access to one of the following:
Method | Notes |
(S)FTP | Secure server login credentials are required |
AWS S3 | We connect via secure access keys |
Google Drive | Grant access to data-integration@roihunter.com |
BigQuery | Available in beta |
ROI Hunter Storage | We can host the data on AWS S3 or (S)FTP if you don’t have a solution in place. |
Let us know early if you need us to provide hosting — this can reduce setup time.
Do you need to use some other storage? Let us know and we can discuss the options.
🔐 Access & Security Notes
File encoding: UTF-8 (let us know if using another format)
Proxy access available: We can connect through a proxy if your infrastructure requires IP whitelisting
Whitelist IP: 94.130.136.58
How Much Time Will It Take?
Setting up analytics integration can vary depending on how quickly your team can:
Prepare and automate daily data exports
Align the required format and dimensions
Share access credentials and storage details
💡 Most delays happen when these steps aren’t ready before onboarding should start. We recommend reviewing this with your data team ahead of time.