Setup tab walkthrough | Mintfunnel Help

The Setup tab is where you install tracking, tell Mintfunnel which sites to measure, and decide what counts as a conversion. This article is a field-by-field tour. If attribution is new to you, read How Mintfunnel attribution works first.

The Setup tab is where you install tracking, tell Mintfunnel which sites to measure, and decide what counts as a conversion. This article is a field-by-field tour. If attribution is new to you, read How Mintfunnel attribution works first.

You will find it by clicking Analytics in the left navigation's Analytics section, then opening the Setup tab at the top of the page.

The install snippet

At the top is a copy-paste script tag: the SDK loader. It goes in the `<head>` of every page you want measured. It carries a token unique to your account, so you never enter an API key.

Next to the snippet itself is a Google Tag Manager toggle, which switches it to a GTM-safe format because GTM strips attributes from external script tags and breaks the standard version. Below the snippet is a Send the whole setup to your developer callout: expand it, enter your developer's email address, and click Send instructions. Mintfunnel emails them the snippets and install instructions directly, so you never have to copy anything yourself.

Full instructions: Installing the tracking snippet.

Install verification

Below the snippet is a status pill. Green means the SDK has been seen recently on at least one of your pages. Gray means no heartbeat has arrived in the last hour.

After pasting the snippet, load a page on your own site once. The pill should turn green within a minute. If it stays gray, see the troubleshooting article.

Connected sites

Add every domain and subdomain where the snippet is installed. The SDK only records events when the page's hostname matches one of these entries. That is deliberate: it stops staging and preview environments from polluting your real data, and it is what makes a cross-domain journey, such as `yoursite.com` to `app.yoursite.com`, get measured as one continuous funnel rather than two unrelated visits.

Add the apex domain and each subdomain as separate rows. Use the bare hostname, with no protocol and no path.

Each site counts as one connected data source against your plan. See Connected data sources explained.

Attribution window

The maximum time between a visit and a later action for that action to be credited to the visit.

The default is 720 hours, which is 30 days, and it is also the maximum. Shorten it for short-cycle products using the other presets: 24 hours, 72 hours, or 7 days.

Changes apply to all future matching immediately. Historical events are not re-attributed.

Tracked events

Where you define the onchain and custom actions that count as conversions. Covered in full in Setting Up Tracked Events.

Key events

Where you promote one or more tracked events to your primary conversion, which unlocks cost-per-conversion reporting across every channel.

Usage

Your tracked events for the current month against your plan allowance. It turns amber as you approach the limit and red at 100 percent. Remember that pageviews do not count toward this, only conversions.

Install token

The token in your snippet identifies your account on incoming beacons. If you think it has leaked, for example it was committed to a public repository, click Regenerate install token. A fresh token is issued and the old snippet stops working straight away, so paste the new one onto your site immediately.

Account level versus per campaign

Everything on this tab applies to your whole account: the snippet, your connected sites, and your attribution window are the same everywhere. Per-campaign overrides exist for advanced cases, such as a different attribution window on one Mintfunnel campaign, but if you set nothing, account-level settings apply.

Once the install is verified and your sites are listed, define your conversions in Setting Up Tracked Events, then connect your ad platforms so those conversions push back to them.