Integrate AEM Forms with Adobe Experience Platform

Transcript

Creating a profile schema is the first step in establishing the integration between AEM forms and Adobe Experience Platform, AEP. As part of the schema configuration, the Personal Contact Details field group was added to capture standard profile attributes. Within this field group, the email address field was designated as the primary identity and associated with the email namespace to enable identity resolution in real-time customer profile. Additional custom fields were defined to capture users’ interests in various Adobe Cloud solutions. These fields were grouped under the Adobe Cloud Preference field group to logically organize preference-related attributes. Finally, the schema was enabled for profile, allowing the data ingested against this schema to participate in real-time customer profile and be available for profile-based use cases. Download the sample data file generated from the schema. This file will be used later in the course for data mapping. A dataset was created based on the previously defined schema to store and manage the ingested profile data. This dataset is associated with the profile-enabled schema, allowing the data to flow into real-time customer profile. HTTP streaming in Adobe Experience Platform is a real-time data ingestion method that allows data to be sent to AEP through a secure HTTP endpoint. Instead of uploading files in batches, data is transmitted as it is generated, enabling immediate processing and near real-time profile updates. A new HTTP streaming endpoint was created using the sample data file downloaded earlier to define the expected data structure. A streaming connection was then associated with the previously created dataset, ensuring that incoming data is ingested into the correct dataset and made available for real-time customer profile and related use cases. During the creation of the HTTP streaming connection, source fields from the sample JSON file are mapped to the corresponding target fields in the XDM schema. The mapping interface confirms that all required and identity fields have been successfully mapped, with no errors. Proper field mapping ensures that incoming streaming data aligns with the defined schema structure, allowing the data to be correctly ingested into the associated dataset and made available for real-time customer profile. Once the mapping is completed, make a note of the streaming endpoint URL and the associated dataflow ID, as both are required when configuring the submit action of an adaptive form. The streaming endpoint URL is used to send form data to Adobe Experience Platform, while the dataflow ID ensures the submitted data is routed to the correct dataset for ingestion. An adaptive form based on core components is created. To configure the form for data collection in Adobe Experience Platform, AEP, navigate to the Data tab and select the Adobe Experience Platform card. Under Cloud Configuration, choose the cloud configuration created earlier in the course. Then, select the appropriate profile schema and the required field groups to be included in the form. In the Submission tab, select Submit to Adobe Experience Platform as the submit action. In the Properties panel, choose the appropriate XDM schema, then enter the streaming URL and dataflow ID, obtained from the HTTP streaming connection that was created earlier. This ensures the form data is correctly routed and streamed to AEP for ingestion. Finally, provide a meaningful name to the form and complete the process of form creation. Open the newly created form in edit mode and add a submit button to the form. For this use case, only the essential fields required to capture the necessary data have been included in the form. This ensures the form remains simple, focused, and aligned with the intended data collection requirements. The form is then tested using sample user information and preferences to ensure the submission process works as expected. Upon submission, a profile is created in Adobe Experience Platform using the email address as the primary identity. The selected options capture the user’s preferences for different Adobe Cloud solutions and are stored as profile attributes in AEP. After the form is successfully submitted, a basic thank you message is displayed to the user. The created profile is verified in Adobe Experience Platform by searching using the email address. The profile view confirms that the submitted user information and Adobe Cloud solution preferences have been successfully ingested and stored.