By taking advantage of revenue attribution, you can analyze message performance based on the revenue a message generated.
Revenue is attributed to purchases made within 24 hours of the most recent click on a tracked message link. If 24 hours pass without a purchase, the attribution window closes but can be retriggered if the link is clicked again. The 24-hour attribution window can be retriggered for up to 30 days of the message send date.
Because push notifications and in-app messages get dismissed, they can only be clicked once—but they still provide 24 hours of revenue attribution.
Cordial attributes orders to messages using the message contact ID (mcID). You can learn more about message IDs here.
View revenue attribution
Revenue attribution is displayed for all sent messages on the Dashboard page when you log in to Cordial.
To view revenue by channel, click the appropriate tab: Email, SMS, or Push.
To view revenue attribution for an individual message, you can find the message’s Summary Performance page by navigating to Messages, selecting the appropriate channel in the dropdown, and selecting the message.
Revenue performance is broken down into the following characteristics:
- Total Revenue: Total revenue attributed to the message(s)
- Direct Revenue: Revenue attributed to the original message recipient(s)
- Indirect Revenue: Revenue attributed to subsequent message recipient(s) (e.g. a promotional email that is forwarded to a friend and leads to a purchase will be tracked as indirect revenue)
- AOV: Average Order Value (Total Revenue/Purchases)
- Purchases: Total number of purchases attributed to the message(s)
Revenue attribution can also be used as a conversion metric for experiments in batch and automated messages.
Direct vs. indirect revenue
Total revenue can be divided into two subcategories for more specific performance tracking: direct and indirect.
Direct revenue is revenue from an order that can be directly attributed to the original recipient. This attribution is available due to the receiving contact’s ID (cID) matching the message contact ID (mcID) in the tracked link. For example, an email is sent to Contact A, who clicks on the tracked link to place an order within 24 hours of clicking the link. The order data is attributed to the email and Contact A via the mcID.
If the indirect revenue feature is not enabled, direct revenue will be shown on the dashboard as Total Revenue.
Indirect revenue is a feature that allows an order to be attributed to a message when the order is placed by someone other than the original message recipient. With this feature enabled, the contact ID (cID) of the person placing the order is not required to match the message contact ID (mcID) in order to be tracked. For example, Contact A forwards an email to Contact B, who then places an order. That order data is attributed to Contact B even though the original message contact ID indicates that Contact A received the email.
The indirect revenue feature must be enabled to display the Direct/Indirect Revenue breakdown on your Cordial Dashboard. This feature is currently only supported in the email channel. To enable indirect revenue attribution, contact your CSM.
Revenue attribution as a conversion metric
Experiments measure message performance using direct revenue.
Implement revenue attribution
1. A message is sent to a contact containing a tracked link to a web page.
2. A contact clicks on the tracked link.
3. A cookie is set on the website containing the contact ID (cID) and the mcID.
4. The contact places an order within 24 hours of clicking the link (using the same browser and computer).
5. Order data is sent to Cordial and attributed to the email using the mcID.
Any orders placed after the mcID cookie expires (24 hours) will not be attributed to the email, unless the contact clicks the tracked link once again and makes a purchase. The mcID is stored in the Cordial database for 30 days. Revenue will not be attributed for purchases made after the 30 day mcID expiration period.
Revenue attribution using an API call
This scenario assumes that the website is passing order data to Cordial using the POST /orders API call.
1. An email is sent to a contact containing a link to a web page. The link is appended with the mcID.
2. A contact clicks on the link with the mcID.
3. The website developer stores the mcID for use in step 5.
4. The contact places an order.
5. A POST /orders API call is made containing the order details and the previously stored mcID.
6. Order data is sent to Cordial and attributed to the email using the mcID.
The mcID is stored in the Cordial database for 30 days. It is not possible to make an API call for attribution after the 30 day expiration period.
Revenue attribution using the Cordial mobile app SDK
This scenario assumes that the mobile app contains the Cordial mobile app SDK.
1. A push notification is sent to a contact.
2. A contact clicks on the tracked link.
3. The mcID is saved by the Cordial SDK.
4. The contact places an order within 24 hours of clicking the push notification.
5. Order data is sent to Cordial and attributed to the push notification using the mcID.
The Cordial mobile app SDK can also automatically attribute revenue to email and SMS links that land in the app. Cordial also supports in-app and inbox messaging attribution with our mobile app SDK. For more developer-centric information, you can learn more about how this is done on Android here, and how it's done on iOS here.
Cordial supports WebView apps for out of the box revenue attribution.
Revenue attribution using an SMS shortened link
This scenario assumes that you have the SMS link shortener set up for your domain.
1. A shortened link is sent to a contact.
2. A contact clicks on the shortened link.
3. A contact places an order on the website within 30 days of receiving the message.
4. Order data is sent to Cordial and attributed to the SMS message using the shortened link.