This article will walk you through the add-on Send Gate and the differences in what we will call old Send Gate and its successor Send Gate Plus. It is for you, who already have an integration using the old Send gate and wants to know the benefits of Send Gate Plus.
Jump over to this article to learn about how to convert from old Send Gate to Send Gate Plus.
If you are new to this functionality, you should not consider integrating old Send Gate since it will overtime be fully replaced by Send Gate Plus.
The Send Gate concept
The scope for this feature (both versions) is to enable an automatic process for transferring contacts included in a sendout from Symplify to other systems. The integrated system can then for example check live consent (and reject individual messages) or for example add promotional codes, tags or other information to those specific contacts in that integrated system.
The main scope is the same for old Send Gate and Send Gate Plus but there are some differences.
General management
The improvements to Send Gate Plus from old Send Gate is to create a wider range of use.
- Send Gate Plus can handle both single entries (API triggered starters) and batch entries (segment triggered), meaning it covers all type of send steps in Journeys and Campaign Manager (note that old campaigns are not compatible with Plus).
Old Send Gate can only manage messages in a batch.
- Send Gate Plus enables different paths (optional) for rejected or timed out contacts, meaning e.g. a separate flow for rejected contacts can be added.
Old Send Gate will simply just push a contact forward on the current path.
- Send Gate Plus offers multiple action tags to use to identify and perform different actions on the customer side. You can also have specific default actions for all sendouts in a projects and add additional actions on sendout level.
Old Send gate only has one field for identifier.
Any identifier on project level will be replaced with an identifier on sendout level if this is added.
Integration
The integrations for both versions are very much alike, but we do find some differences here as well.
- With Send Gate Plus you are only allowed one (1) endpoint on an account (different projects can still have different actions).
Old Send Gate allowed multiple endpoints.
- When Send Gate Plus is running on an account/project, all batches within will be put on hold (not sending) until they get accepted.
Individual messages can be rejected but a batch can not (a batch can only be accepted or ignored)
Old Send Gate has a setting to either put batches on hold (until the integrated system has accepted) or to send them without required acceptance.
- With Send Gate Plus the webhook payload will be slightly different depending on whether the source is a batch generated sendout or single triggered sendouts.
Old Send Gate is not used with single triggered sendouts.