SMS Campaign Metrics
SMS Sends include any time Iterable passes the message content to the SMS carrier, Twilio. If the content is accepted, Iterable receives a success code and marks that as a Send.
This metrics is equivalent to 'SMS Sends minus SMS Bounces'.
If an SMS is sent to a malformatted phoneNumber, if a misformed URL in used the 'Image Url' field, if the phoneNumber you're sending to isn't valid, if the user you're sending to has replied 'STOP' in the past, or a variety of other reasons, the SMS send will Bounce.
Users will not automatically be unsubscribed if the SMS bounces.
- To check if a phone number is valid, use Twilio's free lookup tool
- Formatting your phoneNumber? Learn more about setting up SMS
- Where can I see the error code of the bounce?
- On the user's profile. Under the SMS Bounce event, expand the 'smsProviderResponse' object.
- You can then use that error code and search to find out what that Twilio error code responds to.
If a user texts back one of the opt-out words, such as STOP, BLOCK, CANCEL, STOPALL, UNSUBSCRIBE, QUIT, or END, two actions will happen in response.
- Twilio will put that user on a list that will prevent you from sending to that number again.
- Iterable will unsubscribe the user from the Sending Channel (the SMS channel)
Note that re-subscribing the user to the SMS Channel manually in Iterable will not allow the user to receive SMS messages from you, because Twilio also keeps that user on a blacklist. The user will also have to respond with START, YES, or UNSTOP to begin receiving messages again.
If a user responds with one of the opt-out words, that unsubscribe will not automatically be attributed to a campaign.
Metrics related to Purchases or Custom Conversion metrics work the same way they do with Email campaign, except for the method of grabbing the campaignId or templateId.
If a Purchase event of a Custom Event is sent to Iterable and includes the campaignId or templateId field, Iterable will attribute the Purchase or Custom Event to the appropriate campaign.
Email links work by adding a cookie to the user's browser that allow your website to look at the cookie and grab the included data (email, campaignId, and templateId).
SMS links aren't rewritten, however, so in order to get the campaignId or templateId you would need to include those as a merge parameter when building the SMS template. For example, you might include a link that looks like:
Then your website would need to be set up to expect that parameter and use it when any Purchase events or Custom Events are sent back to Iterable.