diff --git a/gatsby-config.js b/gatsby-config.js index 26a832d893..020d6a12c7 100644 --- a/gatsby-config.js +++ b/gatsby-config.js @@ -585,22 +585,22 @@ module.exports = { { title: "Adobe Experience Platform Location Service", - path: "/documentation/places", + path: "/documentation/solution-extensions/places", pages: [{ title: "Overview", - path: "/documentation/places" + path: "/documentation/solution-extensions/places" }, { title: "API reference", - path: "documentation/places/api-reference.md" + path: "documentation/solution-extensions/places/api-reference.md" }, { title: "Event forwarding to Adobe Experience Platform", - path: "documentation/places/places-to-platform.md" + path: "documentation/solution-extensions/places/places-to-platform.md" }, { title: "Release notes", - path: "documentation/places/release-notes.md" + path: "documentation/solution-extensions/places/release-notes.md" } ] }, diff --git a/src/pages/documentation/base-extensions/mobile-core/api-reference.md b/src/pages/documentation/base-extensions/mobile-core/api-reference.md index 25488695d2..67251a52c0 100644 --- a/src/pages/documentation/base-extensions/mobile-core/api-reference.md +++ b/src/pages/documentation/base-extensions/mobile-core/api-reference.md @@ -16,7 +16,7 @@ Programmatic updates made to the configuration can be cleared via the `clearUpda ## collectMessageInfo -User interactions with local or push notifications can be tracked by invoking the `collectMessageInfo` API. Please refer to [this page](../../documentation/adobe-campaign-standard#tracking-local-and-push-notification-message-interactions) for more information about tracking local and push notification message interactions. +User interactions with local or push notifications can be tracked by invoking the `collectMessageInfo` API. Please refer to [this page](../../solution-extensions/adobe-campaign-standard/index.md#tracking-local-and-push-notification-message-interactions) for more information about tracking local and push notification message interactions. ## collectLaunchInfo @@ -128,7 +128,7 @@ iOS ## getPrivacyStatus -You can use the `getPrivacyStatus` API to retrieve the current privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../resources/privacy-and-gdpr.md#getprivacystatus) +You can use the `getPrivacyStatus` API to retrieve the current privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../../resources/privacy-and-gdpr.md#getprivacystatus) ## getSdkIdentities @@ -147,7 +147,7 @@ To retrieve data as a JSON string from the SDKs and send this data to your serve -You must call the API below and retrieve identities stored in the SDK, **before** the user opts out.

This API does **not** include the identities stored in the Edge Identity extension. To retrieve the identities from the Edge Identity extension, use [getIdentities](../identity-for-edge-network/api-reference.md#getidentities). +You must call the API below and retrieve identities stored in the SDK, **before** the user opts out.

This API does **not** include the identities stored in the Edge Identity extension. To retrieve the identities from the Edge Identity extension, use [getIdentities](../../edge-extensions/identity-for-edge-network/api-reference.md#getidentities). @@ -332,7 +332,7 @@ Flutter ## setPrivacyStatus -You can use the `setPrivacyStatus` API to set the privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../resources/privacy-and-gdpr.md#setprivacystatus) API's. +You can use the `setPrivacyStatus` API to set the privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../../resources/privacy-and-gdpr.md#setprivacystatus) API's. ## setPushIdentifier diff --git a/src/pages/documentation/base-extensions/mobile-core/configuration/api-reference.md b/src/pages/documentation/base-extensions/mobile-core/configuration/api-reference.md index e266778dfc..54a75379a8 100644 --- a/src/pages/documentation/base-extensions/mobile-core/configuration/api-reference.md +++ b/src/pages/documentation/base-extensions/mobile-core/configuration/api-reference.md @@ -58,7 +58,7 @@ iOS This API is only available in Android. -You can bundle a JSON configuration file in the app's Assets folder to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](../#configure-with-app-id-per-environment) approach. +You can bundle a JSON configuration file in the app's Assets folder to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](./index.md#configure-with-app-id-per-environment) approach. @@ -68,7 +68,7 @@ Android ## configureWithFileInPath -You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](../#configure-with-app-id-per-environment) approach. +You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](./index.md#configure-with-app-id-per-environment) approach. To pass in a bundled path and file name: diff --git a/src/pages/documentation/base-extensions/mobile-core/configuration/index.md b/src/pages/documentation/base-extensions/mobile-core/configuration/index.md index 9bca8ce43e..2a3562f2b1 100644 --- a/src/pages/documentation/base-extensions/mobile-core/configuration/index.md +++ b/src/pages/documentation/base-extensions/mobile-core/configuration/index.md @@ -46,7 +46,7 @@ Keys that are not found on the current configuration are added when this method -Do not use this API to update the build.environment or any key with an environment prefix, because it can lead to unexpected behavior. For more information, read [Environment-aware configuration properties](./index.md#environment-aware-configuration-properties). +Do not use this API to update the build.environment or any key with an environment prefix, because it can lead to unexpected behavior. For more information, read [Environment-aware configuration properties](#environment-aware-configuration-properties). @@ -74,7 +74,7 @@ For implementation details, please refer to [Configuration API reference](./api- ## Using a bundled file configuration -You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](./index.md#configure-with-app-id-per-environment) approach. +You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](#configure-with-app-id-per-environment) approach. To download the JSON configuration file, use the following URL: diff --git a/src/pages/documentation/base-extensions/mobile-core/identity/api-reference.md b/src/pages/documentation/base-extensions/mobile-core/identity/api-reference.md index 016be8e940..012db98755 100644 --- a/src/pages/documentation/base-extensions/mobile-core/identity/api-reference.md +++ b/src/pages/documentation/base-extensions/mobile-core/identity/api-reference.md @@ -21,9 +21,9 @@ If the provided URL is null or empty, it is returned as is. Otherwise, the follo * The `adobe_mc` attribute is a URL encoded list that contains: * `MCMID` - Experience Cloud ID (ECID) * `MCORGID` - Experience Cloud Org ID - * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../adobe-analytics/api-reference.md#gettrackingidentifier) + * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../../solution-extensions/adobe-analytics/api-reference.md#gettrackingidentifier) * `TS` - A timestamp taken when this request was made -* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../adobe-analytics/api-reference.md#setvisitoridentifier). +* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../../solution-extensions/adobe-analytics/api-reference.md#setvisitoridentifier). This API is designed to handle the following URL formats: @@ -154,9 +154,9 @@ If an error occurs while retrieving the URL string, the callback handler will be * The `adobe_mc` attribute is an URL encoded list that contains: * `MCMID` - Experience Cloud ID (ECID) * `MCORGID` - Experience Cloud Org ID - * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../adobe-analytics/index.md) + * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../../solution-extensions/adobe-analytics/index.md) * `TS` - A timestamp taken when this request was made -* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../adobe-analytics/index.md). +* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../../solution-extensions/adobe-analytics/index.md). @@ -180,7 +180,7 @@ Flutter -This API is only available in Android and is deprecated starting in version 2.0.0 of the Identity extension. Use [`MobileCore.registerExtensions()`](../../api-reference.md#registerextensions) instead. +This API is only available in Android and is deprecated starting in version 2.0.0 of the Identity extension. Use [`MobileCore.registerExtensions()`](../api-reference.md#registerextensions) instead. The `registerExtension()` API registers the Identity extension with the Mobile Core extension. This API allows the extension to send and receive events to and from the Mobile SDK. @@ -203,11 +203,11 @@ Some example use cases for this API are: This API is **not** recommended for: -* Resetting a user's privacy settings; see [Privacy and GDPR](../../resources/privacy-and-gdpr.md). +* Resetting a user's privacy settings; see [Privacy and GDPR](../../../resources/privacy-and-gdpr.md). * Removing existing custom identifiers; use the [`syncIdentifier`](#syncidentifier) API instead. * Removing a previously synced advertising identifier after the advertising tracking settings were changed by the user; use the [`setAdvertisingIdentifier`](#setadvertisingidentifier) API instead. -See [`MobileCore.resetIdentities`](../../api-reference.md#resetidentities) for more details. +See [`MobileCore.resetIdentities`](../api-reference.md#resetidentities) for more details. ## setAdvertisingIdentifier diff --git a/src/pages/documentation/base-extensions/mobile-core/identity/push-sync.md b/src/pages/documentation/base-extensions/mobile-core/identity/push-sync.md index ea691da7b5..4a57906364 100644 --- a/src/pages/documentation/base-extensions/mobile-core/identity/push-sync.md +++ b/src/pages/documentation/base-extensions/mobile-core/identity/push-sync.md @@ -70,7 +70,7 @@ Launch your app with the device connected to an [Adobe Experience Platform Assur In the list of events, verify that you have an event with type `UPDATED_IDENTITY_RESPONSE`. In the details panel on the right, confirm that the following values are correct: * The value for `pushidentifier` should match the value that was sent in step 2 above. -* The value for mid should match the value for mid that is sent to Analytics. If you are using a [custom visitor identifier](../adobe-analytics/api-reference.md#setidentifier), this payload should also contain a vid variable with a value that matches the value that was used to identify this user. +* The value for mid should match the value for mid that is sent to Analytics. If you are using a [custom visitor identifier](../../../solution-extensions/adobe-analytics/api-reference.md#setidentifier), this payload should also contain a vid variable with a value that matches the value that was used to identify this user. ![Verify push identifier synced](./assets/push-sync/push-identities.png) diff --git a/src/pages/documentation/base-extensions/mobile-core/lifecycle/api-reference.md b/src/pages/documentation/base-extensions/mobile-core/lifecycle/api-reference.md index 632325515a..4a35f3c34f 100644 --- a/src/pages/documentation/base-extensions/mobile-core/lifecycle/api-reference.md +++ b/src/pages/documentation/base-extensions/mobile-core/lifecycle/api-reference.md @@ -84,7 +84,7 @@ iOS -Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../../api-reference.md#registerextensions) API instead. +Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../api-reference.md#registerextensions) API instead. Registers the Lifecycle extension with the Mobile Core. diff --git a/src/pages/documentation/base-extensions/mobile-core/lifecycle/event-reference.md b/src/pages/documentation/base-extensions/mobile-core/lifecycle/event-reference.md index d894af987e..6963110c20 100644 --- a/src/pages/documentation/base-extensions/mobile-core/lifecycle/event-reference.md +++ b/src/pages/documentation/base-extensions/mobile-core/lifecycle/event-reference.md @@ -96,7 +96,7 @@ This event is a response from the Lifecycle extension to notify that the applica -To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform). +To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../../edge-extensions/lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform). @@ -110,7 +110,7 @@ In Android, there is a 500 millisecond timeout between consecutive `lifecycleSta #### Data payload -The Lifecycle application foreground data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application, device, and environment when the event occurred. Please refer to [Lifecycle Application Foreground metrics](../../lifecycle-for-edge-network/metrics.md#lifecycle-application-foreground-metrics) for a list of metrics included with this event. +The Lifecycle application foreground data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application, device, and environment when the event occurred. Please refer to [Lifecycle Application Foreground metrics](../../../edge-extensions/lifecycle-for-edge-network/metrics.md#lifecycle-application-foreground-metrics) for a list of metrics included with this event. ### Lifecycle application background @@ -123,7 +123,7 @@ The event is generated by the Lifecycle extension when: -To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform). +To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../../edge-extensions/lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform). @@ -137,4 +137,4 @@ In Android, there is a 500 millisecond timeout between consecutive `lifecycleSta #### Data payload -The Lifecycle Application Background data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application close type and previous session length. Please refer to [Lifecycle Application Background metrics](../../lifecycle-for-edge-network/metrics.md#lifecycle-application-background-metrics) for a list of metrics included with this event. +The Lifecycle Application Background data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application close type and previous session length. Please refer to [Lifecycle Application Background metrics](../../../edge-extensions/lifecycle-for-edge-network/metrics.md#lifecycle-application-background-metrics) for a list of metrics included with this event. diff --git a/src/pages/documentation/base-extensions/mobile-core/lifecycle/ios.md b/src/pages/documentation/base-extensions/mobile-core/lifecycle/ios.md index 50e112afce..2c27e28066 100644 --- a/src/pages/documentation/base-extensions/mobile-core/lifecycle/ios.md +++ b/src/pages/documentation/base-extensions/mobile-core/lifecycle/ios.md @@ -12,7 +12,7 @@ keywords: -In version 4 of the iOS SDK, this implementation was completed automatically.

When upgrading to the Experience Platform SDK, you must add code to continue collecting Lifecycle metrics. For more information, see [Manual Lifecycle Implementation](../../upgrade-platform-sdks/lifecycle.md). +In version 4 of the iOS SDK, this implementation was completed automatically.

When upgrading to the Experience Platform SDK, you must add code to continue collecting Lifecycle metrics. For more information, see [Manual Lifecycle Implementation](../../../resources/upgrade-platform-sdks/lifecycle.md). ## Implementing Lifecycle metrics in iOS @@ -45,7 +45,7 @@ The following scenarios are known to falsely cause a crash to be reported by the * If you are debugging using Xcode, re-launching the app while it is running in the foreground will cause a crash. * You can avoid a crash in this scenario by backgrounding the app prior to re-launching the app from Xcode. * If your app is launched in the background because of an enabled background capability (e.g. - background fetch, location update), then `lifecycleStart` is called and the app never comes to the foreground, the next launch (whether in the background or foreground) will result in a crash. -* If you programmatically delete Adobe’s pause flag from `NSUserDefaults`, while the app is in the background, the next launch or resume causes a crash. +* If you programmatically delete Adobe's pause flag from `NSUserDefaults`, while the app is in the background, the next launch or resume causes a crash. ### How can I prevent false crashes from being reported? diff --git a/src/pages/documentation/base-extensions/mobile-core/lifecycle/tabs/index.md b/src/pages/documentation/base-extensions/mobile-core/lifecycle/tabs/index.md index b47898cb36..ac8e4a3315 100644 --- a/src/pages/documentation/base-extensions/mobile-core/lifecycle/tabs/index.md +++ b/src/pages/documentation/base-extensions/mobile-core/lifecycle/tabs/index.md @@ -10,7 +10,7 @@ Add the Lifecycle extension and its dependency, the [Mobile Core](../index.md) e -Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../resources/manage-gradle-dependencies.md) for more information. +Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../../../resources/manage-gradle-dependencies.md) for more information. diff --git a/src/pages/documentation/base-extensions/mobile-core/rules-engine/consequence-details.md b/src/pages/documentation/base-extensions/mobile-core/rules-engine/consequence-details.md index cfcaf72817..0272dd1a7d 100644 --- a/src/pages/documentation/base-extensions/mobile-core/rules-engine/consequence-details.md +++ b/src/pages/documentation/base-extensions/mobile-core/rules-engine/consequence-details.md @@ -17,7 +17,7 @@ The Adobe Experience Platform Mobile SDK supports multiple types of rule consequ ## Analytics consequence -This rule consequence is currently handled by the [Analytics](../../adobe-analytics/index.md) extension. +This rule consequence is currently handled by the [Analytics](../../../solution-extensions/adobe-analytics/index.md) extension. | Friendly name | Key | Type | Required | Description | | :--- | :--- | :--- | :--- | :--- | @@ -27,7 +27,7 @@ This rule consequence is currently handled by the [Analytics](../../adobe-analyt ## In-App message consequence -This rule consequence is currently handled by the [Campaign](../../adobe-campaign-standard/index.md) extension. +This rule consequence is currently handled by the [Campaign](../../../solution-extensions/adobe-campaign-standard/index.md) extension. | Friendly name | Key | Type | Required | Description | | :--- | :--- | :--- | :--- | :--- | @@ -92,4 +92,4 @@ This rule is currently handled by the [Mobile Core](../index.md) extension. | Friendly name | Key | Type | Required | Description | | :--- | :--- | :--- | :--- | :--- | -| Event data | `eventdata` | object | Yes | Dictionary of pairs to overlay on the triggering event's EventData. For more information, see the [attach data tutorial](../../user-guides/attach-data.md). | +| Event data | `eventdata` | object | Yes | Dictionary of pairs to overlay on the triggering event's EventData. For more information, see the [attach data tutorial](../../../resources/user-guides/attach-data.md). | diff --git a/src/pages/documentation/base-extensions/mobile-core/signal/api-reference.md b/src/pages/documentation/base-extensions/mobile-core/signal/api-reference.md index 9159d72779..d5b788f264 100644 --- a/src/pages/documentation/base-extensions/mobile-core/signal/api-reference.md +++ b/src/pages/documentation/base-extensions/mobile-core/signal/api-reference.md @@ -40,7 +40,7 @@ Flutter -Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../../api-reference.md#registerextensions) API instead. +Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../api-reference.md#registerextensions) API instead. Registers the Signal extension with the Mobile Core. @@ -56,4 +56,4 @@ Android ## collectPii -The Signal extension can be used to handle `collectPii` rules. For more information, see the [collectPii](../../api-reference.md#collectpii) API. +The Signal extension can be used to handle `collectPii` rules. For more information, see the [collectPii](../api-reference.md#collectpii) API. diff --git a/src/pages/documentation/base-extensions/mobile-core/signal/index.md b/src/pages/documentation/base-extensions/mobile-core/signal/index.md index 1cfb416a78..b946366cfe 100644 --- a/src/pages/documentation/base-extensions/mobile-core/signal/index.md +++ b/src/pages/documentation/base-extensions/mobile-core/signal/index.md @@ -36,7 +36,7 @@ For more information about creating and configuring a rule in the Data Collectio -Using dynamic dependency versions is not recommended for production apps. Refer to this [page](../resources/manage-gradle-dependencies.md) for managing gradle dependencies. +Using dynamic dependency versions is not recommended for production apps. Refer to this [page](../../../resources/manage-gradle-dependencies.md) for managing gradle dependencies. diff --git a/src/pages/documentation/base-extensions/mobile-core/signal/rules-engine-integration.md b/src/pages/documentation/base-extensions/mobile-core/signal/rules-engine-integration.md index 67bb2e0cf9..16c3b45e5f 100644 --- a/src/pages/documentation/base-extensions/mobile-core/signal/rules-engine-integration.md +++ b/src/pages/documentation/base-extensions/mobile-core/signal/rules-engine-integration.md @@ -98,7 +98,7 @@ The following example shows how to use the data that is passed to the MobileCore ![Send Postback action example](./assets/rules-engine-integration/send-postback-action.png) -For more information about `collectPii` and its usage, see `collectPii` in the [Mobile Core API reference](../../api-reference.md#collectpii). +For more information about `collectPii` and its usage, see `collectPii` in the [Mobile Core API reference](../api-reference.md#collectpii). ### Using tokens in Open URL rule actions diff --git a/src/pages/documentation/base-extensions/mobile-core/signal/tabs/index.md b/src/pages/documentation/base-extensions/mobile-core/signal/tabs/index.md index 4e199a11fb..dacc8fa9b4 100644 --- a/src/pages/documentation/base-extensions/mobile-core/signal/tabs/index.md +++ b/src/pages/documentation/base-extensions/mobile-core/signal/tabs/index.md @@ -10,7 +10,7 @@ Add the Signal extension and its dependency, the [Mobile Core](../index.md) exte -Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../resources/manage-gradle-dependencies.md) for more information. +Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../../../resources/manage-gradle-dependencies.md) for more information. diff --git a/src/pages/documentation/base-extensions/platform-assurance-sdk/common-issues.md b/src/pages/documentation/base-extensions/platform-assurance-sdk/common-issues.md index 53f28570fd..2638ab31b1 100644 --- a/src/pages/documentation/base-extensions/platform-assurance-sdk/common-issues.md +++ b/src/pages/documentation/base-extensions/platform-assurance-sdk/common-issues.md @@ -71,7 +71,7 @@ Or ensuring internet connectivity on the device/simulator. If you see an Invalid Mobile SDK Configuration error (see screenshot below), verify the following: 1. Mobile Core is [configured](../mobile-core/configuration/api-reference.md) -2. Configuration in the Data Collection UI is [published](../getting-started/create-a-mobile-property.md#publish-the-configuration) +2. Configuration in the Data Collection UI is [published](../../home/getting-started/create-a-mobile-property.md#publish-the-configuration) 3. Ensure the device/simulator has internet connectivity ![Invalid Mobile SDK configuration](./assets/common-issues/assurance-invalid-configuration-error.png) diff --git a/src/pages/documentation/base-extensions/platform-assurance-sdk/tabs/index.md b/src/pages/documentation/base-extensions/platform-assurance-sdk/tabs/index.md index 0893ccf53e..be2792cc53 100644 --- a/src/pages/documentation/base-extensions/platform-assurance-sdk/tabs/index.md +++ b/src/pages/documentation/base-extensions/platform-assurance-sdk/tabs/index.md @@ -14,7 +14,7 @@ implementation 'com.adobe.marketing.mobile:assurance' -Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../resources/manage-gradle-dependencies.md) for more information. +Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../../resources/manage-gradle-dependencies.md) for more information. diff --git a/src/pages/documentation/base-extensions/profile/api-reference.md b/src/pages/documentation/base-extensions/profile/api-reference.md index 8ccf532396..3ee8df411a 100644 --- a/src/pages/documentation/base-extensions/profile/api-reference.md +++ b/src/pages/documentation/base-extensions/profile/api-reference.md @@ -46,7 +46,7 @@ iOS -This API is only available in Android and is deprecated starting in version 2.0.0 of the UserProfile extension. Use [`MobileCore.registerExtensions()`](../api-reference.md#registerextensions) API instead. +This API is only available in Android and is deprecated starting in version 2.0.0 of the UserProfile extension. Use [`MobileCore.registerExtensions()`](../mobile-core/api-reference.md#registerextensions) API instead. Registers the Profile extension with the Mobile Core extension. diff --git a/src/pages/documentation/base-extensions/profile/tabs/index.md b/src/pages/documentation/base-extensions/profile/tabs/index.md index 5a98ecd7af..ef03bbfca7 100644 --- a/src/pages/documentation/base-extensions/profile/tabs/index.md +++ b/src/pages/documentation/base-extensions/profile/tabs/index.md @@ -14,7 +14,7 @@ implementation 'com.adobe.marketing.mobile:userprofile' -Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../resources/manage-gradle-dependencies.md) for more information. +Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../../resources/manage-gradle-dependencies.md) for more information. diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/api-reference.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/api-reference.md index 0cef0c02f0..0cbf38372e 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/api-reference.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/api-reference.md @@ -70,7 +70,7 @@ iOS -Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../mobile-core/api-reference.md#registerextensions) API instead. +Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../../base-extensions/mobile-core/api-reference.md#registerextensions) API instead. @@ -85,7 +85,7 @@ Android This API call can lead to unintended SDK behavior, e.g. resetting of Experience Cloud ID (ECID). So it should be sparingly used and caution should be followed! This `MobileCore` API is a request to each extension to reset its identities. Every extension responds to this request in its own unique manner. For example, Optimize extension uses this API call to clear out its client-side in-memory propositions cache. -For details on syntax, usage and availability, refer to [Mobile Core - Reset identities](../mobile-core/api-reference.md#resetidentities). +For details on syntax, usage and availability, refer to [Mobile Core - Reset identities](../../base-extensions/mobile-core/api-reference.md#resetidentities). ## updatePropositions diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/index.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/index.md index 9ae5ae698a..959ed29da2 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/index.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/index.md @@ -24,7 +24,7 @@ Before starting, make sure the following steps are completed. ### Configure the Datastream for Adobe Target and/or Journey Optimizer - Offer Decisioning -On [Experience Platform Data Collection](https://experience.adobe.com/#/data-collection/), navigate to **Data Collection** > **Datatreams** using the left navigation panel. Select an existing datastream or create a new datastream. For more details, see the [configure datastreams guide](../getting-started/configure-datastreams.md). +On [Experience Platform Data Collection](https://experience.adobe.com/#/data-collection/), navigate to **Data Collection** > **Datatreams** using the left navigation panel. Select an existing datastream or create a new datastream. For more details, see the [configure datastreams guide](../../home/getting-started/configure-datastreams.md). 1. In the datastream, click on the desired environment from the list. Make sure **Adobe Experience Platform** section is enabled and configured with the required information like **Sandbox** and **Event Dataset**. 2. For Journey Optimizer - Offer Decisioning, navigate to **Adobe Experience Platform** section and enable **Offer Decisioning** checkbox. @@ -40,7 +40,7 @@ On [Experience Platform Data Collection](https://experience.adobe.com/#/data-col 1. In your mobile property, navigate to **Extensions** in the left navigation panel and click on the **Catalog** tab. 2. In the extensions Catalog, search or locate the **Adobe Journey Optimizer - Decisioning** extension, and click **Install**. 3. Since an extension configuration is not necessary, click **Save**. -4. Follow the publishing process to update SDK configuration. For more details, see the [publish the configuration guide](../getting-started/create-a-mobile-property.md.md#publish-the-configuration). +4. Follow the publishing process to update SDK configuration. For more details, see the [publish the configuration guide](../../home/getting-started/create-a-mobile-property.md#publish-the-configuration). ![Adobe Journey Optimizer - Decisioning extension configuration](./assets/index/configuration.png) @@ -48,7 +48,7 @@ On [Experience Platform Data Collection](https://experience.adobe.com/#/data-col -For the AEPOptimize APIs to work properly, you need to integrate Mobile Core and Edge extensions in your mobile app. For more details see, documentation on [Mobile Core](../mobile-core/index.md) and [Adobe Experience Platform Edge Network](../edge-network/index.md). +For the AEPOptimize APIs to work properly, you need to integrate Mobile Core and Edge extensions in your mobile app. For more details see, documentation on [Mobile Core](../../base-extensions/mobile-core/index.md) and [Adobe Experience Platform Edge Network](../../edge-extensions/edge-network/index.md). ### Install the Experience Platform Mobile SDK @@ -143,7 +143,7 @@ To use Target Third Party ID in the Experience Edge mobile workflows, the corres ![Target Third Party ID configuration](./assets/index/target-tpid.png) -In your mobile application, integrate the Identity for Edge Network extension to add the Target Third Party ID in the Identity Map in the personalization query request to the Edge network when calling the `updatePropositions` API. For more details, see the [Identity for Edge Network - updateIdentities API](../identity-for-edge-network/api-reference.md#updateidentities). +In your mobile application, integrate the Identity for Edge Network extension to add the Target Third Party ID in the Identity Map in the personalization query request to the Edge network when calling the `updatePropositions` API. For more details, see the [Identity for Edge Network - updateIdentities API](../../edge-extensions/identity-for-edge-network/api-reference.md#updateidentities). @@ -227,7 +227,7 @@ After you finish your rule configuration, verify the rule details are as shown b ![Adobe Journey Optimizer - Decisioning extension Lifecycle rule Configuration](./assets/index/lifecycle-rule.png) 1. Click on **Save**. -2. [Republish your configuration](../getting-started/create-a-mobile-property.md#publish-the-configuration) to the desired environment. +2. [Republish your configuration](../../home/getting-started/create-a-mobile-property.md#publish-the-configuration) to the desired environment. ### Analytics for Target (A4T) @@ -283,7 +283,7 @@ iOS -The Edge `sendEvent` API can then be used to send this tracking XDM data along with any additional XDM and freeform data to the Experience Edge network. Additionally, an override dataset can also be specified for tracking data. For more details, see [Edge - sendEvent API](../edge-network/api-reference.md#sendevent). +The Edge `sendEvent` API can then be used to send this tracking XDM data along with any additional XDM and freeform data to the Experience Edge network. Additionally, an override dataset can also be specified for tracking data. For more details, see [Edge - sendEvent API](../../edge-extensions/edge-network/api-reference.md#sendevent). @@ -297,7 +297,7 @@ iOS ## Configuration keys -To update the SDK configuration programmatically, use the following information to change the Optimize extension configuration values. For more information, see the [programmatic updates to Configuration guide](../mobile-core/configuration/api-reference.md#updateconfiguration). +To update the SDK configuration programmatically, use the following information to change the Optimize extension configuration values. For more information, see the [programmatic updates to Configuration guide](../../base-extensions/mobile-core/configuration/api-reference.md#updateconfiguration). | Key | Required | Description | Data Type | | :--- | :--- | :--- | :--- | @@ -305,4 +305,4 @@ To update the SDK configuration programmatically, use the following information -If the override dataset is used for proposition tracking, make sure the corresponding schema definition contains the `Experience Event - Proposition Interaction` field group. For more information, see the [setup schemas and datasets guide](../getting-started/set-up-schemas-and-datasets.md). +If the override dataset is used for proposition tracking, make sure the corresponding schema definition contains the `Experience Event - Proposition Interaction` field group. For more information, see the [setup schemas and datasets guide](../../home/getting-started/set-up-schemas-and-datasets.md). diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/api-reference.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/api-reference.md index 794ef0f21d..ea18a64a64 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/api-reference.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/api-reference.md @@ -105,7 +105,7 @@ public static void getPropositions(final List decisionScopes, fin ``` * _decisionScopes_ is a list of decision scopes for which propositions are requested. -* _callback_ `call` method is invoked with propositions map of type `Map`. If the callback is an instance of [AdobeCallbackWithError](../mobile-core/api-reference.md#adobecallbackwitherror), and if the operation times out or an error occurs in retrieving propositions, the `fail` method is invoked with the appropriate [AdobeError](../mobile-core/api-reference.md#adobeerror). +* _callback_ `call` method is invoked with propositions map of type `Map`. If the callback is an instance of [AdobeCallbackWithError](../../base-extensions/mobile-core/api-reference.md#adobecallbackwitherror), and if the operation times out or an error occurs in retrieving propositions, the `fail` method is invoked with the appropriate [AdobeError](../../base-extensions/mobile-core/api-reference.md#adobeerror). #### Example diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/index.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/index.md index a435fba3ef..eb33c4c48c 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/index.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer-decisioning/tabs/index.md @@ -16,7 +16,7 @@ implementation 'com.adobe.marketing.mobile:optimize' -Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../resources/manage-gradle-dependencies.md) for more information. +Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../../resources/manage-gradle-dependencies.md) for more information. diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/api-reference.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/api-reference.md index 6de07f2552..0fa0373ab4 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/api-reference.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/api-reference.md @@ -43,7 +43,7 @@ iOS -Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../mobile-core/api-reference.md#registerextensions) API instead. +Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../../base-extensions/mobile-core/api-reference.md#registerextensions) API instead. diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/index.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/index.md index e903d84e2b..87ccc76658 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/index.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/index.md @@ -20,13 +20,13 @@ The following documentation details how to use the extension and required config 1. Read the tutorial on [getting started with push configuration](https://experienceleague.adobe.com/docs/journey-optimizer/using/get-started/configuration/push-config/push-gs.html) to learn how to configure push channels in Adobe Journey Optimizer. 2. [Update your app's Datastream](#update-datastream-with-profile-dataset) in [Adobe Experience Platform Data Collection](https://experience.adobe.com/#/data-collection/) 3. Integrate with following extensions: - * [Mobile Core](../mobile-core/index.md) - * [Adobe Experience Platform Edge Network](../edge-network/index.md) - * [Identity for Edge Network](../identity-for-edge-network/index.md) + * [Mobile Core](../../base-extensions/mobile-core/index.md) + * [Adobe Experience Platform Edge Network](../../edge-extensions/edge-network/index.md) + * [Identity for Edge Network](../../edge-extensions/identity-for-edge-network/index.md) ### Update Datastream with a Profile dataset -Navigate to a previously configured Datastream by following the instructions in the [configure datastreams tutorial](../getting-started/configure-datastreams.md) in [Adobe Experience Platform Data Collection](https://experience.adobe.com/#/data-collection/) and select **Add Service**. In the service dropdown select **Adobe Experience Platform**. +Navigate to a previously configured Datastream by following the instructions in the [configure datastreams tutorial](../../home/getting-started/configure-datastreams.md) in [Adobe Experience Platform Data Collection](https://experience.adobe.com/#/data-collection/) and select **Add Service**. In the service dropdown select **Adobe Experience Platform**. * In the **Event Dataset** dropdown, select a dataset previously created in the [Adobe Experience Platform](https://experience.adobe.com/#/platform) UI. * In the **Profile Dataset** dropdown, select the **AJO Push Profile Dataset**. @@ -38,7 +38,7 @@ Navigate to a previously configured Datastream by following the instructions in ## Set up a mobile property in Adobe Data Collection -To learn how to create the mobile property, please read the tutorial on [creating a mobile property](../getting-started/create-a-mobile-property.md) +To learn how to create the mobile property, please read the tutorial on [creating a mobile property](../../home/getting-started/create-a-mobile-property.md) Now that a mobile property is created, we can setup the Adobe Journey Optimizer extension. @@ -51,11 +51,11 @@ Go to the [Experience Platform Data Collection UI](https://experience.adobe.com/ 1. Navigate to the **Catalog** tab, locate the **Adobe Journey Optimizer** extension, and select **Install** 2. Select the pre-created **AJO Push Tracking Experience Event Dataset** from the **Event Dataset** dropdown. 3. Select **Save**. -4. [Follow the publishing process](../getting-started/create-a-mobile-property.md#publish-the-configuration) to update SDK configuration. +4. [Follow the publishing process](../../home/getting-started/create-a-mobile-property.md#publish-the-configuration) to update SDK configuration. -The datasets selected should use a schema that uses the "Push Notification Tracking" XDM field group. The pre-created CJM Push Tracking Dataset contains this XDM field group in its schema definition. For more information, please read the tutorial on [setting up schemas and datasets](../getting-started/set-up-schemas-and-datasets.md). +The datasets selected should use a schema that uses the "Push Notification Tracking" XDM field group. The pre-created CJM Push Tracking Dataset contains this XDM field group in its schema definition. For more information, please read the tutorial on [setting up schemas and datasets](../../home/getting-started/set-up-schemas-and-datasets.md). ![](./assets/index/configuration.png) diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tabs/index.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tabs/index.md index 34c970dd7a..f903694831 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tabs/index.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tabs/index.md @@ -18,7 +18,7 @@ implementation "com.adobe.marketing.mobile:messaging" -Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../resources/manage-gradle-dependencies.md) for more information. +Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../../resources/manage-gradle-dependencies.md) for more information. diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/tabs/native-from-javascript.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/tabs/native-from-javascript.md index 0e1f2f5b9d..04aee096e4 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/tabs/native-from-javascript.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/tabs/native-from-javascript.md @@ -26,7 +26,7 @@ public boolean shouldShowMessage(FullscreenMessage fullscreenMessage) { -In the `shouldShowMessage` function of the `MessagingDelegate`, call [`handleJavascriptMessage(_:withHandler)`](./class-message.md#handlejavascriptmessage_withhandler) to register your handler. +In the `shouldShowMessage` function of the `MessagingDelegate`, call `handleJavascriptMessage(_:withHandler)` to register your handler. The name of the message you intend to pass from the JavaScript side should be specified in the first parameter. diff --git a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/validate-messages.md b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/validate-messages.md index f5eb3fb2b1..f65289d8f2 100644 --- a/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/validate-messages.md +++ b/src/pages/documentation/edge-extensions/adobe-journey-optimizer/tutorials/validate-messages.md @@ -21,7 +21,7 @@ This guide will walk you through steps necessary to ensure your app is properly ## Prerequisites -* Your app must have the **AEPMessaging** SDK extension installed. Integrate **AEPMessaging** by following the guide on [setting up AEPMessaging SDK](../setup.md). +* Your app must have the **AEPMessaging** SDK extension installed. Integrate **AEPMessaging** by following the guide on [setting up AEPMessaging SDK](../index.md). * This troubleshooting guide uses validation provided by the **AEPAssurance** extension and the **Adobe Assurance UI**. Integrate **AEPAssurance** in your application by following the [Adobe Experience Platform Assurance installation guide](https://experienceleague.adobe.com/docs/experience-platform/assurance/home.html). @@ -46,7 +46,7 @@ Ensure that your app has registered all necessary AEP SDK extensions by doing th -If your app uses the [Edge Consent extension](../../consent-for-edge-network/index.md), the device must be consenting (i.e. - a consent value of `Yes`) in order to download in-app messages. +If your app uses the [Edge Consent extension](../../../edge-extensions/consent-for-edge-network/index.md), the device must be consenting (i.e. - a consent value of `Yes`) in order to download in-app messages. A sample view in the Assurance UI can be seen below: @@ -127,7 +127,7 @@ Using the IAM plugin you can do the following for each message downloaded by the ### Q: What do I do when one of the required extensions is missing? -**A:** Ensure that each required extension is linked to your project and registered by `MobileCore`. For more information, please read the [Mobile Core API reference](../../mobile-core/api-reference.md#registerextensions). +**A:** Ensure that each required extension is linked to your project and registered by `MobileCore`. For more information, please read the [Mobile Core API reference](../../../base-extensions/mobile-core/api-reference.md#registerextensions). ### Q: Why can't I find an event named `Retrieve message definitions`?