Send date vs event date

A campaign goes out on one day, but the opens, clicks and orders it earns arrive over the days that follow. Send date and event date are the two ways SEINō can date those results. The same events are counted either way. What changes is the day they land on, and that changes what a chart is telling you.

The same campaign, dated two ways

Take a campaign sent on 30 April. It is opened the same day, clicked on 1 May, and leads to one order on 4 May and another on 12 May.

Dated by	30 April	1 May	4 May	12 May
Send date	open, click, 2 orders	—	—	—
Event date	open	click	1 order	1 order

By send date, everything the campaign ever earns is credited to 30 April, the day it went out. By event date, each interaction lands on the day it actually happened, so one campaign’s results are spread across two weeks.

Which one answers your question

The two answer different questions, so neither is more correct.

• Send date answers how did this campaign perform? Everything it earned sits on one day, so you can compare campaigns, templates and A/B tests against each other, and a newsletter’s full lifetime value stays with the newsletter.
• Event date answers what happened in this period? Use it when the calendar is what matters: revenue for a month, daily engagement, website sessions, or any figure that has to reconcile with a report from outside SEINō.

The gap between them is widest right after a send. A campaign that went out yesterday has earned almost nothing by event date, while by send date it already carries everything it will ever earn.

Where you choose

You choose when you choose your data, not afterwards. Campaign data is available both ways, so picking the dataset is usually the whole decision.

Three places carry their own Date field setting: alerts, target plans, and dashboard widgets. There it sets which date drives that one item’s window, whatever the rest of your reporting uses.