From fbb01d811b744ccc0605d1e561b2ed3829f5bbac Mon Sep 17 00:00:00 2001 From: "joshua.mccrowell" Date: Thu, 18 Apr 2024 12:35:03 -0400 Subject: [PATCH] Removing a link to a non-existent section --- .../custom_data/custom_events/nested_objects.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md b/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md index 20e114833f7..dcd4b6b24e5 100644 --- a/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md +++ b/_docs/_user_guide/data_and_analytics/custom_data/custom_events/nested_objects.md @@ -39,12 +39,11 @@ To access the nested data in your custom event, generate a schema for each event After generating a schema, you can reference the nested data during segmentation and personalization. Refer to the following sections for usage examples: -- API request body -- Liquid templating -- Message triggering -- Segmentation -- Personalization -- Event property segmentation +- [API request body](#api-request-body) +- [Liquid templating](#liquid-templating) +- [Message triggering](#message-triggering) +- [Segmentation](#segmentation) +- [Personalization](#personalization) ### API request body