WLI: Redirect Parameter

🔗Deep-Linking into Metricool

Every autoin URL accepts an optional redirect query parameter that sends the end user straight to a specific section of Metricool once the auto-login completes, instead of landing on the default view.

The same URL works two ways: as an iframe's src, loading that section inline, or as the destination of a plain button or link, taking the user there on click. It can point to virtually any function inside the app, which you have listed here.

How the redirect parameter works

An autoin URL has the shape:

https://app.metricool.com/autoin/[AUTOIN_TOKEN]?redirect={destination}

The autoin token identifies the brand the link logs into; redirect is what decides which screen opens after that login happens. Its value can be either of two forms:

• A short keyword the app resolves to a fixed destination (e.g. planner).

• An app-relative path, the same one you'd see in the browser's address bar while navigating Metricool manually (e.g. /brand-connections).

redirect can be combined with other query parameters understood by the destination it points to — the next two examples show one of each form.

Example 1: Opening the scheduler directly

This embeds the calendar view by pointing the iframe straight at the planner, skipping Metricool's default landing screen:

<iframe
    src="https://app.metricool.com/autoin/[AUTOIN_TOKEN]?redirect=planner"
    referrerpolicy="origin"
    allow="camera; microphone"
    sandbox="allow-same-origin allow-scripts allow-popups allow-forms"
    style="width: 100%; height: 800px; border: 0; display: block;">
</iframe>

The end user never sees Metricool's own navigation — the iframe opens directly on the scheduling calendar, matching the "Schedules" tab in the host app.

Example 2: Opening brand connections for specific networks

index.html uses the same mechanism to link straight to the network-connection screen, further scoped to a set of networks with the networks parameter:

<a
	href="#"
	data-url="https://mciframe.marketingadvisers.co.uk/autoin/[AUTOIN_TOKEN]?redirect=/brand-connections&networks=facebook;instagram;facebookads"
	>My Socials</a
>

Here redirect carries an app path (/brand-connections) rather than a keyword, and networks — a semicolon-separated list of network identifiers — pre-filters that screen to only the networks the host app wants to offer the user.

Using redirect on buttons and links, not just the iframe src

The autoin URL is a plain link, so it isn't tied to a static iframe — anywhere your app can put an href or set an iframe's src dynamically, you can use one.

1. Full-page navigation. Set the URL as a normal href (optionally with target="_blank") and clicking it opens Metricool, already authenticated, on the destination redirect points to.

2. Loading the destination into an existing iframe. index.html takes this route: the "My Socials" link isn't a real navigation link. It stores the autoin URL in a data-url attribute, and a shared click handler loads it into the app's single content iframe instead of following the link:

   sidebarLinks.forEach(link => {
       link.addEventListener('click', (event) => {
           event.preventDefault();
           const newUrl = event.target.getAttribute('data-url');
           if (newUrl) {
               iframe.src = newUrl;
           }
       });
   });

   This is what makes it a redirect on a button rather than an iframe hardcoded to one destination: the same sidebar, the same iframe, but each entry swaps in a different redirect value on click.

Redirecting to any Metricool function

redirect isn't limited to planner or /brand-connections — any route Metricool's own interface navigates to while you're logged in can be used the same way, because the parameter simply reuses the app's internal routing rather than a fixed, curated list of destinations.

To find the value for a section that isn't documented yet, browse to that section inside Metricool with a normal session and copy the path shown in the address bar; that path is what you pass as redirect on your autoin link, adding any extra query parameters that section itself supports (as brand-connections does with networks).

Additional Resources: