A social media experiment library is a shared table where every test your brands run is logged with the same eight fields, so the next brand starts from a result instead of a guess. Build it as one sheet with one row per test, a fixed result format, and a monthly review that promotes winners into brand playbooks. Below is the template and a starter set of tests worth running first.
TLDR: Log every test with the same fields (hypothesis, brand, platform, variable, sample, result, confidence, next action). Run one variable at a time, call a result only when it beats the account's own median by a margin you set in advance, and review the table monthly.
The eight fields every test row needs
Most test logs fail because each brand records results differently. One writes "carousel did better", another pastes a screenshot. Nobody can search either. Fix the shape first.
| Field | What goes in it | Example |
|---|---|---|
| Hypothesis | One sentence, with the expected direction | Carousels beat single photos for product posts |
| Brand and platform | Which account ran it | Brand C, Instagram |
| Variable | The one thing that changed | Format |
| Control | What you compared against | Last 8 single-photo posts |
| Sample | How many posts in each arm | 6 vs 8 |
| Result | Your metric against the account's own median | 1.12x median |
| Confidence | Low, medium or high (rules below) | Low |
| Next action | Adopt, retest or drop | Retest on Brand D |
Keep "result" relative to each account's own median. A 3% engagement rate is great for one brand and weak for another, so raw rates cannot be compared across a portfolio.
Set the confidence rules before the first test
Small accounts produce noisy numbers. Agree the rules once, in writing, so nobody argues after the fact.
- Low: fewer than 5 posts per arm, or a gap under 10% from the median. Log it, do not act on it.
- Medium: 5 to 10 posts per arm and a gap above 10%. Retest on a second brand.
- High: the same direction on two or more brands. Promote it to a playbook.
For scale, in Mydrop's data, even the best format (carousels) ran only 10% above an account's typical post. If your test shows a 40% lift from one post, suspect luck.
Twelve starter tests that are worth the slot
Skip tests the data already answers. In the same Mydrop dataset, hashtag count moved median engagement by at most 5%, so a hashtag test will mostly cost you a week. Start with these instead:
- Carousel against single photo for the same message.
- First-line hook: a number against a question against a statement.
- Caption under 80 characters against 150 or more (short captions ran 9% below median in our data).
- Link in the caption against link in bio.
- Posting between 7 and 9 am against 6 to 8 pm, in the audience's local time.
- Founder or staff face against product shot.
- Native video against a repurposed one with a watermark.
- Call to action: save, send, comment.
- Posting twice a week against four times.
- Alt text written for people against no alt text.
- Customer quote against brand claim.
- Comment-reply within one hour against next day.
One variable per test. If the hook and the format both change, you have learned nothing.
Assign one owner per brand and one librarian
Each brand lead logs their own tests, because they know what else was happening that week (a sale, an outage, a holiday). One person across the portfolio, the librarian, checks that every row is complete and tags duplicates.
Keep the librarian's job small: ten minutes a week. If it takes longer, your fields are too loose.
Run the monthly review in 30 minutes
Pull every row marked medium or high. Sort by next action. Three outcomes only:
- Adopt: write it into the playbooks of every brand where the platform matches.
- Retest: assign it to a second brand with a different audience size.
- Drop: mark it closed so nobody repeats it in six months.
A dropped test is a success. It saves the next team a week.
Let the calendar and the approvals carry the experiment
The library only works if tests are actually scheduled with the right labels. In Mydrop, you can plan the control and test posts for each brand in the multi-brand calendar, tag them with the test name, and route them through the same approval flow as normal content. Results then come from per-post analytics against each account's median, so the "result" column is a copy, not a calculation.
If you are running one brand with no portfolio, the same table works at smaller scale. Our experimentation framework for enterprise teams covers the hypothesis step in more depth.
Start this week with three rows
Do not build the full library. Open a sheet with the eight columns above, pick the three starter tests that fit your brands best, assign an owner to each, and schedule the posts for next week. In 30 days you will have your first medium-confidence result, and the library will have started.




















Google review
Trustpilot review