Troubleshooting Analytics & Attribution

The fixes for the problems people actually hit, in the order they tend to hit them.

Last updated

The fixes for the problems people actually hit, in the order they tend to hit them.

The install status stays gray

The pill turns green once the SDK has been seen on one of your pages in the last hour. If it will not:

  • Hard-refresh the page on your site, with Cmd+Shift+R or Ctrl+Shift+R, to clear cached HTML.
  • Check the SDK loaded. Open your browser's developer console on your site and type `window.mintfunnel.version`. A version string means it loaded. `undefined` means the snippet never ran.
  • If you used Google Tag Manager, confirm you clicked Publish. Saving in GTM does not put the tag on your live site. This is the single most common cause.
  • Confirm the snippet is in `<head>` and that no content security policy or sandbox attribute is blocking it.
  • Check you are testing the live site, not a staging or preview environment.
  • Try a private window with extensions disabled. An ad blocker on your own machine will block the SDK.
  • Confirm the hostname is registered under connected sites. The SDK only records on hostnames you added.

Traffic shows up but wallet connects do not

Expected, until you add one line. The snippet cannot see wallet connections; only your site knows when one happened. You need `window.mintfunnel.identify({ address, chainId })` in your wallet-connect handler. See Installing the tracking snippet.

Once added, do a fresh test connect. A reload of an already-connected session may not fire it, depending on your wallet library.

The connect wallet button does not work on my site

This is not caused by Mintfunnel. The snippet is entirely passive and never touches your connect button. It is almost always a wallet-library configuration problem on your side, most often a missing RPC URL in wagmi or viem. Check your browser console for errors.

Onchain conversions are not appearing

  • Confirm the wallet is attributed. Onchain tracking follows wallets Mintfunnel has already linked to a visit. If the connect was never reported, later onchain activity has nothing to attach to.
  • Check the contract address and chain on the tracked event. A right address on the wrong chain records nothing, silently.
  • Historical transactions are not backfilled. The indexer starts watching when you save the event, so a transaction from before that will not appear.
  • For DEX purchases, use Token purchase rather than Token swap, with the address of the token being bought. The swap type misses most router-based trades.

A custom event is not showing up

The name passed to `track()` must match what you configured, exactly, including case. Then open your browser's network panel and look for a request to `/collect/attribution/v1`. A 200 response means the event was accepted, so the problem is the name rather than the install.

Conversions are credited to the wrong channel

Credit goes to the most recent tagged visit within your attribution window, which defaults to 30 days. If someone arrived through several channels, the last one before converting wins. Adjust the window under Setup & events if that does not match how your funnel works.

Everything lands in direct traffic

Your links are not tagged. Direct is where untagged traffic goes. Mint links through the link builder for every channel you control, and connect the Telegram or Discord bot so your community mints tagged links too. See Connecting Telegram, Discord, Search Console, and Brand Radar.

My numbers are lower than another analytics tool

Expected, and correct. Mintfunnel drops known bots, crawlers, headless browsers, and HTTP libraries before counting anything. Tools that count them report a bigger number that is less true.

A date range snapped to something shorter

You asked for more history than your plan can view. Free sees 30 days, Starter 12 months, and Pro and Enterprise 3 years. Nothing has been deleted: all your data is retained regardless of plan, and upgrading unlocks the older window instantly. See Plans, limits, and add-ons.

I cannot connect another site or integration

You are at your plan's connected data source limit. Disconnect one you no longer use, add an extra source for $10 per month, or move up a plan. Reconnecting or editing something you already have is never blocked, even at your cap. See Connected data sources explained.

I am near or over my event allowance

Nothing breaks. A soft grace of 20 percent applies before ingest is throttled, and you are warned first. Remember pageviews do not count, so if your allowance is filling fast it is conversions doing it, which is usually good news. Add a 5,000-event bundle for $20 per month, or move up a plan.

Conversions are recorded but never reach my ad platform

Usually an expired credential, or an event that is not mapped to that platform. Check the connection under Data sources & integrations > Conversion push (CAPI), then check Conversion mapping. Once the connection is fixed you can replay the conversions that failed to deliver rather than losing them.

Still stuck

Message the Mintfunnel Team from the Support page in your dashboard. Include your site's domain and roughly when you expected to see the event, and we can look at what actually arrived.

Still need help?

Ask Maren about billing, campaign setup, or anything not covered.

Ask the community →