Nesta página: defina datas de início e término e controle de taxa na guia Agendar para que sua campanha acionada pela API envie na hora certa sem sobrecarregar os sistemas downstream.
Use a guia Agendamento para definir o agendamento da campanha.
Definir datas de início e término
Por padrão, as campanhas acionadas pela API começam assim que são acionadas e terminam assim que a mensagem é enviada uma vez. Se você não quiser executar sua campanha logo após ela ser acionada, poderá especificar uma data e hora em que a mensagem deverá ser enviada usando a opção Início da campanha.
A opção Campaign end permite especificar quando uma campanha deve parar de ser executada. Fora das datas especificadas, a campanha não será executada.
Definir controle de taxa
Journey Optimizer permite que você habilite o controle de taxa para ações de saída (email, mensagens móveis, notificações por push).
Esse recurso é particularmente útil para evitar sobrecarga em sistemas downstream, como páginas de destino ou plataformas de atendimento ao cliente. Por exemplo, você pode definir um limite de taxa de 165 mensagens por segundo para garantir uma entrega estável sem sobrecarregar os sistemas de downstream.
Para definir o controle de taxa, habilite a opção Entrega acelerada na seção Configurações de entrega e especifique a Taxa de entrega desejada por segundo.
- Taxa de entrega mínima com suporte: 1 por segundo.
- Taxa de delivery máxima com suporte: 2000 por segundo quando a opção “Throttle delivery” está habilitada.
Próximas etapas next
Quando a configuração e o conteúdo da campanha estiverem prontos, você poderá revisá-los e ativá-los. Saiba mais
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains how to schedule an API triggered campaign with start and end dates in the Schedule tab, and how to set rate control with the Throttle delivery option.
Intents:
- Understand when an API triggered campaign starts and ends by default
- Set a start date and time with Campaign start
- Set an end date and time with Campaign end
- Set a delivery rate per second with Throttle delivery
- Understand which profiles are excluded when the delivery rate is too low
Glossary:
- Campaign start: Option to specify a date and time at which the message is sent
- Campaign end: Option to specify when a campaign stops being executed
- Rate control: Feature that limits the delivery rate of outbound actions, to prevent overload on downstream systems such as landing pages or customer care platforms
- Throttle delivery: Option in the Delivery settings section that enables rate control
- Delivery rate: The number of messages per second specified when Throttle delivery is enabled
Guardrails:
- By default, API triggered campaigns start once they are triggered, and end as soon as the message has been sent once.
- Outside of the specified dates, the campaign is not executed.
- Minimum delivery rate supported: 1 per second (hard limit).
- Maximum delivery rate supported: 2000 per second when the Throttle delivery option is enabled (hard limit).
- When a delivery rate is set, the maximum timeframe for which the campaign audience can execute is 12 hours (hard limit).
- If the delivery rate does not allow all the audience to be sent the message in the 12 hour timeframe, the remaining profiles are excluded from the campaign. The count of these excluded profiles is visible in the campaign report.
Applicability:
- Rate control: outbound actions (Email, Mobile messages, Push notifications)
Terminology:
- Canonical name: API triggered campaign schedule
- Do not confuse: Campaign start (when the message is sent) ≠ Campaign end (when the campaign stops being executed)
FAQ:
- Q: When does an API triggered campaign start by default? — Once it is triggered. It ends as soon as the message has been sent once.
- Q: How do I send the message at a specific time? — Use the Campaign start option to specify a date and time.
- Q: How do I limit the delivery rate? — Enable Throttle delivery in the Delivery settings section and specify the Delivery rate per second.
- Q: What is the supported range for the delivery rate? — From 1 per second to 2000 per second.
- Q: What happens to profiles that cannot be reached in 12 hours? — They are excluded from the campaign, and their count appears in the campaign report.
Examples:
- A rate limit of 165 messages per second ensures steady delivery without overwhelming downstream systems.
Related pages:
- Next step, review and activation: Learn more (campaigns/review-activate-api-triggered-campaign.md)