Where do I get the advertising platforms’ credentials?

Two places in the portal ask for credentials, both under “Data connections”: the cost sync in the “Receive costs” section and the conversion pushback in the “Return conversions” section. They partly ask for the same values: one Microsoft Advertising developer token covers both.

What each platform needs

Sources at the provider

• Meta: developers.facebook.com/docs/marketing-api/conversions-api/get-started
• Google Ads: developers.google.com/google-ads/api/docs/api-policy/developer-token
• TikTok: business-api.tiktok.com/portal/docs
• LinkedIn: learn.microsoft.com/en-us/linkedin/marketing/conversions/conversions-overview
• Microsoft Advertising: learn.microsoft.com/en-us/advertising/guides/get-started

Sign in instead of copying: Google Ads and Meta

Under “Data connections”, “Connect ad account” in the “Receive costs” section takes you to sign in with Google Ads or Meta; then you pick the ad account from a list. There is no token to copy. The connection exists once you have chosen and confirmed an account; a sign-in without an account expires after one hour. In Meta’s sign-in dialog, sharing ad accounts is optional. If you share none, Metrunio lists none and offers to sign you in again.

• Google Ads: Metrunio stores a lasting grant and uses it to fetch a fresh access token before every call. If you revoke access in your Google account or the connection goes unused for six months, the import reports “Please reconnect”.
• Meta: depending on the setup, the sign-in is valid indefinitely or for 60 days. If Meta names an expiry date, it is shown on the connection (“Access valid until …”), and Metrunio warns you beforehand (see below).
• Reporting conversions to Meta: under “Data connections”, after signing in you pick the dataset (pixel) from the list Meta names for that sign-in. Sharing datasets is optional in Meta’s dialog too: if your pixel is missing, sign in again and share it, or enter its ID by hand. Whether Meta accepts reports to the chosen dataset is what test mode shows.
• One sign-in for both pages: the cost import and the conversion pushback ask the platform for the same permissions. If one of them is already connected through a sign-in, the other offers “Use existing Meta sign-in” (or Google), with no new dialog at the platform; “Sign in with another Meta account” stays next to it. It covers what you shared during the first sign-in: if the ad account or the pixel is missing, the selection that follows offers to sign you in again. An expired Meta token is not reused.
• Sign in again, same account: if cost sync reports “please reconnect” and you sign in again for that connection, Metrunio keeps the previous ad account on its own as soon as it is part of the new sign-in, and requests a fetch right away. The message afterwards names the account; “Choose another account” next to it lets you pick a different one from the same sign-in instead. If the previous account is not part of the sign-in, you choose as for a new connection.
• Switch accounts without a new dialog: if a connection already runs through a sign-in, “Edit” first offers “Choose an account from the existing sign-in”. You then pick another ad account (or, for pushback to Meta, another pixel) from what this connection’s sign-in shares. Next to it, “Sign in with another Google account” (or Meta) covers an account under a different login. The same choice appears in the “Incomplete” warning when a connection is missing its account. Here too, what you shared at sign-in is what counts: if the account you want is missing from the list, sign in again from there.
• Disconnecting is per connection: once reused, each connection holds its own encrypted copy of the authorisation. Disconnect the cost import and the pushback keeps running, and vice versa. If you revoke access at Google or Meta itself, that applies to both.
• What Metrunio does with it: read costs and report conversions. Metrunio does not change campaigns, budgets or ads, even where the platform requires broader permissions for reporting conversions.
• What happens to the data: the authorisation is stored encrypted and only with your workspace. We use the data for your reports, the conversions you report back to your own account and the features you use yourself. It is transferred to the processors we use for this, and to an AI tool or program when you connect it to your account yourself and thereby instruct us to pass your data to it. The authorisation itself, meaning the platform’s access token, never leaves Metrunio, not even to a connected tool. We do not sell the data or combine it across customers. Data received from Google APIs is subject to the Limited Use requirements of the Google API Services User Data Policy. If you disconnect, we delete the authorisation immediately; you can also revoke access at myaccount.google.com/permissions or under “Business integrations” at Meta. The details are in the privacy notice under “Signing in with Google Ads and Meta”.
• TikTok, LinkedIn, Microsoft Advertising: still with a token. Their sign-in requires a separate partner approval each.

Advance warning before access expires

If the platform names an expiry date at sign-in, Metrunio stores that date next to the encrypted authorisation. The authorisation itself stays encrypted. This applies to Meta without “Facebook Login for Business” (about 60 days) and to Google if you limited access in time when signing in.

• 14 days before: the connection shows “Access expires soon” in ochre, with the date. The overview shows a notice you can hide. Everything keeps running until the expiry date.
• From the expiry date: the connection shows “Access expired” in red. No more costs arrive and no more conversions go out. This notice cannot be hidden.
• Reconnect: “Sign in with Meta again” (or Google) on the connection. The previous ad account stays if it is part of the new sign-in, and the new expiry date applies right away.
• Agencies: in the client overview, access that expires soon turns the client ochre, expired access turns it red. The weekly summary email names it with the date.