Skip to content
NewWe ran our own gift through a study. The gift lost, and we published it. Our own study: the gift lost. Read the study →
How it works Studies Pricing Our own study Contact Sign in
Outcome attribution

Find out whether the send led to the booking, the donation or the sale.

Outcome attribution counts the bookings, donations, renewals or purchases that follow a send, and adds them up by study group. It’s included on every study at no extra cost, and you switch it on per study.

Scope your study →How the counting works
How it works

Your systems report the outcome, and we count it by group.

Pick the way that fits how your team already records a booking, a donation or a sale. Each one is set up and revocable by you, with no standing access to your payment system.

Booked calls

Bookings can count themselves

If your study’s button or page links to your cal.com booking page, a call booked from a scanned piece can count automatically. Booked some other way? Log it on the campaign page.

The Webhook path

Your server sends each conversion

Your systems post a conversion to POST /v1/conversions with the anonymous code it belongs to.

The Click-token path

The button carries a signed reference

On a hosted video, we add a signed reference to your next-step link, and your server sends it back with the conversion.

The Identity-Match CSV path

Or upload a file

Match conversions to codes on your side, then upload the file. Nothing to wire up.

What we keep

You see totals for each group, never what one person spent.

SweetNote checks the anonymous code, adds the conversion to its group, and discards the individual amount. No recipient personal data crosses from your systems.

  • Totals onlyReports show group totals, never a per-person amount.
  • A floor on every rateAn outcome shows as a rate only once at least 25 people sit behind it.
  • A fixed windowThe headline reads the first 30 days. Conversions keep counting to day 90 from go-live, then are refused. The link between codes and groups is deleted at day 120.
  • Compared fairlyOn a study with groups, each group’s outcomes are counted against everyone assigned to it, so the comparison stays fair.
Switching it on

It’s included in every study, and it stays off until you choose it.

  • No extra cost, on every study
  • Switched on by you, per study, when you set it up
  • Covered by the DPA’s Outcome Attribution Schedule, which you sign
  • Your notice stays yours: suggested wording below
More detailSuggested notice wording for your recipients, and the one optional cookie.

Suggested recipient-facing disclosure

Under the DPA Outcome Attribution Schedule § 10, any disclosure your privacy policy or the law requires about conversion measurement is yours. This wording is optional; you remain responsible for your notice, and counsel review is recommended.

“When you respond to one of our mailings or gifts by scanning its code, our measurement partner SweetNote helps us understand whether that outreach led to a donation, purchase, or registration. If you complete one, SweetNote receives only the amount, currency, and time of the transaction together with an anonymous campaign reference, never your card or account details, adds it to group-level totals (minimum group size 25), and immediately discards the individual amount. Measurement stops 90 days after the campaign begins. You can decline measurement on the page the code opens, and we honor the Global Privacy Control signal.”

Swap “donation, purchase, or registration” for your outcome and place it where your notice covers analytics or service providers. This wording is for a study whose code opens a page we host.

For a study that opens your own page, there is no SweetNote page to decline on, so drop the last sentence: use your own site’s privacy notice and link it near the code.

Cookies for outcome attribution

  • None required. None of the three ways to send conversions needs a cookie.
  • The Click-token path. We append a signed sn_ref token to your call-to-action link. If you persist it in a first-party cookie, your server sets it on your domain.
  • SweetNote sets none. No sn_ref or other attribution cookie on your site or the reveal page. The reveal page’s one consent cookie, sn_consent, is unrelated and in the Cookie Policy.
  • The Webhook and Identity-Match CSV paths. No cookie at all, no cookie disclosure.
  • If you use the cookie join, add this row to your cookie table:
CookieSet byPurposeDurationCategory
sn_ref Your own domain (first-party), on behalf of your measurement partner, SweetNote Connects a response to your mailing or gift to a later donation, purchase, or registration, so outcome can be measured in group-level totals (minimum group size 25). Holds only an anonymous campaign reference, never a name, card, or account details. 90 days First-party · Analytics / marketing
  • Declines and GPC. A decline on the reveal page or a Global Privacy Control signal means no sn_ref is written.
  • Own-page studies. No sn_ref is ever appended, so the row never applies. Outcomes come from your own records, by file or from your systems.
  • Persisting it. Server-set, HttpOnly, 90-day Max-Age. A JavaScript cookie capped at seven days by Safari ITP silently breaks delayed conversions. Detail in the Schedule § 10.

Wiring it up?

Send questions about your conversion source or your notice through the contact form. Security posture, retention and subprocessors are on the security page.

Count what your next send actually earned.

Price a study in two minutes and switch outcome attribution on when you set it up.

Scope your study →Book 15 minutes