---
url: https://superduperai.co/library/hook-ab-test-campaign-links/
title: A/B test hooks with campaign links: judge after a week on installs, not views
description: The creator-growth method: same video, different hook, one store campaign link per variant, installs per campaign read after a week. Includes the iOS ct= link shape and the noise rule.
category: hooks
platforms: [tiktok, reels, shorts]
works_with: [manual, claude-code, any-llm]
tags: [hook, ab-test, campaign-link, measurement, installs, app-store, growth]
difficulty: intermediate
verified: false
created: 2026-11-01
skill: creator-growth
---

# A/B test hooks with campaign links: judge after a week on installs, not views

The creator-growth method: same video, different hook, one store campaign link per variant, installs per campaign read after a week. Includes the iOS ct= link shape and the noise rule.

## Prompt

```text
Set up a hook A/B test for {app} on {platform}.

1. One body, two or three hooks. Cut the same 20-40 s body and prepend each hook variant (0-3 s). Nothing else changes: same caption, same posting hour, same account.

2. One campaign link per variant. iOS:
https://apps.apple.com/app/apple-store/id{APP_ID}?pt={PROVIDER_ID}&ct={platform}-{account}-{hookA}&mt=8
The ct value is at most 40 characters; use a short code per hook (hookA, hookB). Android: the Play store link with &referrer=utm_source%3D{platform}-{account}-{hookA}. Put the link in the bio or the pinned comment and change it when the variant changes, or run each variant from its own account if you have niche accounts.

3. Post each variant on a different day at the same hour, then repeat so each hook has 2-3 posts. A single post is one data point and one data point is weather.

4. Judge after a week. Read installs per campaign in App Store Connect under App Analytics, Sources (iOS) or the Play Console acquisition report by referrer (Android). Views are attention; installs are the result. A hook that wins on views and loses on installs lost.

5. Noise rule: at small volumes, percentage swings are noise and multiples are findings. A hook with 2x the installs of the other on the same views is a result; a 20 percent difference is a coin toss. Keep both and run another week.

6. Write down the winner, its installs and views, and the loser's, in one line, dated. The next test starts from the winner.

Return: a table (variant, hook text, ct code, full link, post dates), and the one-line result template to fill after the week.
```

## Steps

1. Build the campaign links before you shoot. The ct code goes in the filename of the variant so the edit and the link never get swapped.
2. Post variants on different days at the same hour; repeat so each has 2-3 posts.
3. After 7 days, read installs per campaign, not views. Write one dated line with the numbers.
4. If one variant has a multiple of the other's installs, it won. If the gap is a percentage, run another week.

## Example

App: a photo app for sellers. Platform: TikTok, account @cleanlisting.

| Variant | Hook | ct | Link | Post dates |
|---|---|---|---|---|
| A | Listing photo. Two taps. On the phone. | tt-cleanlisting-hookA | https://apps.apple.com/app/apple-store/id{APP_ID}?pt={PROVIDER_ID}&ct=tt-cleanlisting-hookA&mt=8 | Mon, Thu |
| B | Stop editing product photos on a laptop. | tt-cleanlisting-hookB | ...&ct=tt-cleanlisting-hookB&mt=8 | Tue, Fri |
| C | It's 11 pm and you have forty photos to list. | tt-cleanlisting-hookC | ...&ct=tt-cleanlisting-hookC&mt=8 | Wed, Sat |

Result line template: '{date}: hookA {installs}/{views}, hookB {installs}/{views}, hookC {installs}/{views}. Winner: {letter} by {multiple}x on installs. Next: {what changes}.'

Example filled, with made-up numbers for the shape only: '2026-11-08: hookA 14/9,200, hookB 6/11,000, hookC 15/7,400. hookC and hookA within noise of each other, both over 2x hookB on installs. Next: keep A and C, test a new B.'

## Tips

- Views tell you the hook worked on strangers. Installs tell you it worked on the right strangers. The creator-growth skill's trigger for paying creators needs both: a view threshold you set (it suggests 100k as an example) and a campaign link that shows installs.
- Do not kill a hook over a 20 percent week. The rule in the skill is that at small volumes only multiples count.
- In Claude Code, `/creator-growth` writes the measurement setup into docs/marketing.md with one link per platform and account; this entry is the per-hook version of that.

## Works with

- By hand: No tool needed: a checklist or a technique.
- Claude Code: Runs as a skill or a prompt in the terminal; can read your files and write the result.
- Any LLM: Model-agnostic: Gemini, Mistral, a local model.