Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guide iconUser guide
Developer guide iconDeveloper guide
Admin guide iconAdmin guide
English
  • Русский
  • English
Login
    User documentationGetting StartedFAQAltcraft glossary
      Profiles and databasesarrow
    • Subscription resourcesManaging databasesSubscriber profileProfiles import and data updateScheduled customer data importAutomatic data collectionBulk customers profiles updateDouble opt-in subscriptionSuppression listsProfile relationsProfile history exportProfile exportCreating a static segment based on import resultsHow to open a CSV fileMatchingTypes of fields in the databaseGlobal control groupsSubscription Manager
      Communication channelsarrow
      • Email channelarrow
      • Email: ISP interactions best practicesEmail: sending domain configurationEmail: setting up and using postmastersБыстрый старт
        Push channelarrow
        • Mobile Pusharrow
        • Settings & implementation
            Integrate your app with Altcraftarrow
          • Providers: push message structureProcessing and adding a subscriptionEvent registration
          Web pusharrow
        • Preliminary Settings
            Web browser push configurationarrow
          • Firebase Cloud messagingApple SafariMozilla Services
          Connecting Web Push to a WebsiteTransferring Data to the PlatformWeb Push SDK Methods
            Import of subscriptions from third-party push servicesarrow
          • Migrating push subscriptions from third-party servicesHow to transfer push subscriptions configured for Safari?Migration from OneSignal
      SMS channel
        Creating mailing from scratcharrow
      • EmailSMSWeb PushMobile PushWhatsAppViber*™Руководство: SMS-рассылка через VK NotifyMAX BotMAX GroupNotifyTelegram BotTelegram Group
      Communication Channels WorkflowРуководство: SMS-рассылка через УТШРуководство: push-рассылка через сервис от "Согласие"
      Segmentationarrow
    • Static SegmentsDynamic SegmentsUpdatable Segments
        Segmentation Conditionsarrow
      • Segmentation by Profile dataSegmentation by Interactions with EntitiesSegmentation by Activity of the channelSegmentation by external dataSegmentation by external SQL tablesSegmentation by Profile structure
      Best Send Time (BST)Logical operators "AND" and "OR"Recommendations for working with segments
      Message templatesarrow
      • Working with message templatesarrow
      • Working in the editorEmail-templateSMS templatePush templateMAX templateTelegram templateWhatsApp templateViber™ templateNotify template
        Visual editor for email-templatearrow
      • Visual editor interfaceAdding blocksElements and their settingsCustom blocksStyle managerLayer manager
      Template fragmentsImage galleryContent personalizationCreating tables based on array elementsBlock editor for email template
        Altcraft Variables and Functionsarrow
      • Logical expressions in messagesLoops in messagesMarket variables in templatesUsing the JSONPath functionality
        Dynamic content in messagesarrow
      • Dynamic HTML contentDynamic JSON contentContent from SQL database in templatesDynamic API content
      Importing and exporting a message templateImporting a template from a third-party serviceExporting a template from Pixcraft
      Mailingsarrow
    • Mailings calendarBroadcast mailingsRegular mailingTrigger mailingMultivariate testingMailing testingMailing schedulePlacement mailing
      Campaignsarrow
    • Working with CampaignsLocal control groups (LCG)Audience expansionAudience building
      Automation scenariosarrow
    • Managing scenariosNodes of the scenarioClassic marketing scenariosStep-by-step welcome scenario guideScenario for automatic notification of the managerAbandoned cart scenario
      Marketarrow
    • Market settings
        Productsarrow
      • How to create a product manuallyHow to import a product from a fileScheduled product importProduct and SKU SegmentsPreparing the YML file
      OrdersMarket variables in message templateGuide: how to send an order confirmation email
      Loyalty programsarrow
    • Loyalty programsLoyalty integration with external systemsБыстрый стартBasic loyalty program use casesOrder SegmentsPromotion codes
      Reports and analyticsarrow
    • Channel reportTraffic report
        Summary reportarrow
      • Summary report metrics
      Cohorts reportLifetime reportFunnels reportGoals reportAudience growth reportClick map reportLoyalty programs reportBounces reportUndeliveries reportReport on global control groups
      Integrationsarrow
      • Action hooksarrow
      • Altcraft Action HooksAction hooks event typesAction Hook Message StructureJSON batch request (HTTP POST action hook)Message to RabbitMQ brokerMessage to RabbitMQ exchangerMessage to Kafka brokerTest event
        Integration of third-party services using Albatoarrow
      • Connecting Altcraft to Albato Launching the welcome scenario using AlbatoTransmitting event dataSetting app a trigger mailingEvent registrationGoogle Sheets and Altcraft integration AmoCRM and Altcraft integration
      Facebook Ads Manager™Google Ads AudiencesMAXYandex.Audience™VK Ads™Static segment synchronizationYandex AppMetrica™Tilda™Lpgenerator™WhatsAppViber*™ integrationIntegration scopeData Transmitted During SynchronizationNotify
      Weblayersarrow
      • Formsarrow
      • Create a formForm constructorAppearanceActions after form activationData analyticsBinding data channel and formsConditional logic in forms and surveysNPS testing
        Pixelsarrow
      • Goal customer actions and scoring
        Pop-upsarrow
      • Creating and publishing a pop-upSetting up a popup in the code editorManaging pop-ups manually via scriptPopup analyticsGuide: pop-up for push subscriptionsCase: Creating a pop-up with the "Wheel of Fortune" widgetBasic cases of placing a popup via the Tag Manager
        Tag Managerarrow
      • Configuring and installing Tag ManagerTrigger typesVariables typesLinking a pixel and the Tag manager
      Settingsarrow
    • Account settingsCustom linksVirtual sendersSending policiesAudit journalTags FAQ
        Users, groups and accessarrow
      • Two-Factor Authentication (2FA)
        Connectionsarrow
      • Connection to Facebook Ads ManagerConnection to Google AdsConnecting to Yandex.Audience™Connection to 360dialogConnection to EdnaConnection to Devino TelecomConnection to SMSTrafficConnection to VK Ads™Connection to MTS OmniChannelCustom Authentication ConnectionOAuth2 connectionBasic Authentication connectionToken Authentication connectionConnection to RapportoMAX connectionConnection to Notify
      Attribute settings
      API requests: where to startarrow
    • Import or update a profileTrigger mailing launchEngage profile in scenario
      Changelogarrow
    • v2026.1.76v2025.4.75v2025.4.74v2025.3.73v2025.2.72v2025.1.71v2024.4.70v2024.3.69v2024.2.68.2v2024.1.68
    Documentation archivelibrary
  • Reports and analytics
  • Bounces report

Bounces report

Hard and Soft bounces​

In such cases, when the message cannot be delivered to the recipient, the mail server sends back an error message. There are two types of these errors: Hard bounce and Soft bounce.

Hard bounces are server class errors (5xx). Such errors occur in cases, when sending to the mail server is impossible, for example, the email does not exist. If the server returns a Hard bounce error, the platform changes the profile status to "Hard bounced" and adds the email address to the global supression list. As long as the address is in the global supression list, you will not be able to send a message to it. You can remove an address from the global supression list only in the administration panel in the "Supression list " section .

caution

Email addresses with Hard bounce errors are collected in the supression list located in the administration panel. This should not be confused with the Global suppress list in the user panel.

Soft bounces are sending client errors (4xx). Unlike Hard bounce, Soft bounce does not affect customer subscription statuses. If a Soft bounce is received, the platform tries to resend the message according to resend rules. If the message cannot be delivered, the platform will record a non-delivery event.

The reasons of Soft bounce can be:

  • Subscriber inbox is full
  • Letter attachments are too big for subscriber mail server
  • Email service is temporarily unavailable

This report will allow you to track the number of Email messages that didn't get delivered to recipients the first time. In other words, soft bounces are combined in this report.

Report settings​

To start working on bounces report, you need to select time period and mailing (or "all mailings").

Also, you can use grouping by from domain or IP address that was used for mailing.

Grouping by from domain:

Grouping by IP address

info

You can download the resulting report in MS Excel and CSV format by clicking the Export report button.

Table​

The following information is displayed in the table:

  • email domain that was used for sending mailings;
  • bounce text (reply from provider about customer email temporary unavailable);
  • amount - number of message bounces if one message was sent several times.

To view the full error message, hover over the bounce text. A list of common soft bounce reasons and their descriptions is provided in the table below:

Bounce textDescription
421 Message source blocked temporarily. One or more sender authentication rules matched.Messages from this sender are temporarily blocked due to a failure to meet email authentication rules. This can occur if the sender did not pass SPF, DKIM, or DMARC verification. The sender's From-domain authentication settings should be checked.
421 Service Temporarily UnavailableThe server is temporarily unavailable, potentially due to overload or technical maintenance.
451 Please try again laterA temporary issue on the server side, likely due to overload or maintenance.
451 <<EMAIL>>: Recipient address rejected: Intentional policy rejection, please try again laterThe recipient's email address was rejected based on server policy. This may happen due to incorrect settings on the recipient’s side or if the sender was previously marked as spam.
450 <<EMAIL>>: Sender address rejected: Greylisted for 120 seconds! Please, see <URL>The sender’s address is temporarily rejected due to greylisting. The server temporarily refuses messages from the sender and expects the sender to retry after the specified time. The platform will automatically retry after 120 seconds. If the issue persists after retrying, the sender’s settings should be checked.
info

The Altcraft platform allows an inaccuracy of 0.02% when generating reports.

Last updated on Mar 12, 2026
Previous
Loyalty programs report
Next
Undeliveries report
  • Hard and Soft bounces
  • Report settings
  • Table
© 2015 - 2026 Altcraft, LLC. All rights reserved.