> For the complete documentation index, see [llms.txt](https://docs.roivenue.com/roivenue-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/arukereso.md).
# Árukereső
How to connect Árukereső to Roivenue, including generating the API key and whitelisting Roivenue, and what the connector downloads.
Árukereső is a Hungarian price comparison site. The Roivenue connector downloads daily click and cost data per product using the Árukereső API.
## Setting up the connector
Árukereső needs two things before Roivenue can read anything: an API key, and an IP range that allows Roivenue to call the API. Both are on the same admin page.
### 1. Open the API Config page
Sign in to Árukereső and open the admin section, or go straight to [arukereso.hu/admin/ApiConfig](https://www.arukereso.hu/admin/ApiConfig).
### 2. Generate the API key
Generate a key for the Roivenue connector. Árukereső copies it to your clipboard, and you will paste it into Roivenue in step 4. Treat it as a password.
### 3. Allow Roivenue to call the API
Árukereső only accepts API calls from IP ranges you list. Roivenue does not call from a fixed address, so enter both halves of the address space, `0.0.0.0/1` and `128.0.0.0/1`.
{% hint style="warning" %}
Skipping this step is the most common reason an Árukereső connector authorises and then returns nothing. The API key alone is not enough.
{% endhint %}
### 4. Authorise the connector in Roivenue
Add an Árukereső connector in Roivenue. It asks for two values: the e-mail address of your Árukereső account, which identifies the authorisation, and the API key from step 2.
## What the default setup downloads
Creating an Árukereső connector from the recommended template gives you one job, bringing back one row per product and day.
| Árukereső column | Roivenue column |
| -------------------------- | --------------- |
| `Dátum` | date |
| `Terméknév*` | adCampaign |
| `Átkattintások` | clicks |
| `Átkattintások költsége**` | cost |
Every row is stamped with Árukereső as the platform and HUF as the currency.
{% hint style="info" %}
Árukereső has no campaigns or ad groups, so the template puts the product name into the campaign field. Campaigns on Árukereső rows are therefore product names, and there is no ad group.
{% endhint %}
Impressions, conversions and conversion value are all set to zero, because Árukereső reports none of them through this connector. Clicks and cost are the whole picture, so cost per click works while anything built on conversions does not.
The job reprocesses the last three days on every run, so recent figures can still move slightly.
## Available columns
The tables above are what the recommended template downloads. Every column this connector can bring back is listed on [Árukereső - Supported Columns](/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/arukereso/arukereso-supported-columns.md).
Adding one means editing the connector in the Advanced Editor, which stops that connector receiving template updates.
## How far back the data goes
{% hint style="warning" %}
Árukereső serves the last 30 days only. Connecting today gives you a month of history, whatever start date you pick, and anything older has to come from a different source.
{% endhint %}
## Troubleshooting
The connector authorises but no data arrives
Check the IP ranges on the API Config page first. Both `0.0.0.0/1` and `128.0.0.0/1` need to be listed, and an incomplete range is the usual cause: the key is accepted, the calls are not.
Conversions and revenue are zero
That is expected. Árukereső does not report orders or revenue through this API, so the connector sets both to zero rather than leaving them missing. Attribute Árukereső on cost and clicks, and take conversions from your order data instead.
One product appears as two campaigns
The campaign field holds the product name, and Árukereső returns the name as it was at the time. A product renamed during the period therefore appears under each name it had. The underlying `Identifier` stays the same, but it is not part of the default mapping.
I asked for a year of history and only got a month
That is the platform limit rather than a fault. Árukereső exposes 30 days, so Roivenue cannot request more.