Skip to content

Commit e7ce1e2

Browse files
authored
Fix a variety of 404s (#1948)
* fix 404s * fixes
1 parent c0686c0 commit e7ce1e2

File tree

8 files changed

+23
-21
lines changed

8 files changed

+23
-21
lines changed

pages/docs/data-governance/lexicon.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -308,7 +308,7 @@ Once you have your Segment Token & Workspace, head over to Lexicon and Select Im
308308

309309
### Avo.app Import
310310
In order to import your data dictionary from Avo.app, you will need to enable an integration with Mixpanel. The following information would be necessary in order to complete this integration from Avo.app:
311-
- Mixpanel Project ID (https://mixpanel.com/project/[Mixpanel Project ID]/...)
311+
- Mixpanel Project ID (`https://mixpanel.com/project/[Mixpanel Project ID]/...`)
312312
- Mixpanel Service Account Username & Secret (Owner or Admin role required)
313313
To publish your Avo data dictionary to Lexicon, click the "Publish to Lexicon" button in the integration interface.
314314

pages/docs/data-structure/user-profiles.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ You can get an overview of how Group Profiles relate to Mixpanel's Data Model un
212212
The end time will be inferred from the next event sent with a higher `Start Timestamp`. If you do not have an updated value for a property and simply want it to become inactive at a certain timestamp, please set up your DWH table to set undefined for the property at the time that it becomes inactive/expires.
213213

214214
### How do I set the initial set of profile properties for the user?
215-
Historical profile properties can only be imported through a Warehouse Connector sync. For more information about the connectors and which are supported, see our [docs](https://docs.mixpanel.com/docs/tracking/warehouse-connectors). There is currently no other method to import historical profile properties or set defaults. To set initial values, please ensure that your warehouse table has the rows covering the historical period you want to analyze.
215+
Historical profile properties can only be imported through a Warehouse Connector sync. For more information about the connectors and which are supported, see our [docs](https://docs.mixpanel.com/docs/tracking-methods/warehouse-connectors). There is currently no other method to import historical profile properties or set defaults. To set initial values, please ensure that your warehouse table has the rows covering the historical period you want to analyze.
216216

217217
### What if I have the same property name sent as a regular profile property as well as a historic property?
218218
If a regular profile property shares a name with an historic property, the two properties will be treated as distinct and separate entities (they will not be de-dupped).

pages/docs/reports/apps/jql.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
# JQL: Create custom queries using Javascript code
22

3-
> ❗️JQL is currently in maintenance mode and will be completely deprecated December 31, 2025. We recommend discontinuing use of JQL and using an [alternate method](https://docs.mixpanel.com/docs/export-methods) to get the data you need. Below are alternatives for common use cases and you need help deciding the best method for you, reach out to [support](mixpanel.com/get-support).
4-
> - Raw Event export: [Export API](https://developer.mixpanel.com/reference/raw-data-export-api) or [Data Pipelines](https://docs.mixpanel.com/docs/data-pipelines)
5-
> - User Profile export: [Engage Query API](https://developer.mixpanel.com/reference/engage-query) or [Data Pipelines](https://docs.mixpanel.com/docs/data-pipelines)
6-
> - Other reporting: [Query API](https://developer.mixpanel.com/reference/query-api) or in-app [Core Reports](https://docs.mixpanel.com/docs/reports)
3+
> ❗️JQL is currently in maintenance mode and will be completely deprecated December 31, 2025. We recommend discontinuing use of JQL and using an [alternate method](/docs/export-methods) to get the data you need. Below are alternatives for common use cases and you need help deciding the best method for you, reach out to [support](https://mixpanel.com/contact-us/support).
4+
> - Raw Event export: [Export API](https://developer.mixpanel.com/reference/raw-data-export-api) or [Data Pipelines](/docs/data-pipelines)
5+
> - User Profile export: [Engage Query API](https://developer.mixpanel.com/reference/engage-query) or [Data Pipelines](/docs/data-pipelines)
6+
> - Other reporting: [Query API](https://developer.mixpanel.com/reference/query-api) or in-app [Core Reports](/docs/reports)
77
88
The JQL JavaScript code must define a `main()` function. This JavaScript will be compiled, and the `main()` function will be executed by the query engine. The return value of `main()` must be a sequence of zero or more transformations applied to a collection of events, user records or joined records.
99
Events are retrieved by calling the `Events()` function.

pages/docs/tracking-methods/integrations/cms-ecommerce.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ However, to really exercise the power of Mixpanel, you can do a custom implement
1515

1616
## Shopify
1717
<Cards>
18-
<Cards.Card icon title="Integration Guide" href="/docs/quickstart/install-mixpanel/shopify" />
18+
<Cards.Card icon title="Integration Guide" href="/docs/tracking-methods/integrations/shopify" />
1919
</Cards>
2020

2121
Even though the integration process is largely the same as the regular [JavaScript API Integration](/docs/tracking-methods/sdks/javascript), there are a few things specific to Shopify that you’ll want to account for.
@@ -26,7 +26,7 @@ Mixpanel users who have successfully implemented on a Shopify site [have some gr
2626

2727
While Shopify is strict about preventing arbitrary scripts from running in the checkout flow, you can easily capture customer events and conversions by integrating the Mixpanel Javascript SDK with the Shopify Web Pixel API.
2828

29-
Reference our [Guide to Integrating Mixpanel Javascript SDK with Shopify](/docs/quickstart/install-mixpanel/shopify) for a detailed walkthrough.
29+
Reference our [Guide to Integrating Mixpanel Javascript SDK with Shopify](/docs/tracking-methods/integrations/shopify) for a detailed walkthrough.
3030

3131
If you are looking for a no-code solution, check out the [Vendo app by Growth Analytics Marketing](https://mixpanel.com/partners/integrations/vendo) (a Mixpanel solution and technology partner), available in the Shopify app store. Vendo automatically sends data from your Shopify store front-end and back-end to your Mixpanel project. Vendo offers a 30-day free trial and a free plan.
3232

pages/docs/tracking-methods/sdks/react-native.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,7 @@ You can handle the identity of a user using the [`.identify()`](https://mixpanel
229229
We recommend against calling `.identify()` for anonymous visitors to your site.
230230
</Callout>
231231

232-
Call [`.identify()`]((https://mixpanel.github.io/mixpanel-react-native/Mixpanel.html#identify)) when you know the identity of the current user, passing in their user ID as an argument. This is typically at account registration and at log in.
232+
Call [`.identify()`](https://mixpanel.github.io/mixpanel-react-native/Mixpanel.html#identify) when you know the identity of the current user, passing in their user ID as an argument. This is typically at account registration and at log in.
233233

234234
**Example Usage**
235235
```javascript

pages/docs/tracking-methods/sdks/swift.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -562,7 +562,7 @@ A few commonly used group methods are highlighted below:
562562

563563
## Session Replay
564564

565-
Install the [Session Replay SDK for Swift](/docs/tracking-methods/sdks/android/swift-replay) to record replay data. Learn more about [Session Replay](/docs/session-replay) and [implementing Session Replay on iOS](/docs/session-replay/implement-session-replay/session-replay-ios).
565+
Install the [Session Replay SDK for Swift](/docs/tracking-methods/sdks/swift/swift-replay) to record replay data. Learn more about [Session Replay](/docs/session-replay) and [implementing Session Replay on iOS](/docs/session-replay/implement-session-replay/session-replay-ios).
566566

567567
## Debugging and Logging
568568

redirects/developer-mixpanel-com.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@
1313
/developer-docs-redirect/collection-via-a-proxy /docs/tracking-methods/sdks/javascript
1414
/developer-docs-redirect/custom-query /docs/reports/apps/jql
1515
/developer-docs-redirect/data-discrepancy-faq /docs/data-pipelines#faq
16+
/developer-docs-redirect/data-model /docs/data-structure/concepts
1617
/developer-docs-redirect/data-pipelines /docs/data-pipelines
1718
/developer-docs-redirect/data-structure-deep-dive /docs/how-it-works/concepts
1819
/developer-docs-redirect/data-warehouse-export https://developer.mixpanel.com/reference/create-warehouse-pipeline

redirects/local.txt

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -45,12 +45,14 @@
4545
/docs/analysis/users /docs/users
4646
/docs/best-practices/analytics-strategy/engagement /docs/tracking-best-practices/tracking-plan
4747
/docs/best-practices/adoption https://mixpanel.com/blog/establish-a-product-analytics-practice/
48-
/docs/best-practices/analytics-strategy /docs/tutorials/analytics-strategy
49-
/docs/best-practices/analytics-strategy/overview /docs/best-practices/analytics-strategy
48+
/docs/best-practices/analytics-strategy /guides/plan/framework
49+
/docs/best-practices/analytics-strategy/overview /guides/plan/framework
50+
/docs/best-practices/analytics-strategy/retention /guides/launch/track-user-retention
5051
/docs/best-practices/create-a-tracking-plan /docs/tracking-best-practices/tracking-plan
5152
/docs/best-practices/developer-environments /docs/tracking-best-practices/developer-environments
5253
/docs/best-practices/project-setup /docs/orgs-and-projects/managing-projects
5354
/docs/best-practices/server-side-best-practices /docs/tracking-best-practices/server-side-best-practices
55+
/docs/boards/advanced /docs/boards
5456
/docs/boards/overview /docs/boards
5557
/docs/cohort-sync/overview /docs/cohort-sync
5658
/docs/data-pipelines/integrations/amazon-s3 /docs/data-pipelines/old-pipelines/integrations/schematized-aws-pipeline
@@ -68,6 +70,7 @@
6870
/docs/debugging/bot-traffic /docs/tracking-best-practices/bot-traffic
6971
/docs/debugging/distinct-id-limits /docs/tracking-best-practices/hot-shard-limits
7072
/docs/debugging/overview /docs/tracking-best-practices/debugging
73+
/docs/features/revenue_analytics /guides/launch/revenue-analytics
7174
/docs/features/session-replay /docs/session-replay
7275
/docs/formulas /changelogs/2023-09-19-formulas
7376
/docs/funnels /docs/reports/funnels
@@ -162,11 +165,18 @@
162165
/docs/pricing/pricing_faqs /docs/pricing#faqs
163166
/docs/privacy/overview /docs/privacy
164167
/docs/quickstart/connect-your-data /docs/quickstart/install-mixpanel
168+
/docs/quickstart/track-events /docs/quickstart/capture-events/track-events
165169
/docs/quickstart/what-to-track /docs/what-to-track
166170
/docs/reports/funnels#counting-method /docs/reports/funnels#measurements
167171
/docs/reports/overview /docs/reports
168172
/docs/reports/segmentation /docs/reports/insights
173+
/docs/session-replay/session-replay-web#server-side-stitching-beta /docs/session-replay#server-side-stitching
174+
/docs/session-replay/session-replay-web /docs/session-replay/implement-session-replay/session-replay-web
175+
/docs/session-replay/session-replay-ios /docs/session-replay/implement-session-replay/session-replay-ios
176+
/docs/session-replay/session-replay-android /docs/session-replay/implement-session-replay/session-replay-android
169177
/docs/tracking-best-practices/distinct-id-limits /docs/tracking-best-practices/hot-shard-limits
178+
/docs/tracking-methods/data-warehouse /docs/tracking-methods/warehouse-connectors
179+
/docs/tracking-methods/data-warehouse#mirror /docs/tracking-methods/warehouse-connectors#mirror
170180
/docs/tracking-methods/data-warehouse/bigquery /docs/tracking-methods/warehouse-connectors
171181
/docs/tracking-methods/data-warehouse/column-types /docs/tracking-methods/warehouse-connectors
172182
/docs/tracking-methods/data-warehouse/databricks /docs/tracking-methods/warehouse-connectors
@@ -262,12 +272,3 @@
262272
/docs/users/overview /docs/users
263273
/guides /guides/onboarding-overview/
264274
/guides/analytics-strategy /guides/plan/framework
265-
/docs/features/revenue_analytics /guides/launch/revenue-analytics
266-
/docs/tracking-methods/data-warehouse#mirror /docs/tracking-methods/warehouse-connectors#mirror
267-
/docs/tracking-methods/data-warehouse /docs/tracking-methods/warehouse-connectors
268-
/docs/boards/advanced /docs/boards
269-
/docs/quickstart/track-events /docs/quickstart/capture-events/track-events
270-
/docs/session-replay/session-replay-web#server-side-stitching-beta /docs/session-replay#server-side-stitching
271-
/docs/session-replay/session-replay-web /session-replay/implement-session-replay/session-replay-web
272-
/docs/session-replay/session-replay-ios /docs/session-replay/implement-session-replay/session-replay-ios
273-
/docs/session-replay/session-replay-android /docs/session-replay/implement-session-replay/session-replay-android

0 commit comments

Comments
 (0)