Mintlify commit backfills

docs.json

@@ -362,8 +362,7 @@
                   "docs/features/revenue-analytics",
                   "docs/features/saved-metrics-and-behaviors",
                   "docs/features/sessions",
-                  "docs/features/slack-integration",
-                  "docs/features/spark"
+                  "docs/features/slack-integration"
                 ]
               }
             ]
@@ -423,7 +422,13 @@
                       "docs/access-security/single-sign-on/google"
                     ]
                   },
-                  "docs/access-security/audit-log"
+                  {
+                    "group": "Audit Log",
+                    "root": "docs/access-security/audit-log",
+                    "pages": [
+                      "docs/access-security/audit-log-reference"
+                    ]
+                  }
                 ]
               },
               {
@@ -611,6 +616,7 @@
                           "guides/guides-by-use-case/empower-your-team/mcp/integrations"
                         ]
                       },
+                      "guides/guides-by-use-case/empower-your-team/headless",
                       "guides/guides-by-use-case/empower-your-team/close-strategy-execution-gap",
                       "guides/guides-by-use-case/empower-your-team/see-replays"
                     ]
@@ -649,6 +655,17 @@
               }
             ]
           },
+          {
+            "group": "MIXPANEL AI",
+            "icon": "/icons/flower.svg",
+            "pages": [
+              "guides/guides-by-use-case/empower-your-team/mixpanel-agent",
+              "guides/guides-by-use-case/empower-your-team/mcp",
+              "guides/guides-by-use-case/empower-your-team/mcp/mcp-by-industry",
+              "guides/guides-by-use-case/empower-your-team/mcp/integrations",
+              "guides/guides-by-use-case/empower-your-team/headless"
+            ]
+          },
           {
             "group": "PLAYBOOKS",
             "icon": "/icons/note.svg",
@@ -3918,6 +3935,10 @@
     {
       "source": "/troubleshooting/docs/tracking-best-practices/traffic-attribution",
       "destination": "/docs/tracking-best-practices/traffic-attribution"
+    },
+    {
+      "source": "/docs/features/spark",
+      "destination": "/docs/mixpanel-agent"
     }
   ]
 }

docs/agentic-automations.mdx

@@ -1,20 +1,20 @@
 ---
 title: "Agentic Automations"
 ---
 
 ## Overview
 
 Mixpanel Agentic Automations are sub-agents of Mixpanel Agent that you configure once to do recurring analysis work for you, and deliver the result where you already work.
 
 <Note>
     Agentic Automations are in beta. If you'd like access, please reach out to your Mixpanel account team to join the waitlist.
 </Note>
 
 ## Types of Agentic Automations
 
 - **KPI Monitoring** *(available now)* — Watches a metric you own and ships a personalized digest on the cadence you choose. See [below](#kpi-monitoring) for details.
 
 In the future, we're also exploring Research, Event-Triggered, and Data Governance automations. For early access, please reach out to your Mixpanel account team to join the waitlist.
 
 ## KPI Monitoring
 
@@ -29,18 +29,25 @@
 Click '+ Create New' button in your side navigation bar. At the bottom of the 'Analysis' section, click the Automation button.
 
 <Note>
     Don't see this button? Agentic Automations are in beta. If you'd like access, please reach out to your Mixpanel account team to join the waitlist.
 </Note>
 </Step>
 
+<Step title="Pick a cadence">
+
+Digests can be delivered daily, weekly, or monthly. Pick the rhythm that matches how your team operates. Weekly is a balanced default cadence for most teams.
+</Step>
+
 <Step title="Pick the metric to monitor">
 
 Choose any Insights-style event metric — sums, counts, or unique counts over an event you've already instrumented. The agent will use the metric's existing definition as the source of truth for what it watches.
 </Step>
 
-<Step title="Pick a cadence">
+<Step title="Add instructions">
+
+Use the **Instructions** field to tell the agent how to interpret results and what to call out. For example: "Flag anything that deviates more than 2 standard deviations from the 30-day average" or "Focus on week-over-week change, not absolute values."
 
-Digests can be delivered daily, weekly, or monthly. Pick the rhythm that matches how your team operates — daily is a good default for most active KPIs.
+Instructions shape the digest's commentary, not the underlying query. The agent runs a single, fixed query based on the metric you selected. It cannot run additional queries, pull in other metrics, or take actions. Instructions guide how the agent frames its summary: which comparisons to emphasize, what thresholds matter to you, and what language to use when describing shifts.
 </Step>
 
 <Step title="Pick a delivery channel">
@@ -61,7 +68,7 @@
 
 ## Limits
 
 - **Automations per user per project.** Free: 5, Growth: 10, Enterprise: 20.
 - **Metric types.** KPI Monitors today support Insights-style event metrics only. Funnel and retention metrics aren't yet supported.
 - **Delivery channels.** Slack and email are available today
 - **Cadence.** Daily, weekly, or monthly. There's no per-user delivery window control yet (e.g., "weekdays 8–10am local").

docs/data-governance/lexicon.mdx

@@ -17,7 +17,7 @@
 
 </Frame>
 
 Lexicon is a data dictionary that stores descriptions of events and their properties. Project owners and admins can add/manage descriptions for all events and properties and organize data for clarity and discoverability. Event and property definitions help your entire team understand what your data means, so everyone stays on the same page.
 
 To open Lexicon, select the **Data** tab on the left-hand navigation menu, and then select **Lexicon**.
 
@@ -47,32 +47,32 @@
 
 | Field | Description |
 | --- | --- |
 | Event Name | The database name of the event. Status Icons indicate whether the event is hidden or visible in the Mixpanel project |
 | Display Name | The event name that displays in the Mixpanel interface. |
 | Description | The information that describes the event, such as what triggers it or what properties are sent with it. |
 | 30-Day Volume | The total number of events that users fired in the last 30 days. |
 | 30-Day Queries | The total number of UI queries that project members executed in the last 30 days. Includes queries from selecting events in reports, viewing reports, and queries in "Users" and "Events" tabs. Excludes dashboard views.|
 | Last Queried | The user that last used this event in the Mixpanel UI. |
 | First Queried | The user that first used this event in the Mixpanel UI. |
 | Owners | The user(s) that are points-of-contact for this event. |
 | Status | Whether this event is Pending, Visible, Hidden, Blocked, or Merged. |
 
 
 ### Event Properties
 
 Event properties describe details about events, such as distinct_id or browser.
 
 This table contains descriptions for each field in the “Event Properties” view.
 
 | Field | Description |
 | --- | --- |
 | Name | The database name of the property. |
 | Display Name | The property name that displays in the Mixpanel interface. |
 | Description | The information that describes the property, such as what events it is sent with. |
 | Example Value | What is an example value of this property. |
 | Events With Property | The total number of events that contain this property in the last 30 days. |
 | Queries | The total number of UI queries that project members executed in the last 30 days. Includes queries from selecting events in reports, viewing reports, and queries in "Users" and "Events" tabs. Excludes dashboard views.|
 | Status | Indicates whether the property is visible or hidden from the Mixpanel interface. Also indicates if the property is blocked, merged, or marked as sensitive. |
 
 Lexicon contains property definitions for the default properties that Mixpanel’s client-side libraries automatically send with each event across web and mobile platforms.
 
@@ -89,10 +89,10 @@
 | Field | Description |
 | --- | --- |
 | Name | The database name of the property. |
 | Display Name | The property name that displays in the Mixpanel interface. |
 | Description | The information that describes the property, such as what events it is sent with. |
 | Example Value | What is an example value of this property. |
 | Status | Indicates whether the property is visible or hidden from the Mixpanel interface. Also indicates if the property is blocked, merged, or marked as sensitive. |
 | Users With Property | The total number of profiles that contain this property. |
 | Queries | The total number of UI queries that project members executed in the last 30 days. Includes queries from selecting events in reports, viewing reports, and queries in "Users" and "Events" tabs. Excludes dashboard views.|
 
@@ -108,7 +108,7 @@
 
 ### Custom Events
 
 [Custom Events](/docs/features/custom-events) are events and properties you combine into one event to use in Mixpanel reports. The fields for custom events are “Name”, “Description”, "Definition", "30 Day Queries", "Last Queried" and “Created” (defined above).
 
 ### Lookup Tables
 
@@ -124,7 +124,7 @@
 
 Lexicon provides several options for you to filter your events, custom events, event properties, and profile properties.
 
 You can filter by visible or hidden events, blocked events, merged events, tags, your defined events, autotracked events, and default Mixpanel events. These filtering options help you arrive at the most useful data to analyze your performance.
 
 <Frame>
 ![Lexicon Filtering](/images/lexiconFiltering.png)
@@ -146,21 +146,25 @@
 Only project owners may block and unblock data from the Lexicon. Learn more about [Roles and Permissions](/docs/orgs-and-projects/roles-and-permissions).
 </Note>
 
-In Lexicon, you can intercept and block incoming events or properties. Mixpanel won’t store any **new data** for the event or property you select to block. **Warning: You cannot recover event data after you block it.**
+In Lexicon, you can intercept and block incoming events or properties. Mixpanel won't store any **new data** for the event or property you select to block. **Warning: You cannot recover event data after you block it.**
 
 When an event is blocked, all events of that type that have previously been ingested (before blocking it) will still show in the interface. Only project owners can block events and properties. **Note: It takes a few hours for Mixpanel to process the blocked event.**
 
 Sample use cases for blocking events and properties are:
 
 **Sensitive data:** If you accidentally send sensitive data, such as passwords or credit card information, you can block the event or property with that data and prevent it from being stored in Mixpanel servers.
 
 **Cost and Time Efficiency:** Being able to block events and properties that are no longer useful directly from Lexicon is easier and more efficient than having to implement changes to your code base.
 
 **Better Organization:** Events and properties that are no longer useful can cause a cluttered Mixpanel project. Blocking unnecessary events and properties optimizes your code for a clean and streamlined project implementation.
 
 **Blocking Events**
 
+<Info>
+Previously, Block was called "Drop" in Lexicon. Events that formerly showed a "Dropped" status now show a "Blocked" status.
+</Info>
+
 By blocking an event, you can intercept and block incoming events. Mixpanel will not store any new data for the event you select to block.
 
 To block an event in Lexicon:
 
@@ -188,7 +192,7 @@
 
 **Blocking Properties**
 
 By blocking a property, you can intercept and block an incoming property. Mixpanel won’t store any new data for the property you select to block.
 
 To block a property in Lexicon:
 
@@ -209,7 +213,7 @@
 ## Hiding Data
 
 <Note>
 You must have an admin or owner project role to hide and unhide data from the Lexicon. Learn more about [Roles and Permissions](/docs/orgs-and-projects/roles-and-permissions).
 </Note>
 
 In Lexicon, you can hide any events or properties. Unlike [blocking data](/docs/data-governance/lexicon#blocking-data), hiding data does not affect data ingestion; any events/properties that are hidden will continue to be ingested in your project and count toward your data allowance.
@@ -241,8 +245,8 @@
 
 To show an event or property:
 
 1. Select one or more hidden events, event properties, or profile properties. The “Unhide” icon appears. You can check the “Status” field to determine whether an event or property is visible or hidden.
 2. Select **Unhide**. After you select **Unhide**, the event or property status changes to “Visible”.
 <Frame>
 ![Lexicon Show Events and Properties](/images/show-events-and-properties.png)
 </Frame>
@@ -255,9 +259,9 @@
 
 Let's suppose your iOS app sends an event named “Purchase”, and your Android app sends an event named “purchase item”. Even though both events have the same function, you have to individually select them every time you build a report.
 
 By merging “Purchase” and “purchase item” into a single event named “Purchase”, you would no longer need to query each event separately since Mixpanel would recognize both “Purchase” and “purchase item” as a unique event.
 
 Being able to merge events can help streamline your implementation, reduce your costs by eliminating redundant events being sent to Mixpanel, and simplify report analysis because you’re only using optimal events and properties.
 Do note however that user profile properties cannot be merged at this time.
 
 <Note>
@@ -277,18 +281,18 @@
 <Frame>
 ![Lexicon Merge Events](/images/lexicon-merge-events.png)
 </Frame>
 3. In the “MERGE SELECTED EVENTS INTO…” section, specify which event Mixpanel should consider as the new unique event.
 4. Click **Merge**. The merged event appears and the “Status” column indicates “Merged”.
 
 **Unmerge Events**
 
 To unmerge events:
 
 1. Select the merged event to unmerge. The “Unmerge” icon appears.
 <Frame>
 ![Lexicon Unmerge Events](/images/unmerge-events.png)
 </Frame>
 2. Click Unmerge. The merged event appears as the original two distinct events.
 
 **Merging Properties**
 
@@ -299,20 +303,20 @@
 <Frame>
 ![Lexicon Merge Events](/images/merge-properties.png)
 </Frame>
 3. In the “MERGE SELECTED PROPERTIES INTO…” section, specify which property Mixpanel should recognize as the newly merged property name.
 4. Click **Merge**. The merged property appears and the “Status” column indicates “Merged”.
 
 **Unmerge Properties**
 
 To unmerge properties:
 
 1. Select the merged property to unmerge. The “Unmerge” icon appears.
 
 <Frame>
 ![Lexicon Unmerge Events](/images/unmerge-properties.png)
 </Frame>
 
 2. Click Unmerge. The merged property appears as the original two distinct properties.
 
 ## Verify Data
 
@@ -320,9 +324,9 @@
   Customers on an Enterprise can access the Verified Data feature. See our [pricing page](https://mixpanel.com/pricing/) for more details.
 </Note>
 
 Verified Data in Mixpanel allows designated project owners and admins to add Verified badges to certain Events, Behaviors, Formulas, Custom Events, and Cohorts. This signals to other users within your project that this data has been vetted and can be confidently used for analysis and reporting.
 
 By providing a clear distinction between vetted and non-vetted data, it becomes easier for teams to adopt Mixpanel, knowing they are using the right events.
 
 **How it Works**
 
@@ -355,7 +359,7 @@
 
 ## Export and Import Lexicon Data
 
-Mixpanel supports exporting and importing Lexicon data dictionaries. Project owners, admins, analysts, and consumers can click **Export** in Lexicon to receive a CSV file via email that contains the events and properties, and/or user profile properties data from a project.
+Mixpanel supports exporting and importing Lexicon data dictionaries. Project owners, admins, and analysts can click **Export** in Lexicon to receive a CSV file via email that contains the events and properties, and/or user profile properties data from a project.
 
 <Frame>
 ![Lexicon Export](/images/lexiconExport.png)
@@ -405,24 +409,24 @@
 
 ### Avo.app Import
 To import your data dictionary from Avo.app, you will need to enable an integration with Mixpanel. The following information would be necessary to complete this integration from Avo.app:
 - Mixpanel Project ID (`https://mixpanel.com/project/[Mixpanel Project ID]/...`)
 - Mixpanel Service Account Username & Secret (Owner or Admin role required)
 To publish your Avo data dictionary to Lexicon, click the "Publish to Lexicon" button in the integration interface.
 
 Click [here](https://www.avo.app/docs/publishing/integrations) for more information on integrating Avo.app with Lexicon.
 
 ### mParticle Import
 When importing a data dictionary from mParticle, navigate to your Data Plan and select Download Plan Version from the upper right menu.
 
 - Click Import on the top right-hand side of Lexicon
 - Select mParticle
 - Select the downloaded JSON file from mParticle Data Plans
 - Review Events, Event Properties, and User Profile Properties to be imported.
 - Import data into Lexicon
 
 ## Lexicon Schemas API
 
 Mixpanel provides a suite of API endpoints for you to Retrieve, Create, and Delete your data dictionary in Lexicon. To use these APIs, check out our [API reference docs](/reference/lexicon-schemas-api).
 
 ### Lexicon UI vs Lexicon Schemas API
 
@@ -441,14 +445,14 @@
 
 ## Lexicon Event Details
 
 Mixpanel provides a variety of tools to make it easier for teams to better understand what specific events mean.
 
 | Field | Description |
 | --- | --- |
 | Name | The database name of the event. |
 | Display Name | The event name that displays in the Mixpanel interface. |
 | Description | The information that describes the event, such as what triggers it or what properties are sent with it. |
 | Status | The event is either hidden or visible in the Mixpanel project. |
 | Tags | Allows your team to categorize events by different themes. |
 | Platforms | Allows your team to categorize which platforms this event is fired in. |
 | Owners | Allows your team to assign a point-of-contact to events in case team members have follow-up questions about an event. (Only available on the Enterprise Plan) |

docs/data-pipelines.mdx

@@ -12,12 +12,12 @@
   Customers on an Enterprise or Growth plan can access Data Pipeline as an add-on package. See our [pricing page](https://mixpanel.com/pricing/) for more details.
 </Note>
 
 Data Pipelines is a feature that continuously exports data from your Mixpanel project to a Cloud Storage bucket or Data Warehouse of your choice. This feature is ideal for those who wish to perform SQL analysis on Mixpanel data within their own environment.
 
 Setting up Data Pipelines involves two main steps:
 
 1. Configuring your destination to accept data writes from Mixpanel.
-2. Creating data pipelines through the **Integrations** page in the UI.
+2. Creating data pipelines through the **Destinations** page in the UI.
 
 We offer a 30-day free trial of the Data Pipelines add-on. For details on activation, refer to the [FAQ](#how-does-the-free-trial-work).
 
@@ -58,14 +58,13 @@
  To create and manage a Data Pipeline, you must have an admin or owner project role. Learn more about [Roles and Permissions](/docs/orgs-and-projects/roles-and-permissions).
 </Note>
 
 After configuring your destination to accept data exported from Mixpanel, we must initiate the pipeline from the Mixpanel UI.
 
-After configuring your destination, initiate data export in **Integrations** page on your Mixpanel project > **Create Pipeline** > fill in necessary configurations. You can choose different data sources including events, people and identity and other advanced options. See [Data Pipelines](/docs/data-pipelines/json-pipelines) for more details.
+After configuring your destination, initiate the data export in the **Destinations** page on your Mixpanel project -> **Create Pipeline** -> fill in the necessary configurations. You can choose different data sources, including events, people and identity, and other advanced options. See [Data Pipelines](/docs/data-pipelines/json-pipelines) for more details.
 
 <Steps>
 
-
-<Step title="Click the settings button and select Integrations">
+<Step title="Click the settings button and select Destinations">
 
 <Frame>
 ![create_pipeline1](/images/create_pipeline1.png)
@@ -91,91 +90,91 @@
 
 ### Managing Existing Pipelines
 
 To delete, pause, or unpause a JSON pipeline:
 
-1. Go to the **Integrations** page
+1. Go to the **Destinations** page
 2. Find the pipeline you want to manage
 3. Click the **3-dot** menu on the right side of the pipeline
 4. Select **Delete Pipeline**, **Pause Pipeline**, or **Unpause Pipeline** as needed
 
 Note: JSON pipelines can only be managed through the UI, not via the data pipelines API.
 
 ### Backfilling Historical Data
 
-You can schedule an initial backfill when creating a pipeline. This ensures that historical data is also exported to the data warehouse. Note that the `from_date` must be within 6 months in the past.
+You can schedule an initial backfill when creating a pipeline. This ensures that historical data is also exported to the data warehouse. Note that the `from_date` value must be within 6 months in the past.
 
 The completion time for a backfill depends on the number of days and the amount of data in the project. Larger backfills can take up to multiple weeks.
 
 ### Viewing Pipeline Configuration
 
 To check a pipeline's configuration:
 
-1. Go to the **Integrations** page
+1. Go to the **Destinations** page
 2. Either:
-   - Click on the pipeline name to view configuration at the top of the page, or
+   - Click on the pipeline name to view the configuration at the top of the page, or
    - Click the **3-dot** menu and select **View Configuration**
 
 ### Why does the number of events in Mixpanel not match the number of exported events to my destination?
 
 Discrepancies between the event counts in Mixpanel and those exported to your destination can occur for several reasons:
 
 - **Data Sync**: If [Events Data Sync](/docs/data-pipelines/json-pipelines#events-data-sync) is not enabled or is unsupported for your pipeline, this could prevent some data from being exported.
 - **Data Delay**: Late-arriving data may take up to one day to sync from Mixpanel to your destination, leading to temporary discrepancies.
 - **Hidden Events**: Mixpanel exports all events, including those hidden in the Mixpanel UI via Lexicon. To reconcile differences in counts, check if the events in your destination include those hidden in the Mixpanel UI.
-- **Timezone Differences**: Data is exported to your warehouse in UTC, whereas data displayed in Mixpanel is in your project timezone. 
+- **Timezone Differences**: Data is exported to your warehouse in UTC, whereas data displayed in Mixpanel is in your project's timezone. 
 
 ### What timezone is the data exported in?
 
 The data is exported in UTC timezone. You’ll need to convert it to your project’s timezone when running queries in your warehouse. Please refer to [this page](/docs/data-pipelines/common-sql-queries) for some common SQL queries.
 
 ### How can I count events exported by Mixpanel in the warehouse?
 
 Counting events can be slightly different for each warehouse, since we use different partitioning methods. Here are examples for [BigQuery](/docs/data-pipelines/integrations/bigquery#get-the-number-of-events-each-day) and [Snowflake](/docs/data-pipelines/integrations/snowflake#get-the-number-of-events-each-day).
 
 ### How does the free trial work?
 
 Mixpanel offers a 30-day free trial of the Data Pipelines, allowing you to create one pipeline per data source for each project.
 
 **Trial limitations**:
 
-- Exports are scheduled on a daily basis only.
+- Exports are scheduled daily only.
 - Data synchronization feature is not available.
 - Only one pipeline can be created per data source per project.
-- Backfilled data is limited to one day prior to the creation date of the pipeline.
+- Backfilled data is limited to one day before the creation date of the pipeline.
 
 ### Why can’t I delete my trial pipeline?
 
 You can’t delete a trial pipeline in Mixpanel — this is intentional. Each project is limited to one trial pipeline per data source, and keeping it prevents deleting/recreating trials to bypass limits. It also serves as a record that the trial has been used. Even after you upgrade to a paid Data Pipelines package, the trial pipeline remains visible and cannot be removed. This is a policy decision to preserve the integrity of the trial program, not a technical constraint.
 
 ### What is Active Pipeline Limit
 
-Each project can have 2 recurring pipelines and 1 date ranged backfill pipeline active. Multiple pipelines cannot write to the same destination or for the same date range in a destination. Recurring pipelines must have different frequencies.
+Each project can have two recurring pipelines and one date-ranged backfill pipeline active. Multiple pipelines cannot write to the same destination or for the same date range in a destination. Recurring pipelines must have different frequencies.
 
 To maintain optimal performance across our services, we limit the number of concurrently running pipeline steps to one per project. This approach ensures that each job, including those involving substantial backfills, waits its turn, preventing any single project from monopolizing resources and thus promoting fair scheduling among all customers.
 
 ### Is it possible to specify when pipeline exports run?
 
-No. Hourly pipelines are targeted to run 30 minutes past the hour to be exported, and daily pipelines are targeted to run 30 minutes past the day to be exported (e.g. 00:30 AM) in the project’s timezone. For example, a project in the Pacific timezone with a daily events pipeline will start the export for data from 5/22 on 5/23 00:30 AM PT.
+No. Hourly pipelines are targeted to run 30 minutes past the hour to be exported, and daily pipelines are targeted to run 30 minutes past the day to be exported (e.g., 00:30 AM) in the project’s timezone. For example, a project in the Pacific timezone with a daily events pipeline will start the export for data from 5/22 on 5/23 00:30 AM PT.
 
 Please note that the [24-hour SLA](/docs/data-pipelines#what-is-the-service-level-agreement) applies.
 
 ### What is the Service Level Agreement?
 
 Our Service Level Agreement (SLA) stipulates a latency policy for exported events of up to 24 hours end-to-end, with an additional 24-hour allowance for late-arriving data.
 
-**Note**: Mixpanel classifies late data as any data point or user profile update that reaches Mixpanel servers more than two hours after the end of the export window. Late-arriving event data is exported only for pipelines that with **sync** enabled.
+**Note**: Mixpanel classifies late data as any data point or user profile update that reaches Mixpanel servers more than two hours after the end of the export window. Late-arriving event data is exported only for pipelines that have **sync** enabled.
 
 For hourly pipelines, data that arrives on time is expected to be exported within 24 hours from the moment it is ingested by Mixpanel. For daily pipelines, this 24-hour period begins at the start of the next calendar day based on project time (e.g., data ingested on January 1st is scheduled to be exported from the start of January 2nd midnight to the end of the day on January 3rd).
 
 Data arriving late is handled during a daily sync process the following day after ingestion, provided sync is enabled. For instance, if data for January 1st arrives on January 3rd, it would be exported in the sync run on January 4th.
 
 ### What should I set for the Account Name and Storage Integration when creating a Snowflake pipeline?
 
-The Account Name should be set to your unique account identifier Eg. "blah2321.us-west-2" while the Storage Integration should be set to the name of the storage integration you created in Snowflake Eg. "MIXPANEL_EXPORT_STORAGE_INTEGRATION".
+The Account Name should be set to your unique account identifier, e.g., "example1234.us-west-2", while the Storage Integration should be set to the name of the storage integration you created in Snowflake Eg. "MIXPANEL_EXPORT_STORAGE_INTEGRATION".
 
 ### What happens to late-arriving data?
 
 For [incremental JSON pipelines](/docs/data-pipelines/json-pipelines#incremental-pipelines), late-arriving data will be exported as it's ingested. However, that is not the case for Raw and Schematized pipelines without [sync](/docs/data-pipelines/json-pipelines#events-data-sync) enabled — manual intervention will be needed to export late-arriving data into your data warehouse.
 ### Can I change the destination of an existing pipeline?
 
-No, you cannot. If you need to change the destination, you would need to create a new pipeline.
+No, you cannot. If you need to change the destination, you would need to create a new pipeline.