Reconciliation
What It Does
Reconciliation lets you import actual cost data from your ad network and have Rinku recalculate campaign costs to match what the network actually charged you.
When you run traffic, Rinku estimates costs based on the rates you've configured. The network, however, charges based on its own click counting — which may differ from Rinku's count due to bot filtering, deduplication, or timing. Reconciliation bridges that gap: you upload a report from the network, Rinku compares spend per zone, calculates a correction coefficient, and applies it so your ROI figures reflect real spend.
How It Works
Reconciliation operates at zone level. Rinku groups your traffic by traffic source (zone) and compares:
- Rinku Costs — what Rinku calculated based on your configured rates
- RC Costs — what the network reports it charged you for that zone
From those two numbers, Rinku derives a correction coefficient:
Coefficient = RC Costs / Rinku Costs
It then applies that coefficient to every click in the zone:
Adjusted Cost = Original Cost × Coefficient
If the network charged you more than Rinku estimated, the coefficient is above 1 and costs go up. If the network charged less, costs go down. The result is an accurate cost figure per zone, which feeds into your ROI and profit calculations.
Before You Import
What to export from your network
Download a report from your ad network for the period you want to reconcile. The file must contain, at minimum:
| Column | Required | Description |
|---|---|---|
| Zone / Source | Yes | The zone ID or traffic source name |
| Clicks | Yes | Number of clicks the network counted |
| Cost | Yes | Amount the network charged for that zone |
| Creative / Ad Group | No | Include if you want zone + creative level breakdown |
The column names in your file can be anything — you'll map them to Rinku's fields during import.
Supported formats: CSV, XLSX
Importing a File
Step 1: Find your campaign
Go to Campaigns. In the campaign list, find the campaign you want to reconcile and click the Upload Stats button in its action row.
Step 2: Upload your file
A modal will open. Select your CSV or XLSX file. Rinku will show you a preview of the first rows so you can confirm the file loaded correctly.
Step 3: Map the columns
Tell Rinku which column in your file corresponds to each field:
| Rinku Field | Maps to | Notes |
|---|---|---|
| Zone / Source | Your zone or source column | Required. Must match the zone identifiers in your campaign traffic |
| RC Clicks | Your clicks column | Required |
| RC Costs | Your cost column | Required |
| Creative | Your creative or ad group column | Optional. Use only if your file and campaign both have creative-level data |
Step 4: Confirm import
Click Import. Rinku queues a background job that:
- Aggregates your file by zone (and creative, if mapped)
- Matches each zone against Rinku's traffic records
- Calculates a correction coefficient per zone
- Applies the coefficient to recalculate costs
Once complete, the task status changes to Completed and your campaign costs are updated.
Reviewing Results
Open the reconciliation task from the Reconciliations tab to see the full breakdown:
| Column | What it shows |
|---|---|
| Source | Zone / traffic source |
| Creative | Creative ID (if used) |
| Rinku Clicks | Clicks Rinku tracked for that zone |
| Rinku Costs | Costs Rinku calculated |
| RC Clicks | Clicks from your network file |
| RC Costs | Costs from your network file |
| Coefficient | RC Costs ÷ Rinku Costs |
Rows are color-coded by how far the coefficient deviates from 1:
- Green — less than 5% variance (normal)
- Yellow — 5–10% variance (worth reviewing)
- Red — more than 10% variance (investigate)
If a zone in your file has no matching traffic in Rinku, it appears as unmatched traffic — this can indicate a zone ID mismatch between your file and what Rinku recorded.
Resetting Reconciliation
If you need to undo a reconciliation import and revert to original costs, click Reset recalculation on the campaign. This removes all reconciliation data and restores every click to its original calculated cost.
You can then re-import a corrected file.
Common Issues
Zone IDs in my file don't match what Rinku shows
The Zone / Source column in your file must contain the same identifier that appears in Rinku's click data. Check Analytics → Group by Source to see how Rinku recorded the zone names, then verify your network export uses the same format.
Some rows show as unmatched traffic
Unmatched rows are zones in your import file for which Rinku found no clicks. Common causes:
- Zone ID format mismatch (e.g.
zone_100vs.100) - The file covers a date range that doesn't overlap with your campaign traffic
- The zone was not part of this campaign
My stats look off after import
Check whether your network export includes a totals row (a summary line at the bottom of the file). Rinku will try to match it as a zone, fail, and mark it as unmatched — but the row still inflates your overall RC Clicks and RC Costs figures, making the reconciliation results unreliable. Remove any totals or summary rows from the file before importing.
The import task shows an error
Open the task in the Reconciliations tab to see the error message. Most errors are caused by:
- A required column not being mapped
- The cost or clicks column containing non-numeric values
- An empty file
Re-upload a corrected file and run the import again.
I imported the wrong file
Use Reset recalculation to revert to original costs, then import the correct file.
Next Steps
- Analytics & Reporting — view reconciled costs in your ROI reports
- Click Verification — inspect individual clicks and cost data
- Get Support — reconciliation questions