--- title: "Calendar insights" slug: "calendar-insights" updated: 2026-11-17T16:37:30Z published: 2026-11-17T16:37:30Z canonical: "docs.xtremepush.com/calendar-insights" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.xtremepush.com/llms.txt > Use this file to discover all available pages before exploring further. # Calendar insights How the Calendar flags clashes, over-contact and planning gaps, and how to act on what it finds. Sending too much to the same people wears down their attention and can lead them to opt out, and a big fixture with nothing planned is a missed chance. Calendar insights check the dates you are looking at for both, so you can fix problems before campaigns go out. They point out campaigns that reach the same people on the same day, people contacted too often, busy broadcast days, and fixtures or key dates nobody has planned for. Each insight explains why it was raised, and you decide what to do: act on it, snooze it or dismiss it. > [!NOTE] > Planning features > > Everything on this page comes with the Calendar's planning features, an optional extra currently in early access: the insights strip and panel, insight actions, and **Review my calendar**. Contact your account manager to have them enabled for your account. See [Standard and planning features](/documentation/docs/calendar#standard-and-planning-features). ## Open the insights panel The **Insights** strip above the Calendar counts the insights for the dates you are looking at, by severity and kind. Click the strip to open it. It also opens on its own when you run **Review my calendar** or click a day's insight dot. The panel groups its cards by kind, under headings such as **Collisions**, **Frequency** and **Coverage gaps**. Insights only consider sends that will happen: drafts, finished campaigns, behaviour-triggered campaigns, and days already past are left out. ## What insights look for | Kind | Raised when | What you might do | | --- | --- | --- | | **Broadcast days** | Two or more campaigns sending to all users land on the same day, or a broadcast lands on a day when a segment is already heavily contacted | Move one broadcast to a quieter day, or narrow its audience | | **Collisions** | Two campaigns can reach the same people on the same day, through a shared segment, a shared list, or custom audience rules that overlap. The card says how closely the audiences match, for example identical or near-identical, and on how many days both send. A campaign that overlaps several others is shown as one card, for example; [*"Weekend campaign" overlaps 11 campaigns]*. A clash is cleared only when the audiences provably differ, so campaigns using dynamic segments or rules on device fields such as country can still be reported | Check whether both campaigns need to reach those people that day. Move one, exclude the shared segment from one, or dismiss the insight if the overlap is intended | | **Frequency** | A person in a segment reaches your contact threshold (4 by default) within your frequency window (7 days by default), across two or more campaigns. | Space the sends out, or check whether every campaign needs that segment | | **Coverage gaps** | An upcoming fixture in a league you follow has no ticket covering it, and no campaign in the 3 days before kickoff mentions the league or the teams | Create a campaign ticket for the fixture, add an idea to come back to, or snooze the insight if the match does not matter to your customers | | **Key dates** | A commercial moment or one of your team's key dates has no campaign planned on it. *Public holidays are never raised* | Plan a campaign for the date, or dismiss the insight if the moment is not relevant to your brand | Each card has a severity: **Critical**, **Warning** or **Opportunity**. A tenant admin can tune the thresholds for frequency and collisions to match your contact policy; see [Configuring the Calendar](/documentation/docs/configuring-the-calendar#insight-settings). ## How insights are ranked The panel shows the insights most worth your time first. Within each kind, the most severe come first, and among those, the ones reaching more people, happening sooner or repeating on more days rank higher. The list always keeps room for the next few coverage gaps, so clashes don’t crowd out planning opportunities. ## Insights on the grid Days with insights carry a dot in Month view: red for critical, amber for a warning, blue for an opportunity. Hover the dot to see how many insights the day has. Click it to narrow the panel to that day; the panel reads **Showing** and the day. Click **Show all days** to see everything again. To narrow the Calendar itself to what insights name, use **Filter > Advisory > Has advisory**. ## Act on an insight | Action | What it does | | --- | --- | | **Open campaigns**, or **Open** and a campaign's name | Opens the campaigns involved, so you can check their details and performance. The button shows how many there are, for example **Open campaigns (2)** | | **Overlapping campaigns** | On a grouped collision, lists each overlapping campaign, how it overlaps (segment, list or custom rules) and on which days | | **Create ticket** | Opens a prefilled ticket. For a coverage gap, it is the same ticket as [creating one from the fixture](/documentation/docs/planning-from-the-calendar#create-a-campaign-ticket-from-a-fixture); for other insights, a Campaign ticket on the insight's first day with the reason in its plan. Needs Work Trafficking | | **Add idea** | Saves a campaign idea on the day, for example for a coverage gap you want to plan for later | | **Ignore** *segment* | Stops a segment causing clashes and frequency warnings, for example a segment that contains every customer. Tenant admins only. *(Ignore is only offered on Collision and Frequency insights)* | | **Snooze** | Hides the insight until a day you choose under **Back on**, up to a year ahead | | **Dismiss** | Hides the insight until what it is about changes, for example a different campaign joins the clash | > [!NOTE] > Dismissing and snoozing > > These apply to your whole team, not just you, and are recorded in the audit log. Any team member can dismiss, snooze or restore an insight. To bring one back, click **Show dismissed**, then **Restore** on its card. ## Review my calendar Use **Review my calendar** at the start of a planning session for a short, ranked list of what to look at first. It asks the Calendar Xpert to look over the dates on screen, pick out what matters most and explain why, and draft ideas for the fixtures nobody has covered. 1. Pick the Xtremepush instance and move the Calendar to the dates you want reviewed. 2. Click **Review my calendar**. The insights panel opens and shows the review's progress as it moves through **Reading your calendar**, **Ranking what matters** and **Writing ideas**. Insights appear as they are ready. When it finishes: - Up to eight insights appear first in the panel under **From the Calendar Xpert**, each with an **Xpert** badge and the Xpert's reasoning. Every one of them refers to an insight the Calendar found or to a real fixture, so the review explains your calendar rather than inventing problems. - Ideas for up to three uncovered fixtures appear on the Calendar as **Assistant ideas**. The review runs only when you ask for it. You can leave the Calendar while it runs and it picks up again when you come back; clicking **Review my calendar** again while one is running shows the same review. If the Xpert cannot be reached, the panel says *The Calendar Xpert couldn't be reached. Try again.* and keeps what it had already found.