Reorg data structure (#1348)

* Update _meta.json

* Create _meta.json

* Create data-type.mdx

* Create default-properties.mdx

* Create reserved-properties.mdx

* Create group-analytics.mdx

* Create properties.mdx

* Update and rename events-and-properties.md to events-and-properties.mdx

* Update and rename user-profiles.md to user-profiles.mdx

* Update integrations.mdx

* Create ad-spend.mdx

* Update _meta.json

* Create traffic-attribution.mdx

* Update _meta.json

* Update and rename concepts.md to concepts.mdx

* Delete pages/docs/data-structure/advanced directory

* remove list and list of object support.

- it now lives in Data Type

* Update 2023-06-06-ad-data.mdx

* Update group-analytics.mdx

* Update user-profiles.mdx

* Update billing.md

* Update migrating-to-simplified-id-merge-system.md

* Update query.openapi.yaml

* Update events-and-properties.mdx

* Update default-properties.mdx

* Update reserved-properties.mdx

* remove undefined. now in data type

* Update data-type.mdx

* Update protecting-user-data.mdx

* Delete pages/docs/data-structure/property-reference.md

* Update local.txt

openapi/src/query.openapi.yaml

@@ -1129,7 +1129,7 @@ paths:
                 data_group_id:
                   type: string
                   description: >-
-                    The ID of the group key, used when querying group profiles, click [here](https://docs.mixpanel.com/docs/data-structure/advanced/group-analytics#exporting-group-profiles-via-api) for more info.
+                    The ID of the group key, used when querying group profiles, click [here](https://docs.mixpanel.com/docs/data-structure/group-analytics#exporting-group-profiles-via-api) for more info.
                 where:
                   type: string
                   description: >-

pages/changelogs/2023-06-06-ad-data.mdx

@@ -8,7 +8,7 @@ date: "2023-06-06"
 ---
 ![ad_spend](https://github.com/mixpanel/docs/assets/130083255/1d171623-615f-4b47-a54d-883306fcd30c)
 
-It’s easier than ever to start sending ad network data to Mixpanel with our [how-to guide](https://docs.mixpanel.com/docs/data-structure/advanced/ad-spend). 
+It’s easier than ever to start sending ad network data to Mixpanel with our [how-to guide](https://docs.mixpanel.com/docs/tracking-methods/integrations/ad-spend). 
 
 We walk you through every step of implementation so you can start analyzing your ad data in no time and monitor key ad performance metrics like (CPC) cost-per-click, (CPM) cost-per-impression and (CTR) click-through-rate. It’s a one time setup for a lifetime of tracking ad metrics.
 

pages/docs/data-structure/_meta.json

@@ -2,7 +2,7 @@
     "concepts": "Concepts",
     "events-and-properties": "Events & Properties",
     "user-profiles": "User Profiles",
+    "group-analytics": "Group Analytics",
     "lookup-tables": "Lookup Tables",
-    "property-reference": "Property Reference",
-    "advanced": "Advanced"
+    "property-reference": "Property Reference"
 }

pages/docs/data-structure/concepts.md → pages/docs/data-structure/concepts.mdx

@@ -8,10 +8,10 @@ Mixpanel data is stored and isolated within a [project](/docs/orgs-and-projects/
 
 | Types | Description |
 |----------|-------------------|
-| **Events** | Events describe actions that take place within your product. An event contains properties that describe the action. Events can also be joined with user profiles, group profiles, and lookup tables to enrich the data. <br><br> [Learn more about event properties](/docs/data-structure/events-and-properties) |
-| **User Profiles** | A user profile is a key/value store that holds state about a user. User profiles are joined to events on `event.distinct_id = user_profile.distinct_id`. <br><br> [Learn more about profile properties](/docs/data-structure/user-profiles) |
-| **Group Profiles** | A group profile is a key/value store that holds state about members of your group. Group profiles are joined to Events on your chosen _group key_. For example, if you create a new group key for `company_id` your events will be joined on `event.company_id = group_profile.company_id`. <br><br> [Learn more about group analytics](/docs/data-structure/advanced/group-analytics) |
-| **Lookup Tables** | A lookup table is a key/value store that holds state about an entity. Lookup tables are joined to events (and other profiles) on your chosen join key. For example, if you create a lookup table for "Songs" and specify the join key as `song_id`, your events will be joined on `event.song_id = lookup_table.song_id`. <br><br>[Learn more about lookup tables](/docs/data-structure/lookup-tables) |
+| **Events** | Events describe actions that take place within your product. An event contains properties that describe the action. Events can also be joined with user profiles, group profiles, and lookup tables to enrich the data. <br/><br/> [Learn more about event properties](/docs/data-structure/events-and-properties) |
+| **User Profiles** | A user profile is a key/value store that holds state about a user. User profiles are joined to events on `event.distinct_id = user_profile.distinct_id`. <br/><br/> [Learn more about profile properties](/docs/data-structure/user-profiles) |
+| **Group Profiles** | A group profile is a key/value store that holds state about members of your group. Group profiles are joined to Events on your chosen _group key_. For example, if you create a new group key for `company_id` your events will be joined on `event.company_id = group_profile.company_id`. <br/><br/> [Learn more about group analytics](/docs/data-structure/group-analytics) |
+| **Lookup Tables** | A lookup table is a key/value store that holds state about an entity. Lookup tables are joined to events (and other profiles) on your chosen join key. For example, if you create a lookup table for "Songs" and specify the join key as `song_id`, your events will be joined on `event.song_id = lookup_table.song_id`. <br/><br/>[Learn more about lookup tables](/docs/data-structure/lookup-tables) |
 
 ### Event Property vs User Profile Property
 
@@ -89,7 +89,7 @@ All three are key/value stores that augment your event data with additional meta
 
 **[User profiles](/docs/data-structure/user-profiles)** are joined to events via `distinct_id` which is the default indexing for Events. 
 
-**[Group profiles](/docs/data-structure/advanced/group-analytics)** are joined to events via an event property you specify as a group key. Once you create a new group key, we will add an additional index for your events on that property. This allows you to do funnels or retention by that property instead of by `distinct_id`.
+**[Group profiles](/docs/data-structure/group-analytics)** are joined to events via an event property you specify as a group key. Once you create a new group key, we will add an additional index for your events on that property. This allows you to do funnels or retention by that property instead of by `distinct_id`.
 
 **[Lookup tables](/docs/data-structure/lookup-tables)** are joined to events and user profiles using the join key that you specify. Unlike group profiles, your events are *not* indexed by the join key. You can use lookup table properties to do filtering, breakdowns, etc but you can't do things like funnels analysis using the join key for uniques. Note: Currently, group profile properties cannot be lookup table keys.