To use Adobe Experience Platform Launch Server Side, data must be sent to Adobe Experience Platform Edge Network using one or more of three options:
The Platform Web SDK and Platform Mobile SDK do not require deployment through Platform Launch Client Side. However, using Platform Launch Client Side to deploy these SDKs is the recommended approach.
After you send data to Edge network, you can toggle on Adobe solutions to send data there. To send data to a non-Adobe solution, you need to set that up in Platform Launch Server Side.
In Adobe Experience Platform, create your schema.
Create a new schema by selecting Schemas>Create Schema and choosing the XDM ExperienceEvent option.
Give the schema a name and short description.
You can add the “ExperienceEvent web details” mixin by selecting Add next to Mixins.
Multiple mixins can be added, if desired.
Save the schema and note the name you gave it.
For more information about schemas, see Experience Data Model (XDM) System Help.
In Platform Launch, create a property of type “Edge.”
Select New Property.
Name the property.
Choose the “Edge” platform type.
After you create the property, go to the Environments tab for the new property and make
note of the environment IDs. You can copy the Environment ID from the Environments tab to paste it when
creating an Edge configuration, if the Adobe Org used in Edge Configuration differs from the Adobe Org used
in Platform Launch Server Side. Otherwise, you can select the environment from a drop-down menu.
In Adobe Experience Platform Edge Configuration, create your edge configuration. You will need the Environment ID generated when you created the Platform Launch Server Side property.
Open the Adobe Experience Platform Edge Configuration interface through Platform Launch, from the link in the left rail.
Select New Edge Configuration.
Name the configuration and provide an optional description.
The description helps to identify configurations in a list of several configurations.
Next, configure Edge Network to send data to Launch Server Side, and to other Adobe products.
In the Edge Configuration UI, select the property you created.
Select the Development, Production, or Staging environment.
Or, to send data to a Launch Server Side environment outside the Adobe org, select **Switch to Advanced Mode and paste in an ID. The ID is provided when you create a Server Side property.
Toggle on the necessary tools and configure as required.
Adobe Analytics requires a report suite ID.
Platform Launch Server Side requires a property ID and environment ID, which is the publish path for the Launch Server Side property.
After configuring, make note of the Environment IDs for the new property.
In Platform Launch Client Side, create your property, then use the Adobe Experience Platform Web SDK extension to configure it.
Name the property.
You can have multiple instances of Alloy. For example, you might have different pre- and post-paywall tracking properties.
Select the Org ID.
Select the Edge Domain.
See the Web SDK extension documentation for more configuration options.
After all of the above is in place, you can build necessary data definitions, rules, and so on that leverage both Platform Launch Server Side and Platform Launch Client Side, but that need only a single request from the page.
Create a new page load rule using the Platform Web SDK extension and the “Send Event” action type:
Open the Rules tab, then select Create New Rule.
Name the rule.
Select Events Add.
Add an event by choosing an extension and one of the event types available for that extension, then configure the settings for the event. For example, select Core - Window Loaded.
Add an action using the Platform Web SDK extension. Select Send Event from the Action Type list, select the desired Instance (Alloy instance configured earlier), and then select a data element to add to the XDM Data block within the Alloy hit.
Leave the rest of the settings as default for this example, and select Save.
For another example, you might create a rule that sends the data layer to Edge if the user hovers over a specified button.
With the following in place, you can now create Platform Launch Server Side rules to forward data to