I can QA it within the hour, but "make sure it's fine" needs the email itself and what each link should do. I need three things:
- The email exactly as written: subject, preview text and body, with personalization tags as they appear (for example a first name tag). I check each tag for a fallback so no line reads with a blank.
- Every link: its label, the URL as written, and where it should go. Without the intended destination I can only mark a link 'intent unknown'.
- Your email platform. Fallback syntax and how test sends behave differ by platform; my sources cover Klaviyo only.
Optional: - Required tracking parameters (for example utm_source). Default: none, tracking not checked. - Daily volume to Gmail addresses. Default: unknown. Gmail requires one-click unsubscribe from senders above the volume in the table below; under it, I'll ask.
| Rule | Value | Source |
|---|---|---|
| Gmail sender volume needing one-click unsubscribe | over 5,000 messages a day | https://support.google.com/a/answer/81126 |
A test send can't confirm everything: in Klaviyo, test recipients see the preview profile's data, and unsubscribe links are placeholders, so those need a live test.
I check content, not inbox placement. The send stays held until every issue is fixed or you accept it.