Connecting Arukereso on Clarisights
Árukereső (Arukereso) is the leading Hungarian price-comparison platform. Connecting Arukereso to Clarisights brings per-product click and cost data — for both native Arukereso traffic and Google CSS traffic routed through Arukereso — into your performance reporting alongside other paid channels.
At a glance
| Authentication | Static API key (Api-Key header) issued by Arukereso, scoped to a single merchant |
| Permissions needed | Partner Portal API access enabled by your Arukereso account manager. Calling IP must be whitelisted on the Arukereso side. |
| Account discovery | Manual — Arukereso has no list-shops endpoint, so you provide Shop ID and Shop Name on the connect form (one shop per credential) |
| Data freshness | Daily |
| Lookback window | Last 30 days on every refresh (Arukereso enforces a max 30-day window per export) |
| Backfill on connect | Last 30 days |
| Timezone | User-supplied (typically Europe/Budapest) — Arukereso's API does not return a timezone |
| Currency | User-supplied (typically HUF) — Arukereso's API does not return a currency |
| Levels supported | Account · Campaign (per-product rows) |
| Limited rollout | No |
Prerequisites
An active Arukereso merchant account
Partner Portal API access enabled — contact your Arukereso account manager to enable the API and issue an Api-Key for your shop
Your Arukereso Shop ID and Shop Name — visible in the Arukereso Partner Portal
Static egress IP whitelisting: Clarisights routes outbound calls through a fixed proxy IP. Provide that IP to your Arukereso account manager so the calling IP is whitelisted on the Arukereso side. Contact Clarisights support if you need the IP value.
(Optional) Enrollment in the Arukereso Google CSS Program — required to receive CSSONLY data; without it, only AKONLY (native Arukereso) data is returned
Steps to Connect
Step 1 — Get your API key, Shop ID, and Shop Name from Arukereso
Contact your Arukereso account manager and request:
An Api-Key for your shop
Confirmation of your Shop ID and Shop Name
IP whitelisting for the Clarisights egress IP
Treat your Api-Key like a password. It grants read access to your Arukereso merchant data.
Step 2 — Add Arukereso in Clarisights
In Clarisights, go to Integrations → Arukereso → Add Account.
[TODO: Screenshot needed — Integrations page Arukereso row]
Step 3 — Enter credentials and shop details
Provide:
API Key — from Arukereso
Shop ID — numeric ID of your Arukereso merchant
Shop Name — human-readable name for the connection
Currency — 3-letter ISO code (typically
HUF)Timezone — IANA timezone string (typically
Europe/Budapest)
Click Submit. Clarisights validates the API key against the Arukereso ListExport endpoint and creates the ad account on success.
[TODO: Screenshot needed — Arukereso credentials form]
⚠ "Invalid Arukereso API key or the calling IP is not whitelisted" → Either the Api-Key is wrong or the Clarisights egress IP is not whitelisted on the Arukereso side. Confirm both with your Arukereso account manager and retry.
⚠ "Too many requests to Arukereso" → You are hitting the Arukereso rate limit (5 GenerateExport / 20 ListExport / 20 Download per minute). Wait a minute and retry. If the error persists during normal use, contact Clarisights support.
Verify the connection
Go to Integrations → Arukereso. Your shop should appear with a "Connected" status.
First data appears within ~24 hours (Arukereso data syncs daily).
Quick start: create a new report, add Arukereso as the data source, and add Account · Product Name · Data Source · Clicks · Spend.
Data available
Hierarchy
Arukereso returns one row per product per day in its export CSV, with no native concept of campaigns or ad groups. Clarisights normalizes the merchant to Account and stores per-product rows at the Campaign level. The Data Source dimension distinguishes native Arukereso clicks (AKONLY) from Google CSS clicks routed through Arukereso (CSSONLY).
Native level (Arukereso) | Clarisights level |
Merchant / Shop | Account |
Product (per-row in the export) | Campaign (Arukereso has no native Campaign / Ad Group / Ad) |
Dimensions
Dimension | Level | Description |
Account | Account | Arukereso shop name and shop ID |
Product ID | Campaign | Arukereso product identifier ( |
Product Name | Campaign | Product name as listed on Arukereso ( |
Data Source | Campaign |
|
Metrics
Metric | Description |
Clicks | Clicks delivered to your shop ( |
Spend | Cost paid for those clicks ( |
Limitations & known constraints
One shop per credential: An Arukereso Api-Key is scoped to a single merchant and there is no list-shops endpoint. To connect multiple shops, request a separate Api-Key per merchant and add each as a separate connection in Clarisights.
IP whitelisting required: Arukereso requires API callers to come from a whitelisted static IP. Without the Clarisights egress IP whitelisted on the Arukereso side, every request will fail with an authentication error.
30-day max window: Arukereso's GenerateExport enforces a maximum 30-day window per export. Clarisights pulls today + last 30 days on every refresh; longer ranges are split into 30-day chunks. Older historical data requires a support backfill.
CSSONLY requires Google CSS enrollment: If your shop is not enrolled in the Arukereso Google CSS Program, the CSSONLY data source will be unavailable and is silently skipped (only AKONLY data flows). Other CSSONLY errors (rate limits, auth, server errors) are not skipped — they retry and surface like any other error.
No campaign / ad-group / ad level: Arukereso does not expose a campaign concept. Per-product data is stored at the Campaign level in Clarisights.
Two metrics only: Arukereso exposes clicks and click cost. Impressions, conversions, and revenue are not available.
Currency & timezone are user-declared: The Arukereso API does not return currency or timezone. The values you enter on connect drive how Clarisights interprets the data — double-check both before connecting.
Rate limits: 5 GenerateExport / 20 ListExport / 20 Download requests per minute, enforced by Arukereso. Backfills run within these limits automatically.
Operating notes
Refresh schedule: daily.
Lookback: last 30 days re-pulled on every refresh, so late-arriving Arukereso updates are picked up automatically.
Async export flow: Each refresh calls GenerateExport to start a CSV export, polls ListExport until the export is ready, then downloads the file — one cycle per (date window × Data Source) pair.
Multi-account: each Api-Key connects exactly one Arukereso merchant. Add multiple connections to onboard additional shops.
Currency conversion: spend is stored in your declared currency and converted by Clarisights to your reporting currency on ingest.
Credential rotation: rotate the Arukereso Api-Key in Integrations → Arukereso → Edit Credentials. The static key has no built-in expiry — rotate when your Arukereso account manager re-issues one.
Need help?
When contacting support from the in-app messenger, please include:
The integration name and shop name (Integrations → Arukereso)
The exact error message or screenshot
The step where the issue occurred
When the issue started