Connect a donation, purchase or registration to the piece that came before it.

Three ways to send conversions

• PathsYour server posts to POST /v1/conversions (Webhook or Click-token), or you upload a file (Identity-Match CSV).
• HandlingSweetNote verifies the join key, adds the conversion to its cohort and variation cell, and discards the per-recipient value. No recipient personal data crosses.
• ControlConfigured and revocable by you. No standing access to your payment system.
• WindowConversions count for 90 days from activation; later ones are rejected. The token-to-cell map is deleted at day 120.
• Floorn ≥ 25 before any Outcome cell shows a rate.
• TermsTurned on at scoping with the DPA Outcome Attribution Schedule.

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.

Cookies for outcome attribution

• None requiredNone of the three ways to send conversions needs a cookie.
• Click-token pathWe 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 noneNo 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.
• Webhook and Identity-Match CSVNo cookie at all, no cookie disclosure.
• If you use the cookie joinAdd this row to your cookie table:

• Declines and GPCA decline on the reveal page or a Global Privacy Control signal means no sn_ref is written.
• Own-page studiesNo sn_ref is ever appended, so the row never applies. Outcomes come from your own records, by file or from your systems.
• Persisting itServer-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.