Skip to main content

​
routing_strategy 0 (RoundRobinStrategy)

In RoundRobinStrategy all your emails are fairly shared between all your IPs and TPSPs The payload for routingMetaData for RoundRobinStrategy is: For example, if you have IP 3.238.19.86 and TPSPs Sendgrid and Mailgun and send 6 emails then 2 emails will be sent from 3.238.19.86, Mailgun and Sengrid.

​
routing_strategy 1 (EmailProviderStrategy)

In the EmailProviderStrategy we can assign IPs and TPSPs to the specific email provider. Existing email provider types: JsonPayload example:
On the left side, you can see the email types: 0 is Gmail, 1 is Yahoo, and ‘others’ in this case all email addresses that don’t belong to Yahoo or Gmail, the left side key is in the string format. Currently, for the right side, the format is an Array of strings in the format of “Entity_ID”. Where ‘Entity’ could be ‘IP’ or ‘TPSP’ (third-party sending provider). For example, the ‘IP_’ prefix means that the entity is IP, and 100 in “IP_100” mean that the ID of this IP is 100. For example, the ‘TPSP_’ prefix means that the entity is TPSP, and 101 in “TPSP_101” mean that the ID of this TPSP is 101. The metadata above means: that for Gmail we send emails fairly between IPs with ID 105 and ID 100; and for Yahoo, we send emails from TPSP with ID 101; and for all the rest email types we send fairly from the TPSP with ID 103 and from IP with ID 104 and 102.

​
routing_strategy 2 (VolumePercentageStrategy)

In the VolumePercentageStrategy we can assign volumes to the specific IPs and TPSPs. JsonPayload example:
Currently, for the left side, the format is a string in the format of “Entity_ID”. Where ‘Entity’ could be ‘IP’ or ‘TPSP’ (third-party sending provider). And for the right side, the volume number of emails that we send (also in the string format). For example, the ‘IP_’ prefix means that the entity is IP, and 100 in “IP_100” mean that the ID of this IP is 100. For example, the ‘TPSP_’ prefix means that the entity is TPSP, and 101 in “TPSP_101” mean that the ID of this TPSP is 101. The metadata above means: that, for example, if we send 20 emails, 4 go from IP with ID 100, 6 go from IP with ID 101, 2 go from TPSP with ID 102, and 8 go from TPSP with ID 103.

​
routing_strategy 3 (SendingDomainStrategy)

In the SendingDomainStrategy we can assign IPs and TPSPs to the specific domains that we are sending from. JsonPayload example:
On the left side, you can see the domains, in this case, it’s sendx.io and sendpost.io, and ‘others’. The email would be put in the ‘others’ category if its domain doesn’t belong to sendx.io or sendpost.io. Currently, for the right side, the format is an Array of strings in the format of “Entity_ID”. Where ‘Entity’ could be ‘IP’ or ‘TPSP’ (third-party sending provider). For example, the ‘IP_’ prefix means that the entity is IP, and 100 in “IP_100” mean that the ID of this IP is 100. For example, the ‘TPSP_’ prefix means that the entity is TPSP, and 101 in “TPSP_101” mean that the ID of this TPSP is 101. The metadata above means: that, for example, if we send emails from t1@sendx.io, t2@sendx.io, t1@sendpost.io, t1@gmail.com, t2@gmail.com, t3@gmail.com, t4@yahoo.com The sendx.io emails (t1@sendx.io, t2@sendx.io) will be sent from TPSP with ID 100 and IP with ID 105. The sendpost.io emails will be sent from IP with ID 101. The ‘others’ emails (t1@gmail.com, t2@gmail.com, t3@gmail.com, t4@yahoo.com) will be sent from IP with ID 102 and 103, and TPSP with ID 104.