PushizoDocs
Messaging & campaigns

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

  1. The Review step of the campaign editor fetches the report automatically. Check links too also requests the links to find broken ones.
  2. 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 in details.report).
  3. 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 campaign preflight summary (acknowledged_by, acknowledged_at).
  4. 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

CategoryCodeSeverityDescription
Brand guidebrand_name_casingwarningThe brand kit name is written differently (for example PUSHIZO).
Brand guideoff_brand_colornoteA color in the email HTML outside the brand palette and greys.
Brand guideoff_brand_fontnoteA font in the email HTML other than the brand font.
Banned phrasebanned_phrasecriticalA phrase from the banned list in the organization AI settings.
Banned phrasephishing_termcriticalA phrase from the platform phishing list (asking for passwords, card details, etc.).
Linkslink_unsafe_hostcriticaljavascript:, localhost, a private/internal address. A public IP address is a warning.
Linkslink_brokencritical4xx/5xx response in the link check (405 is not an issue).
Linkslink_insecure_httpwarningAn http:// link.
Linkslink_shortenerwarningShorteners such as bit.ly or t.co.
Linkslink_unreachablewarningTimeout or network error.
Linkslink_invalidwarningAn address that cannot be parsed.
Linkslink_missing_utmnoteNo utm_source parameter.
Personalizationliquid_syntax_errorcriticalLiquid parse error or a forbidden tag.
Personalizationliquid_missing_defaultwarningA variable that can be empty for a contact has no default filter.
Personalizationliquid_unknown_variablewarningA variable outside the render scope (for example {{ name }}).
Personalizationliquid_undefined_propertywarningThe property/tag is missing from a sample of 5,000 contacts.
KVKK/İYSiys_sms_filter_informationalcriticalA commercial campaign with the Netgsm SMS channel on the İYS informational filter.
KVKK/İYSsms_missing_opt_outwarningThe commercial SMS body has no opt-out instruction (RET, İPTAL, STOP).
KVKK/İYSemail_missing_postal_addresswarningNo postal address in the email channel settings for a commercial email.
KVKK/İYSsend_time_outside_hourswarningSending outside 08:00–21:00 in the app time zone (when quiet hours are not set).
KVKK/İYScommercial_no_categorynoteA 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 HEAD request 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.

On this page