Skill Shot
Sponsored
Spring Swing is open. Download Skill Shot and play for a $2,500 purse.
skillshotgolf.com
Play the Spring Swing
$2,500 purse · $10 per attempt
28618 comments9 shares
LikeCommentShare
Mobile Measurement
Maximize your mobile installs, reduce your ad spend.
Apex measures and tracks your mobile app’s installs so you can see where your advertising spend is going. You’ll know what’s driving app installs, and see the users that are engaging to drive real value. Then, we send the enriched data back to your ad platforms to further reduce costs, and maximize ad spend.
No credit card to start.
Measure
Know which ads bring valuable installs.
See which ad, campaign, or Apex Link led to each install. Apex uses the click or link it can verify, then shows the reason and confidence beside the result.
App installs, opens, purchases, and custom events appear beside your website activity in Apex. Choose the customer action that means an install was valuable, and see both the install and what happened next.
Mobile · which ads bring installs
Last 30 days
| Campaign | Spend | Installs | Worth it(first round booked) | Per install | Really caused by the ads |
|---|---|---|---|---|---|
| Meta · Spring Swing | $8,400 | 231 | 9642% | $36.36 | 131 of 231 (57%)really $64.12 per install · proven Sep 8 · opens the test → |
| Meta · Range Finder | $5,100 | 486 | 12125% | $10.49 | |
 Google Ads · Twilight tee times | $4,200 | 495 | 14830% | $8.48 | |
| apex · Range day invite | free | 86 | 4148% | — | not an ad |
| organic | free | 184 | 7139% | — | not an ad |
"Worth it" is the event you starred in Set up Apex (first round booked). “Really caused” only fills in after a test proves it. Attribution shows the same numbers rolled up per network.
Send credited installs back to connected Meta or Google accounts, with a receipt for every send. Your ad platforms learn from the installs Apex measured, while you can see exactly what each one received.
Follow the customer
See the whole story, not one install.
When a customer signs in or you tell Apex who they are, their web visits, app activity, and messages meet on one profile. See the path from the first web visit through the install and the next message.
One customer
- Web visit
- App install
- One profile
- Message
- First round booked
Dana Whitfield's activity
First round booked9/10/2026, 7:40:00 PMIdentify9/10/2026, 7:38:00 PMPick up where you left off9/10/2026, 6:24:00 PMMobile push · Delivered
App install9/9/2026, 6:24:00 PMSpring Swing landing page9/9/2026, 6:01:00 PMShown Book a round first
Page view9/9/2026, 5:58:00 PM/spring-swing · meta / paid social / Spring Swing
Install story
Why Apex credited this install
AdSpring Swing
Click06:02 PM
22m
Install06:24 PM
1d
Signed in07:38 PM
- Saw your adMeta · Spring Swing · Lookalike · golfers 25-44
- Tapped itWed 06:02:00 PMfbclid captured on the click
- Installed 22m laterWed 06:24:00 PMiPhone 15 · iOS 18.1 · click id matched (fbclid)100% confidentInstallheld back from Google Ads
- Signed in 1d laterThu 07:38:00 PMDana Whitfield
When the app is already installed, an Apex Link tells your app which screen the customer meant to open. After a new install, Apex can remember that destination on Android and make a best effort on iPhone. Your app decides which screen to show.
Send one message a day after install to people who haven't signed up, then stop when they do. Mobile measurement tools usually stop at the report. Apex can act on what happened.
Protect your data
Keep suspicious installs out.
See why an install looks suspicious before it reaches your reports or ad platforms. Apex names the rule, keeps the install out of your totals and billing, and never sends it to your ad platforms until you say otherwise. You read the same reason Apex used, not a score with the rule hidden.
Install story
Why Apex kept this install out
AdRange Finder
Click11:02 AM
4s
Install11:02 AM
Rule that flagged this
Click flooding
142 clicks from 38 devices in the last hour on Range Finder — likely click flooding.
Apex kept this install out of your ad numbers, your totals, and your bill. Count it anyway if you know this person, or if a real campaign just got very popular. A rule can trip on a genuine spike.
- Saw your adMeta · Range Finder
- Tapped itWed 11:02:00 AMfbclid captured on the click
- Installed 4s laterWed 11:02:04 AMPixel 8 · Android 15 · click id matched (fbclid)22% confidentheld back from Meta
Count it anyway when you know the person, or when a real campaign just got very popular. A busy day can look like click flooding. Putting it back sends it to the networks and puts it in your totals. That review is in the product, not a paid add-on.
Measure on iPhone
Tell Apple what a valuable install looks like.
Apple shares limited, delayed data when someone declines tracking. If your app uses Apex through Capacitor, choose the event that means an install was worth it and Apex sends Apple the matching signal. Apex checks Apple’s signature and turns the reports into campaign totals you can read.
Apple attribution
SKAdNetwork
See which ads led to iPhone installs, even when people decline tracking, and what those installs did next.
Which ads Apple credited
5attributed iPhone installs
in the last 30 days
in the last 30 days
5 postbacks from 2 networks
- Meta
3 installs
- Google Ads
2 installs
What those installs did next
2
Worth it
First round booked
2
Showed interest
Tournament viewed
1
Opened the app
Installed or opened, then stopped
Your app gives Apple a private value. Apex translates that value back into the events you named, without identifying the person.
5 of 5 postbacks were signature-checked against Apple.
Conversion values and campaigns Prove the lift
Find out which installs your ads actually added.
A standard install report gives an ad credit for an install. It can't tell you whether that customer would have installed anyway. Hold back a group of known customers and compare what both groups do. The gap is what the ads caused.
Who saw what
One campaign. Two honest groups.
Apex randomly kept 20% of known people from seeing this campaign, then compared what both groups did.
Meta · 3 ad setsads off for 1,922
Saw this Meta ad
Download
Saw the ads2,480 people
9.31%installed
231 of 2,480 people
- First round booked
- 3.87% · 96
Held back from this ad
This ad never appeared.
They saw their normal feed. That gives Apex a real comparison for how many installs would have happened without the ad.
20% held back
Held back620 people
4.03%installed
25 of 620 people
- First round booked
- 1.45% · 9
People who saw the Meta ads installed 5.3 points more often than people held back — about 131% more. That gap is what the ads added.
Known people with an email or phone who did not have the app when they were drawn · counting since Aug 14, 2026
- List synced
- 1,922 of 3,100 matched
- Match rate
- 62%
- Ad sets covered
- 3
- Exclusion verified
- Sep 8, 2026
- Washout
- 3 days
- Leaks
- 0 held-back people installed from Meta
- Flagged installs left out
- 10
With a large enough customer list, Apex runs one ad platform at a time and checks that the held back group is really excluded. If that check fails, the result stays blank.
Experiment across screens
Change the website. Measure the app.
Run a website experiment and measure app installs or purchases. Apex shows which page each group saw, who later signed in on the app, and who couldn't be matched. The missing people stay visible, so the result can't look better than the data behind it.
Web experiment · goal in the app
One test, followed across both screens.
Each card starts with the website version a person saw, follows them when they sign into the app, then counts the app result.
Website version
No app banner
skillshotgolf.com
Assigned on the web4,206
1,902 signed into the app
1,144758
264
Installed
13.9% of signed in people
2,304 never signed in · not counted. They stay visible here so the missing match cannot disappear from the result.
Website version
App first banner
skillshotgolf.com
Assigned on the web4,198
1,961 signed into the app
1,183778
341
Installed
17.4% of signed in people
2,237 never signed in · not counted. They stay visible here so the missing match cannot disappear from the result.
Installs live on a device. Apex can only tie a device to a web visit when the person signs in on both. That's the middle step, and it's why this test counts people rather than browsers. 188 signed in people have no device Apex knows yet; they stay visible below.
Keep the lesson
Start the next decision with evidence.
When an experiment ends with a clear result, Apex offers to save it as a Belief. You choose whether to keep it. The next campaign starts with what you already know.
Belief graph · live
IF/THENDEPENDSCONFLICTS12 beliefs
Belief updated
Your move
See what brings valuable customers.
Start free, connect your app, and watch the first install arrive with its source and what happened next. You don't need a sales call to begin.