How do I import ad spend from a CSV?

At the top of the “Receive costs” section of the data connections you choose the route: connect an ad account (costs then arrive every day on their own), import a CSV file or enter by hand. The routes can be mixed. Below them is the history of your cost imports, once there is one.

Import a CSV file

1. 01Open “Data connections”, go to “Receive costs”, choose “Import a CSV file” and download the template.
2. 02Fill in the required columns kampagne, datum and kosten per row (the English names campaign, date and cost work too). Optional are waehrung (left empty, your account’s reporting currency applies), impressionen and klicks. Reports convert costs in another currency at the ECB rate of the cost day. If the figures come from an ad platform, enter it in the “plattform” column (“platform” works too): meta, google_ads, tiktok, linkedin or microsoft_ads.
3. 03Choose the file and click “Check”. The check shows what could be matched and does not store anything yet.
4. 04If that looks right, click “Apply”. Days already recorded for the same campaign are replaced.

Enter by hand

For a single invoice or to correct a day, choose “Enter by hand”: campaign, day, amount and currency, with clicks and impressions optional. A value already stored for that day is replaced. The automatic sync with the ad account does not overwrite a manual entry, not even when you correct a day it created itself.

The platform is optional. With it, the reconciliation shows the figures under their platform (“Meta reports …”), without it in the combined row “Manual entry or CSV import”. The import rejects an unknown platform (“Gogle Ads”) with its line number instead of dropping it: stored silently without a platform, the costs would sit under the wrong row.

From a shared sheet

For channels without their own connection, such as a newsletter sponsorship or an affiliate network, add the address of a sheet you keep anyway under “Connect a sheet”. Metrunio reads it right away and then once a day, with the same columns as the CSV import. “Fetch now” reads it again immediately.

1. 01In Google Sheets: under “Share”, let “Anyone with the link” view the sheet and copy the link from the address bar. The tab named in the link is read. Or publish the sheet as CSV under “File → Share → Publish to web” and use that link. Any other https address of a CSV file works as well.
2. 02Enter the link under “Data connections”, “Receive costs”, “Connect a sheet” and give it a name.
3. 03Metrunio shows right away how many daily rows were written and which campaigns do not exist in Metrunio. Create them or name them in the sheet as in Metrunio; from the next fetch on, their costs come along.

• Manual entries stay. Otherwise, for the same campaign and day the value read last applies, also over a connected ad account. So only put channels without their own connection in the sheet.
• Rows that disappear from the sheet stay in Metrunio. Enter a correction in the sheet as a new value.
• Anyone who knows the link can read the sheet. Metrunio therefore stores the address encrypted, like an access credential, and after connecting only shows its start and its last four characters.
• Ideally, create a separate sheet or export for Metrunio with only the columns the import needs. We only take over the intended columns; when the file is fetched, further columns may still be transferred temporarily.
• At most 2 MB are read, and only addresses reachable from the internet. If the address shows a sign-in page instead of the sheet, it is not shared; the card says so, and the costs read so far stay.

Instead of a file: the interface

For an ad server, a DSP, an affiliate network or an agency’s reporting there is a second route: POST /v1/server/costs with your server key. One row per campaign and day, daily instead of monthly. The response counts what arrived, what was written and what could not be matched to a campaign. The latter is skipped, not guessed. Figures entered by hand stay as they are. If the figures come from one of the five ad platforms, for instance from an agency’s reporting, state platform per row; for an ad server or a DSP leave the field out. One request carries at most 500 rows. The fields are documented in docs/INTEGRATION-SERVER-API.md. With platform, the platform’s card under “Ad platforms” then shows “arriving” and the route next to “Receive costs”, even without a connected ad account. The same API accepts per-ad costs with the creative level; the fields are listed in the article “How do I evaluate individual Meta and Google Ads ads?”.