Storelift
Start measuring

Store campaign link builder

Share a bare store link on social or in a newsletter and you will never learn where the installs came from. Apple and Google both provide parameters for this; most developers don't know they exist. No signup, and nothing is sent to a server.

You invent it. It shows up under App Store Connect › App Analytics › Campaigns with this name. Spaces become hyphens; punctuation and non-Latin characters are dropped.

The number after id in the store URL: apps.apple.com/…/id6790070467

The numeric ID under Payments and Financial Reports in App Store Connect. You can leave it blank — the campaign is still reported, you just lose the provider split. A made-up value writes garbage into the report.

App Store

Enter an App Store ID

Google Play

Enter an Android package name

How it works

  • App Store: `ct` is your campaign name, `mt=8` is the media type (always 8 for apps), `pt` is the provider token. Apple splits all three out in App Analytics.
  • Google Play: the parameters go into a single `referrer` string, and Play Console reads the UTM fields separately — with `utm_source` empty the report says "(not set)".
  • Use the same campaign name on both stores. The reports stay separate, but your comparison becomes possible under one name.
  • Name the campaign after where you posted it ("instagram-august"), not what it said. Which channel produced installs matters more than how many people clicked.

When the numbers arrive: Apple fills in campaign data after installs happen, and a day's data is final two days later. Seeing nothing on the day you publish the link is normal.

The calculation runs in your browser. Your title and keyword list are never sent to any server — handing an unreleased version's keywords to a tool is usually not something you want.

On Storelift's Revenue page we measure what this traffic did on the store side: impressions, product page views and downloads — split by source.

What campaign parameters actually doStart measuring