diff --git a/pages/docs/data-pipelines.mdx b/pages/docs/data-pipelines.mdx index 4d836ee1c2..1b226df1db 100644 --- a/pages/docs/data-pipelines.mdx +++ b/pages/docs/data-pipelines.mdx @@ -1,4 +1,4 @@ -import { Callout } from 'nextra/components' +import { Callout, Steps } from 'nextra/components' # Data Pipelines Overview @@ -52,8 +52,26 @@ For detailed setup guides per destination, see: ## Step 2: Creating the Pipeline +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. + + +{

Click the settings button and select Integrations.

} + +![create_pipeline1](/create_pipeline1.png) + +{

Select the provider of your warehouse destination, and click "+ Create Pipeline".

} + +![create_pipeline2](/create_pipeline2.png) + +{

Provide the details of your destination to create the pipeline.

} + +![create_pipeline3](/create_pipeline3.png) + + + ## FAQ ### Managing Existing Pipelines diff --git a/pages/docs/tracking-methods/integrations/google-sheets.mdx b/pages/docs/tracking-methods/integrations/google-sheets.mdx index 3e3b1f6e96..c172d0d80f 100644 --- a/pages/docs/tracking-methods/integrations/google-sheets.mdx +++ b/pages/docs/tracking-methods/integrations/google-sheets.mdx @@ -136,3 +136,18 @@ Using the principle of least-privilege, Sheets™ ⇔ Mixpanel requests access t - `https://www.googleapis.com/auth/script.external_request` is used to send your mapped data to mixpanel and to request your report/cohort data from mixpanel. No other sensitive scopes are requested by the application. + +## FAQ + +**1. Why isn't my recurring sync exporting data, even though a manual run works?** + +A recurring sync that is not exporting data despite a functional manual sync may be indicative of a stale trigger caused by the extension entering a bad state (could be caused by a number of reason originating in your local Google Workspace instance). + +As a troubleshooting step please navigate to [Apps Script > My Triggers from your Google Workspace]( https://script.google.com/home/triggers), delete the existing Mixpanel Sheets extension trigger, then try creating a new recurring sync to generate a new trigger. + +**2. Why is my sync failing to authenticate even though I entered the correct Mixpanel credentials?** + +Some users report seeing the error `Authorization is required to perform that action.` when setting up a sync, despite providing the correct Mixpanel authentication. This issue occurs when you are logged into multiple Google accounts simultaneously, where the sheet is owned by one account (e.g., personal) but the extension is installed on another account (e.g., business). + +To resolve the issue, log out and reinstall the extension on the same account you use to access the sheet. + diff --git a/pages/docs/tracking-methods/sdks/javascript/javascript-replay.mdx b/pages/docs/tracking-methods/sdks/javascript/javascript-replay.mdx index d2c3d4f21b..289efee5d6 100644 --- a/pages/docs/tracking-methods/sdks/javascript/javascript-replay.mdx +++ b/pages/docs/tracking-methods/sdks/javascript/javascript-replay.mdx @@ -24,10 +24,13 @@ You can capturing replay data using a sampling method (recommended), or customiz We recommend using the sampling method unless you need to customize when you capture replay data. +When the SDK initializes, it makes a sampling decision based on your configured sampling rate. A percentage of initializations will trigger session recording accordingly. + To enable Session Replay and set your sampling rate, set the `recording_sessions_percent` when initializing the SDK. This is the only change needed in your existing JavaScript SDK implementation to enable Session Replay. + Start with a low sampling rate, then adjust according to your specific analytics needs. - + **Example Usage** ```javascript Javascript @@ -404,3 +407,7 @@ Below is a high-level overview of how the SDK will work on your website: - Optimized Compression: Before sending, Mixpanel will compress the payload using the asynchronous CompressionStream API. This will optimize bandwidth while not blocking the UI thread. We have tested the SDK extensively and it generally has minimal impact on how your website performs. The initial snapshot takes a bit of work, and naturally, more complex and interactive pages generate more data for rrweb and Mixpanel to handle. So, it is always a good practice to do some performance testing after you have implemented Session Replay, just to be sure everything is running smoothly. + +#### Does session recording persist across page loads? + +Session recording does persist across page load for SDK v2.61.0+. See [the release note](https://github.com/mixpanel/mixpanel-js/releases/tag/v2.61.0). \ No newline at end of file diff --git a/pages/docs/tracking-methods/warehouse-connectors.mdx b/pages/docs/tracking-methods/warehouse-connectors.mdx index 26553781dc..9ee60b7148 100644 --- a/pages/docs/tracking-methods/warehouse-connectors.mdx +++ b/pages/docs/tracking-methods/warehouse-connectors.mdx @@ -149,6 +149,13 @@ JSON columns mapped in BigQuery containing multiple properties are subject to a 35.204.177.251 ``` + - Some users report seeing the following error `ErrorMessage=SQL compilation error: Cannot unload to an inlined external location. Please create a stage first and unload to the stage instead.`. To resolve this error, you may set the following account security setting: + + ```jsx + ALTER ACCOUNT SET PREVENT_UNLOAD_TO_INLINE_URL = FALSE; + ``` + + See the [Snowflake documentation on this setting](https://docs.snowflake.com/en/sql-reference/parameters#prevent-unload-to-inline-url) before making the change.
diff --git a/public/create_pipeline1.png b/public/create_pipeline1.png new file mode 100644 index 0000000000..abbfe1985a Binary files /dev/null and b/public/create_pipeline1.png differ diff --git a/public/create_pipeline2.png b/public/create_pipeline2.png new file mode 100644 index 0000000000..0387842084 Binary files /dev/null and b/public/create_pipeline2.png differ diff --git a/public/create_pipeline3.png b/public/create_pipeline3.png new file mode 100644 index 0000000000..ee075ee774 Binary files /dev/null and b/public/create_pipeline3.png differ