Revenue Attribution for Email

Overview

By taking advantage of revenue attribution, you can analyze message performance based on the order revenue the message generated.

Revenue is attributed to purchases made within 24 hours of the most recent click on a tracked message link. Should 24 hours pass without a purchase, the attribution window will close but can be retriggered if the link is clicked once again. The 24-hour attribution window can be retriggered in this manner for up to 30 days of message send date.

Cordial attributes orders to messages using the message contact ID (mcID). Learn more about message ID's.

Viewing Revenue Attribution

Revenue attribution can be viewed on the platform dashboard page as a total of all sent messages, or on individual message performance pages. You are also able to use revenue attribution as a conversion metric for experiments in batch and automated messages.

Revenue Attribution Displayed on the Cordial Dashboard

Revenue Attribution Displayed on the Message Performance Page

Revenue Attribution as a Conversion Metric

Implementing Revenue Attribution

Revenue attribution can be implemented using Javascript listeners or API calls. Below are some example scenarios.

Revenue Attribution Using the Javascript Listener

This scenario assumes that the web site contains the Javascript listener passing orders to Cordial using the cordial.order method.

1. An email 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 web site containing the contact ID (cID) and the mcID.
4. The contact places a 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.

Revenue Attribution Using an API Call

This scenario assumes that the web site 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 web site 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.