Skip to content

Revenue Tracking

Revenue tracking allows you to attribute orders and revenue to specific campaign emails, drip series emails, or workflow automation emails. This is accomplished through a tracking mechanism that follows users from email clicks through to order completion.

How It Works

  1. Lindris automatically adds a unique revenue tracking hash as a query parameter (_ls) to all links in your email messages
  2. When recipients click these links, they are redirected to your site with the tracking hash
  3. The JavaScript tracker stores this hash in a cookie (valid for 30 days from the most recent click)
  4. When using one of our e-commerce integrations and an order is created, the tracking hash is included in the order event data
  5. Lindris uses this data to attribute revenue to the original email source

Implementation

JavaScript Tracker

Ensure the Lindris JavaScript tracker is installed on your website. The tracker automatically handles storing the _ls parameter in a cookie (lindris_pr).

Go to the JavaScript Tracker page for more information.

API Integration

When sending order events to Lindris, include the revenue tracking hash if available.

See the Order Events endpoint for more information.

Revenue Attribution

Orders are attributed based on the following rules:

  1. If a tracking hash is present in the order event, the revenue is attributed to the corresponding email source (campaign, drip series, or automation)
  2. The tracking cookie has a 30-day lifetime from the most recent tracked link click, allowing for attribution of purchases within that window
  3. If multiple tracking hashes exist, the most recent one is used
  4. Orders without a tracking hash are recorded but not attributed to any email source

Attribution Window Behavior

  • The revenue tracking cookie (lindris_pr) expires 30 days after it's set
  • Each time a user clicks a new tracked email link, the cookie is renewed with a fresh 30-day expiration
  • Both the tracking cookie and the user identifier cookie are required for attribution
  • Example: A user clicks an email link, then clicks another email link 25 days later, and makes a purchase on day 50 - the purchase will be attributed to the second email (because the cookie was renewed on day 25)

Viewing Revenue Data

Revenue data can be viewed in several places in the Lindris:

  • Overview Dashboard
  • Campaign Reports
  • Drip Series Reports
  • Workflow Automation Reports
  • Single contact pages