{"componentChunkName":"component---src-templates-markdown-template-jsx","path":"/guides/data-platform/tiered-events/","result":{"data":{"pageMetadata":{"title":"Tiered Events","path":"/guides/data-platform/tiered-events/","sourceCode":null,"metadataParent":{"title":"Data Platform","path":"/guides/data-platform/","sourceCode":null,"hasVersionPicker":null,"metadataChildren":[{"title":"Trends","path":"/guides/data-platform/trends/","order":1,"label":null},{"title":"Setup","path":"/guides/data-platform/setup/","order":2,"label":null},{"title":"Live Stream","path":"/guides/data-platform/live-stream/","order":3,"label":null},{"title":"Data Catalog","path":"/guides/data-platform/catalog/","order":4,"label":null},{"title":"Rules","path":"/guides/data-platform/rules/","order":5,"label":null},{"title":"Plans","path":"/guides/data-platform/data-planning/","order":6,"label":null},{"title":"Filters","path":"/guides/data-platform/data-filter/","order":7,"label":null},{"title":"Event Forwarding","path":"/guides/data-platform/event-forwarding/","order":8,"label":null},{"title":"Event Match Quality","path":"/guides/data-platform/event-match-quality/","order":9,"label":null},{"title":"Data Retention","path":"/guides/data-platform/data-retention/","order":10,"label":null},{"title":"Tiered Events","path":"/guides/data-platform/tiered-events/","order":11,"label":null},{"title":"Blocked Data Backfill Guide","path":"/guides/data-platform/blocked-data-backfill-guide/","order":12,"label":null}],"metadataParent":{"title":"Guides","path":"/guides/","metadataChildren":[{"title":"Platform Overview","path":"/guides/platform-overview/","order":0.5,"label":null},{"title":"Getting Started","path":"/guides/getting-started/","order":1,"label":null},{"title":"mParticle Agent","path":"/guides/mparticle-agent/","order":1.5,"label":null},{"title":"Oversight","path":"/guides/oversight/","order":2,"label":null},{"title":"Data Platform","path":"/guides/data-platform/","order":3,"label":null},{"title":"Data Warehouse","path":"/guides/data-warehouse/","order":4,"label":null},{"title":"Customer 360","path":"/guides/customer-360/","order":5,"label":null},{"title":"Analytics","path":"/guides/analytics/","order":6,"label":null},{"title":"Audiences","path":"/guides/audiences/","order":7,"label":null},{"title":"Settings","path":"/guides/settings/","order":8,"label":null},{"title":"Troubleshooting mParticle","path":"/guides/troubleshooting/","order":10,"label":null},{"title":"Default Service Limits","path":"/guides/default-service-limits/","order":11,"label":null},{"title":"Glossary","path":"/guides/glossary/","order":12,"label":null}],"metadataParent":null}}},"markdownRemark":{"html":"<p>mParticle collects data from all of your platforms and data connections and uses it to resolve customer identities and stitch together customer profiles. It also makes this data available to be forwarded to downstream systems, and retains it in long-term data stores that allow you to run data replays with help from mParticle Support.</p>\n<p>By default, mParticle makes all data available for evaluation. However, many events and the data related to them may not be needed for running data replays or evaluations depending on how you use Audiences or Calculated Attributes. With Tiered Events, you can choose to collect data but not store it, or to collect and store data but not evaluate it. </p>\n<p>These configurations help improve performance for all customers, and may provide cost savings for <a href=\"/guides/settings/usage\">value-based pricing</a> customers.</p>\n<p><img src=\"/images/guides/platform-guide/tiered-events/tiered-events-overview.png\" alt=\"List of custom events showing tiered events\"></p>\n<p>mParticle provides three event tiers. All three tiers support ingestion and forwarding of data, but provide different levels of support for storage and evaluation:</p>\n<ul>\n<li><strong>Connect</strong>: Data is not stored in mParticle, but can be ingested and forwarded. The data is also used for profile enrichment. Because Connect tier events aren’t stored, they won’t be visible in the User Activity view.</li>\n<li><strong>Preserve</strong>: Events marked as Preserve are ingested, stored, and forwarded but are not used in real-time evaluations for audiences or calculated attributes. The data is still available for replaying to third party tools, and for <a href=\"/developers/apis/http/#upload-multiple-event-batches\">backfills</a> of <a href=\"/guides/customer-360/calculated-attributes/overview/\">calculated attributes</a> and <a href=\"/guides/audiences/create-an-audience/#one-time-audiences\">one-time audience creation</a>.</li>\n<li><strong>Personalize</strong>: This tier is the default for all events and related data collected as part of an mParticle ingestion. Events are ingested, available for evaluation in audiences and calculated attributes, stored, and forwarded.</li>\n</ul>\n<p>The following table can help you decide which tier to apply to data:</p>\n<table>\n<thead>\n<tr>\n<th align=\"left\"><div style=\"width:225px\">Feature</div></th>\n<th align=\"center\">Personalize</th>\n<th align=\"center\">Preserve</th>\n<th align=\"center\">Connect</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td align=\"left\">Event data</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n</tr>\n<tr>\n<td align=\"left\">Profile enrichment</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n</tr>\n<tr>\n<td align=\"left\">Ingest</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n</tr>\n<tr>\n<td align=\"left\">Forward</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n</tr>\n<tr>\n<td align=\"left\">Store for data replays and backfills</td>\n<td align=\"center\">✓</td>\n<td align=\"center\">✓</td>\n<td align=\"center\"></td>\n</tr>\n<tr>\n<td align=\"left\">Evaluate for calculated attributes</td>\n<td align=\"center\">✓</td>\n<td align=\"center\"></td>\n<td align=\"center\"></td>\n</tr>\n<tr>\n<td align=\"left\">Evaluate for real-time audience</td>\n<td align=\"center\">✓</td>\n<td align=\"center\"></td>\n<td align=\"center\"></td>\n</tr>\n</tbody>\n</table>\n<p>If your account uses <a href=\"/guides/settings/usage/\">value-based pricing</a>, you can <a href=\"#change-the-default-event-tier\">change the default event tier for ingested events</a>.</p>\n<h2 id=\"manage-your-event-tiers\" style=\"position:relative;\"><a href=\"#manage-your-event-tiers\" aria-label=\"manage your event tiers permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Manage your event tiers</h2>\n<p>There are two ways to modify your event tiers:</p>\n<ul>\n<li>Individually through the mParticle UI</li>\n<li>In bulk by modifying a CSV formatted Event Volume Report</li>\n</ul>\n<aside>\nYou cannot change a Personalize event’s tier assignment if the event is currently used in the definition of a calculated attribute or an audience. When creating a calculated attribute or audience, it is possible to place multiple events in the Personalize event tier at once using the “All” selector.\n</aside>\n<h3 id=\"prerequisites\" style=\"position:relative;\"><a href=\"#prerequisites\" aria-label=\"prerequisites permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Prerequisites</h3>\n<p>Before you modify your event tiers using either method, ensure the following prerequisites are met:</p>\n<ul>\n<li>You must have the Admin and Compliance role to change event tiers for an event type. All other data will behave as if on the Personalize tier.</li>\n<li>\n<p>Verify that the consequences of changing tiers are acceptable in your environment:</p>\n<ul>\n<li>Event marked Preserve are never available for real-time evaluation, only for data replay or backfills.</li>\n<li>Events marked Connect are not available for data replays, backfills or real-time evaluation. These events are not visible in the User Activity View.</li>\n<li>Only events, including custom events, screen views, commerce events, and application lifecycle events, can be assigned an event tier. User information can’t be assigned a tier and so is only in the <strong>Personalize</strong> tier.</li>\n</ul>\n</li>\n</ul>\n<h3 id=\"modify-an-event-tier-in-the-ui\" style=\"position:relative;\"><a href=\"#modify-an-event-tier-in-the-ui\" aria-label=\"modify an event tier in the ui permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Modify an event tier in the UI</h3>\n<p>To change the event tier using the UI:</p>\n<ol>\n<li>Navigate to <strong>Data Platform > Data Catalog</strong> and select the event type such as <strong>Custom Events</strong> or <strong>Screen View</strong>.</li>\n<li>Next to the event, click the <strong>Event Tier</strong> drop-down and select a new tier.</li>\n<li>Click <strong>Apply</strong>.</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/tiered-events-detail.png\" alt=\"One event showing tiered events dialog\"></p>\n<aside>If the event is used in an audience or calculated attribute, you can't change it from <b>Personalize</b>, and you'll see the event grayed out in the Audience <b>Event Tier</b> drop-down.\n<p>To make a change:</p>\n<ul>\n    <li>Remove the event from the audience or calculated attribute definition.</li>\n    <li>Set the event to a different tier.</li>\n</ul>\n</aside>\n<h3 id=\"modify-event-tiers-in-bulk\" style=\"position:relative;\"><a href=\"#modify-event-tiers-in-bulk\" aria-label=\"modify event tiers in bulk permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Modify event tiers in bulk</h3>\n<p>You can make bulk modifications to your event tiers by downloading a copy of your Event Volume Report, entering your new tiers in the New Event Tier column in the downloaded file, and then re-uploading your new report to commit your changes in mParticle. </p>\n<p>To make bulk changes to your event tiers:</p>\n<ol>\n<li>Navigate to <strong>Data Platform > Data Catalog</strong> and hover your cursor over the <strong>Event Tier</strong> tooltip.</li>\n<li>Click <strong>Manage Event Tiers</strong>.</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/event-tier-tooltip.png\"></p>\n<ol start=\"3\">\n<li>Select <strong>Download Event Volume Report</strong> and click <strong>Next</strong>.</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/select-download-report.png\"></p>\n<ol start=\"4\">\n<li>\n<p>Under Select Event Volume Data Range, use the date picker to select one of the date range presets or enter a specific date range to include in your Event Volume Report.</p>\n<ul>\n<li>Regardless of the date range you select for your report, it will represent every event type that mParticle has ingested for your account. The date range selection simply allows you to view the relative volume of events ingested for each type within a specific timeframe.</li>\n</ul>\n</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/click-date-picker.png\"></p>\n<p><img src=\"/images/guides/platform-guide/tiered-events/select-date-range.png\"></p>\n<ol start=\"5\">\n<li>After entering the date range of the event data you want included in your report, click <strong>Download Report</strong>.</li>\n<li>\n<p>Open the Event Volume Report downloaded to your computer. Find the row for each event type you want to change the tier for, and enter the tier in the <strong>New Event Tier</strong> column. Make sure to save your changes.</p>\n<ul>\n<li>Remember, the three event tiers are <code class=\"language-text\">Connect</code>, <code class=\"language-text\">Preserve</code> and <code class=\"language-text\">Personalize</code>.</li>\n</ul>\n</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/modify-report.png\"></p>\n<ol start=\"7\">\n<li>To upload your modified report, repeat steps 1-2, select <strong>Bulk Update Event Tiers</strong>, and click <strong>Next</strong>.</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/select-upload-report.png\"></p>\n<ol start=\"8\">\n<li>In the Bulk Update Event Tiers modal, click <strong>Upload</strong> and select your modified Event Volume Report.</li>\n<li>Click <strong>Update Event Tiers</strong> to upload your modified Event Volume Report. When the upload is complete, a new Event Volume Report is automatically generated and downloaded to your computer so you can confirm that your changes were made correctly.</li>\n</ol>\n<h2 id=\"change-the-default-event-tier\" style=\"position:relative;\"><a href=\"#change-the-default-event-tier\" aria-label=\"change the default event tier permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Change the default event tier</h2>\n<p>By default, mParticle assigns all event types to the Personalize tier. However, you can change the default assignment to Preserve or Connect if your account uses <a href=\"/guides/settings/usage/\">value-based pricing</a>. </p>\n<p>Changing the default tier is helpful. For example, if you create a data plan with many new event types and most of them won’t be needed for real-time evaluations, you could assign them to the Preserve or Connect tier by default.</p>\n<p>To change the default event tier for a workspace:</p>\n<ol>\n<li>In the left-hand navigation, click the <strong>Settings</strong> gear cog to open the settings menu.</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/workspace-setting.png\"></p>\n<ol start=\"3\">\n<li>Click <strong>Workspaces</strong>.</li>\n<li>From the list of workspaces, click a workspace name to open the workspace settings dialog.\n<img src=\"/images/tiered-events/change-default-tier.png\" alt=\"UI for changing the default tier\" width=\"400\"></li>\n<li>Expand <strong>Defaults</strong> and use the drop-down in the Event Tiers section to choose a new default tier.</li>\n<li>Click <strong>Save</strong> to save your changes.</li>\n</ol>\n<aside>The default tier assignment is scoped to workspaces. Use this task in each workspace to change the default tier assignment.</aside>\n<p>After you set a default tier, all new events of all types seen in mParticle are assigned the new default tier. You can override the default tier assignment of an event type in <strong>Data Platform > Data Catalog</strong>.</p>\n<p>For example, you could change the default tier to Connect in the workspace setting and also set the tier for event type MyEvent to Personalize. Then, all new and existing events of type MyEvent are assigned the Personalize tier, while all other new events are given the new default, Connect.</p>\n<h2 id=\"event-volume-report\" style=\"position:relative;\"><a href=\"#event-volume-report\" aria-label=\"event volume report permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Event Volume Report</h2>\n<p>The event volume report is a CSV file that lists all the events used in calculated attributes and audiences. It also shows data volumes for the time range you specify.</p>\n<p>The event volume report is accessible from your workspace settings:</p>\n<ol>\n<li>Hover your cursor over the <strong>Settings</strong> gear icon in the left hand nav and click <strong>Workspaces</strong>.</li>\n<li>Click the <strong>Event Volume Report</strong> button in the upper right.</li>\n<li>Select the date range for the data you want covered in your report, then click <strong>Download Report</strong>.</li>\n</ol>\n<p><img src=\"/images/guides/platform-guide/tiered-events/report.png\" alt=\"Sample report\"></p>\n<aside class=\"warning\">\nThe Event Volume report is a technical report intended to help you understand how data is being ingested, how events are being used in real-time products, and to help support your utilization of event tiers. It provides an inventory of which event types are being ingested, excluding backdated events, back-filled events, and event types generated using Rules.  \n<br>\n<br>\nFor a report of which processed events you are billed for, please refer to the <a href=\"/guides/settings/billing/usage-and-billing-report/\">Usage & Billing Report</a>.\n</aside>\n<p>The Event Volume Report displays an approximate count of each event type ingested from your inputs within a certain date range. You can use these metrics to identify event types to change to a different event tier, or event types to exclude from calculated attributes and audience definitions.</p>\n<h2 id=\"event-volume-report-and-value-based-pricing\" style=\"position:relative;\"><a href=\"#event-volume-report-and-value-based-pricing\" aria-label=\"event volume report and value based pricing permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Event Volume Report and value-based pricing</h2>\n<p>There are differences between the Event Volume Report and your Monthly Credit Usage Report, which is a record of the <a href=\"/guides/settings/usage/#billable-items-quick-reference\">billable items</a> you are charged for. To learn how billable items are calculated, see <a href=\"/guides/settings/usage/\">Usage metering for value-based pricing (VBP)</a>.</p>\n<p>The two reports present different views of your data ingestion:</p>\n<ul>\n<li>The <strong>Monthly Credit Usage Report</strong> provides a retrospective view of the services your account is charged for according to the billing logic documented in <a href=\"/guides/settings/usage/\">Usage metering for value-based pricing</a>.</li>\n<li>The <strong>Event Volume Report</strong> provides a view of how data is being ingested at the time the report is generated, and should be used to help you select your event tier assignments.</li>\n</ul>\n<h3 id=\"differences-between-the-event-volume-report-and-monthly-credit-usage-report\" style=\"position:relative;\"><a href=\"#differences-between-the-event-volume-report-and-monthly-credit-usage-report\" aria-label=\"differences between the event volume report and monthly credit usage report permalink\" class=\"anchor before\"><svg width=\"16px\" height=\"17px\" viewBox=\"0 0 16 17\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n                <g id=\"Symbols\" stroke=\"none\" stroke-width=\"1\" fill=\"none\" fill-rule=\"evenodd\">\n                    <g id=\"Icon/Link\" fill=\"#98A0A3\" fill-rule=\"nonzero\">\n                        <g id=\"link\">\n                            <path d=\"M9.5,12.4 C9.6,12.4 9.7,12.4 9.9,12.4 C9.8,12.5 9.8,12.5 9.7,12.6 L7.5,14.8 C5.8,16.5 3,16.5 1.3,14.8 C-0.4,13.1 -0.4,10.3 1.3,8.6 L3.5,6.4 C3.6,6.3 3.6,6.3 3.7,6.2 C5,5 6.9,4.8 8.4,5.5 C8.8,5.7 9.3,6 9.6,6.4 C10,6.7 10.2,7.2 10.5,7.6 C10.2,7.9 9.9,8 9.5,8 C9.4,8 9.2,8 9.1,7.9 C8.9,7.5 8.5,7.2 8.1,6.9 C7,6.2 5.5,6.4 4.5,7.3 L3.8,8 L2.3,9.5 C1.2,10.6 1.2,12.5 2.3,13.6 C3.4,14.7 5.3,14.7 6.4,13.6 L7.9,12.1 C8.4,12.3 8.9,12.4 9.5,12.4 Z M14.7,1.3 C13,-0.4 10.2,-0.4 8.5,1.3 L6.3,3.5 C6.2,3.6 6.2,3.6 6.1,3.7 C6.7,3.7 7.4,3.7 8,3.9 L9.5,2.4 C10.6,1.3 12.5,1.3 13.6,2.4 C14.7,3.5 14.7,5.4 13.6,6.5 L12.1,8 L11.4,8.7 C10.4,9.7 8.9,9.8 7.8,9.1 C7.4,8.9 7.1,8.5 6.8,8.1 C6.7,8.1 6.5,8 6.4,8 C6,8 5.6,8.2 5.4,8.4 C5.6,8.8 5.9,9.3 6.3,9.6 C6.6,10 7.1,10.2 7.5,10.5 C9,11.2 10.9,11 12.3,9.8 C12.4,9.7 12.4,9.7 12.5,9.6 L14.7,7.4 C16.4,5.7 16.4,3 14.7,1.3 Z\" id=\"Shape\"></path>\n                        </g>\n                    </g>\n                </g>\n            </svg></a>Differences between the Event Volume Report and Monthly Credit Usage Report</h3>\n<p>Following is a list of differences between the Event Volume Report and Monthly Credit Usage Report:</p>\n<ul>\n<li>The Event Volume Report doesn’t include events added or dropped as a result of Rules, but those events are included in the Credit Usage Report. </li>\n<li>\n<p>The Event Volume Report displays event tier assignments at the time the report is generated, but the Credit Usage Report displays event tier assignments for events at the time they were ingested and processed. For example, imagine the following scenario:</p>\n<ul>\n<li>Day 1 of your billing period: you ingest one million events with the <code class=\"language-text\">Screen View</code> event type in the <code class=\"language-text\">Connect</code> event tier.</li>\n<li>Day 5 of your billing period: you change the event tier for <code class=\"language-text\">Screen View</code> from <code class=\"language-text\">Connect</code> to <code class=\"language-text\">Preserve</code> and you ingest another one million events.</li>\n<li>Day 6 of your billing period: you download your Event Volume Report and see two million <code class=\"language-text\">Screen View</code> events in the <code class=\"language-text\">Preserve</code> event tier. However, your Credit Usage Report will show one million events in the <code class=\"language-text\">Connect</code> tier and one million events in the <code class=\"language-text\">Preserve</code> tier.</li>\n</ul>\n</li>\n<li>The Event Volume Report includes automatically generated events like the <code class=\"language-text\">batch.SystemNotifications</code>, which could include events like <code class=\"language-text\">ConsentGranted</code> and <code class=\"language-text\">ConsentDenied</code>. However, automatically generated events are not included in the Monthly Credit Report, because they are not billable items.</li>\n<li>If you download an Event Volume Report before a batch of events is processed, they will not be reflected in the Event Volume Report, but they will be reflected in the Credit Usage Report.</li>\n<li>\n<p>Events timestamped 72 hours prior to when they are ingested are not be reflected in the Event Volume Report. </p>\n<ul>\n<li>For example: Imagine that on February 24, 2022 at 11:00 UTC, you ingest an event that is timestamped at <code class=\"language-text\">February 21, 2022 at 10:00 UTC</code>. An Event Volume Report report created on February 21st will not reflect that event. However, it will be reflected in your Monthly Credit Report.</li>\n</ul>\n</li>\n</ul>","frontmatter":{"title":"Tiered Events","order":11,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/data-platform/tiered-events/"}},"staticQueryHashes":["2950460867"]}