Pre-send check
Before a campaign is sent or scheduled its content is checked automatically: brand guide, banned phrases and phishing, links, personalization (Liquid) errors and KVKK/İYS rules. Available on every plan…
Before a campaign is sent or scheduled its content is checked automatically: brand guide, banned phrases and phishing, links, personalization (Liquid) errors and KVKK/İYS rules. The check is available on every plan (ADR-0089).
How it works
- The Review step of the campaign editor fetches the report automatically. Check links too also requests the links to find broken ones.
- The same check runs again on send or schedule (without requesting links). If there is a critical finding the request
stops with
409 HS_CONFLICT(details.reason = preflight_blocked, full report indetails.report). - If the person reviewing the report gives explicit approval (
preflight_ack=true) the action continues; the approval is written to the audit log (campaign.preflight_acknowledged) and to the campaignpreflightsummary (acknowledged_by,acknowledged_at). - With the approval flow enabled, the approver also sees the critical findings and approves explicitly. A campaign with critical findings cannot be approved from Slack; approve it in the dashboard.
Warnings and notes never stop sending; they only appear in the report.
Rules
| Category | Code | Severity | Description |
|---|---|---|---|
| Brand guide | brand_name_casing | warning | The brand kit name is written differently (for example PUSHIZO). |
| Brand guide | off_brand_color | note | A color in the email HTML outside the brand palette and greys. |
| Brand guide | off_brand_font | note | A font in the email HTML other than the brand font. |
| Banned phrase | banned_phrase | critical | A phrase from the banned list in the organization AI settings. |
| Banned phrase | phishing_term | critical | A phrase from the platform phishing list (asking for passwords, card details, etc.). |
| Links | link_unsafe_host | critical | javascript:, localhost, a private/internal address. A public IP address is a warning. |
| Links | link_broken | critical | 4xx/5xx response in the link check (405 is not an issue). |
| Links | link_insecure_http | warning | An http:// link. |
| Links | link_shortener | warning | Shorteners such as bit.ly or t.co. |
| Links | link_unreachable | warning | Timeout or network error. |
| Links | link_invalid | warning | An address that cannot be parsed. |
| Links | link_missing_utm | note | No utm_source parameter. |
| Personalization | liquid_syntax_error | critical | Liquid parse error or a forbidden tag. |
| Personalization | liquid_missing_default | warning | A variable that can be empty for a contact has no default filter. |
| Personalization | liquid_unknown_variable | warning | A variable outside the render scope (for example {{ name }}). |
| Personalization | liquid_undefined_property | warning | The property/tag is missing from a sample of 5,000 contacts. |
| KVKK/İYS | iys_sms_filter_informational | critical | A commercial campaign with the Netgsm SMS channel on the İYS informational filter. |
| KVKK/İYS | sms_missing_opt_out | warning | The commercial SMS body has no opt-out instruction (RET, İPTAL, STOP). |
| KVKK/İYS | email_missing_postal_address | warning | No postal address in the email channel settings for a commercial email. |
| KVKK/İYS | send_time_outside_hours | warning | Sending outside 08:00–21:00 in the app time zone (when quiet hours are not set). |
| KVKK/İYS | commercial_no_category | note | A commercial campaign without a preference category. |
Campaigns of type transactional are not commercial messages; KVKK/İYS rules do not apply. The unsubscribe link in the
email footer is always added automatically.
API
Report (every plan; dashboard and public API):
curl -X POST "https://api.pushizo.com/v1/apps/$APP_ID/campaigns/$CAMPAIGN_ID/preflight?check_links=true" \
-H "Authorization: Bearer $PUSHIZO_API_KEY"The response has a summary (critical, warning, info, blocked) and a findings list. Finding text is given as a
code; params are only short values that locate the issue:
{
"summary": { "critical": 1, "warning": 2, "info": 1, "blocked": true },
"findings": [
{ "code": "banned_phrase", "category": "content", "severity": "critical", "field": "content.contents.tr", "params": { "phrase": "free gift" } }
]
}To send despite a critical finding use POST .../campaigns/{id}/send?preflight_ack=true (the schedule and approve
endpoints take the same parameter). Node SDK: hs.campaigns.preflight(id, undefined, { checkLinks: true }),
hs.campaigns.send(id, undefined, { preflightAck: true }).
Limits
- At most 50 links per campaign are checked; the link check sends an SSRF-guarded
HEADrequest with a 4 s timeout to at most 15 links (redirects are not followed). - The report contains no personal data; property existence is looked up by key name only.
- The check is rule based and does not replace a legal review.
Campaigns
Campaign lifecycle — types (one-time, scheduled, recurring), state machine, audience and content, delivery settings, approval flow, A/B variants, statistics and the public API.
Templates and Liquid
Versioned message templates — creating, versions and rollback, render preview, copying to another app, the template gallery, statistics and Liquid personalization syntax.