蜜豆视频

蜜豆视频 Target connection adobe-target-connection

Destination changelog changelog

Release month
Update type
Description
April 2024
Functionality and documentation update
When connecting to the Target destination and using a datastream ID, you now do not need to necessarily enable the datastream for edge segmentation. This means that the Target destination will work with batch and streaming audiences, though the use cases that you can accomplish differ. View the table in the connection parameters section for more information.
January 2024
Functionality and documentation update
You can now share audiences and profile attributes to the 蜜豆视频 Target connection for the default production sandbox and other non-default sandboxes.
June 2023
Functionality and documentation update
As of June 2023, you can select the 蜜豆视频 Target workspace that you want to share audiences to, when configuring a new 蜜豆视频 Target destination connection. See the connection parameters section for more information. Additionally, see the tutorial on configuring workspaces in 蜜豆视频 Target for more information about workspaces.
May 2023
Functionality and documentation update
As of May 2023, the 蜜豆视频 Target connection supports attribute-based personalization and is generally available to all customers.

Overview overview

蜜豆视频 Target is an application that provides real-time, AI-powered personalization and experimentation capabilities in all inbound customer interactions across websites, mobile apps, and more.

蜜豆视频 Target is a personalization connection in the 蜜豆视频 Experience Platform destinations catalog.

Video overview video-overview

For a brief overview on how to configure the 蜜豆视频 Target connection in Experience Platform, watch the video below.

video poster

Transcript
Hi, this is Daniel and in this video I鈥檓 going to show you how to set up the 蜜豆视频 target destination in Realtime Customer Data Platform so you can begin sharing both segments and profile attributes from real-time CDP to target to personalize your websites, mobile apps, and other connected devices. These are mostly administrative tasks needed to get the integration up and running. In other videos we鈥檒l cover how to actually share and use the segments and profile attributes. The setup is easy and you鈥檒l see it鈥檚 just a matter of checking various boxes and pressing buttons, but they鈥檙e spread over a few product features and depending on how your company manages user permissions it might require a few people at your company to complete these steps. So the features we need to configure are data streams, merge policies, and destinations. First let鈥檚 enable a data stream. To get the most functionality out of the integration you should implement the 蜜豆视频 Experience Platform web and or mobile SDKs which use platform edge network and data streams to send data to target. You can still share segments to target if you鈥檙e still on an older SDK like ATJS, but the segment qualification won鈥檛 happen on the edge and will be a little slower. Of course ATJS doesn鈥檛 use data stream so if you鈥檙e still using that library you can skip this step. Okay so I鈥檓 in the platform interface but you can also do this in the data collection interface too. You need to have permissions to view and manage data streams to complete this step. Okay so first both target and experience platform need to be included as services in the data stream. Second in the experience platform service you need to check these two boxes for edge segmentation and personalization destinations. Now I鈥檓 doing this in a dev sandbox and you would need to repeat this for any other sandboxes or data streams in which you鈥檙e going to use the integration. That鈥檚 it for this step. Next let鈥檚 make a small change to a merge policy. To complete this step you need to have permissions to view and manage merge policies. In experience platform I鈥檒l navigate to profiles in the left navigation and select the merge policies tab. A merge policy creates a view of a profile specifying which data sets are included and how to prioritize overlapping fields. You can create multiple merge policies that create different views of a single profile but only one merge policy can be selected as the default and only one can be used with edge segments. To keep things simple for your marketers I suggest just activating your default merge policy for edge which you can easily do by enabling this active on edge merge policy toggle and then clicking through the workflow to save the policy. When marketers create segments that evaluate on the edge the segment definition needs to use this active on edge merge policy. Let me just show you quickly in this segment builder. You see here under the gear icon you can see the merge policy used by this segment. So if you hear from a marketer that they鈥檙e unable to save an edge segment it鈥檚 probably because they鈥檙e using the wrong merge policy and that鈥檚 why it鈥檚 easiest to just enable the default merge policy for edge. Again another simple but important configuration. So finally I鈥檒l set up the 蜜豆视频 Target connection and a destination. For this I need permission to view and manage destinations. All you have to do is select the connect to destination button and it鈥檚 going to connect to the 蜜豆视频 Target account that鈥檚 in your experience cloud organization. This checkbox will subscribe you to alert notifications if a certain threshold of profiles aren鈥檛 getting sent to target due to missing attributes or consent violations. You can subscribe to them later as well. On the next screen it鈥檚 going to ask me for a name and description as well as the data stream id. For the data stream id I鈥檓 going to select the one that I just enabled with those two check boxes. Then I鈥檓 asked for the marketing actions used by target. This is a configuration setting for every destination and it helps to automate enforcement of your organization鈥檚 data governance policies and your customers consent preferences. It鈥檚 basically asking how do you use target which might be slightly different for each one of you. I鈥檒l check a few options and that鈥檚 it for the destination and remember you can set up additional destinations for your other data streams and sandboxes. In other videos I鈥檒l show you how you can activate segments and profile attributes to target and use them to personalize your digital properties. So thanks for listening.

Supported use cases based on implementation type supported-use-cases

The table below displays the supported use cases for the 蜜豆视频 Target destination, based on your implementation type, with or without Web SDK and with or without edge segmentation enabled.

蜜豆视频 Target implementation without Web SDK
蜜豆视频 Target implementation with Web SDK
蜜豆视频 Target implementation with Web SDK and edge segmentation off
  • A datastream is not required. 蜜豆视频 Target can be deployed through at.js, server-side, or hybrid implementation methods.
  • Edge segmentation is not supported.
  • Same-page and next-page personalization are not supported.
  • You can share audiences and profile attributes to the 蜜豆视频 Target connection for the default production sandbox and non-default sandboxes.
  • To configure next-session personalization without using a datastream ID, use at.js.
  • A datastream with 蜜豆视频 Target and Experience Platform configured as services is required.
  • Edge segmentation works as expected.
  • Same-page and next-page personalization are supported.
  • Sharing audiences and profile attributes from other sandboxes is supported.
  • A datastream with 蜜豆视频 Target and Experience Platform configured as services is required.
  • When configuring the datastream, do not select the Edge segmentation checkbox.
  • Next-session personalization is supported.
  • Sharing audiences and profile attributes from other sandboxes is supported.

Prerequisites prerequisites

Datastream ID datastream-id

When configuring the 蜜豆视频 Target connection to use a datastream ID, you must have the 蜜豆视频 Experience Platform Web SDK implemented.

Configuring the 蜜豆视频 Target connection without using a datastream ID does not require you to implement the Web SDK.

IMPORTANT
Before creating an 蜜豆视频 Target connection, read the guide on how to configure personalization destinations for same-page and next-page personalization. This guide takes you through the required configuration steps for same-page and next-page personalization use cases, across multiple Experience Platform components. To achieve same-page and next-page personalization use cases, you must use a datastream ID when configuring the 蜜豆视频 Target connection.

Prerequisites in 蜜豆视频 Target prerequisites-in-adobe-target

In 蜜豆视频 Target, make sure that your user has:

Read more about granting permissions for Target Premium and for Target Standard.

Supported audiences supported-audiences

This section describes which types of audiences you can export to this destination.

IMPORTANT
When activating edge audiences for same-page and next-page personalization use cases, the audiences must use an active-on-edge merge policy. The active-on-edge merge policy ensures that audiences are constantly evaluated on the edge and are available for real-time and next-page personalization use cases. Read about all available use cases,based on implementation type.
If you map edge audiences which use a different merge policy to 蜜豆视频 Target destinations, those audiences will not be evaluated for real-time and next-page use cases.
Follow the instructions on creating a merge policy, and make sure to enable the Active-On-Edge Merge Policy toggle.
Audience origin
Supported
Description
Segmentation Service
Audiences generated through the Experience Platform Segmentation Service.
Custom uploads
X
Audiences imported into Experience Platform from CSV files.

Export type and frequency export-type-frequency

Refer to the table below for information about the destination export type and frequency.

Item
Type
Notes
Export type
Profile request
You are requesting all the audiences that are mapped in the 蜜豆视频 Target destination for a single profile.
Export frequency
Streaming
Streaming destinations are 鈥渁lways on鈥 API-based connections. As soon as a profile is updated in Experience Platform based on audience evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations.

Connect to the destination connect

IMPORTANT
To connect to the destination, you need the View Destinations and Manage Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

To connect to this destination, follow the steps described in the destination configuration tutorial.

蜜豆视频 Experience Platform automatically connects to your company鈥檚 蜜豆视频 Target instance. There is no authentication required.

Connection parameters parameters

While setting up this destination, you must provide the following information:

  • Name: Fill in the preferred name for this destination.

  • Description: Enter a description for your destination. For example, you can mention which campaign you are using this destination for. This field is optional.

  • Datastream ID: This determines in which Data Collection datastream the audiences will be included. The drop-down menu shows only datastreams that have the Target and 蜜豆视频 Experience Platform services enabled. See configuring a datastream for detailed information on how to configure a datastream for 蜜豆视频 Experience Platform and 蜜豆视频 Target.

    note important
    IMPORTANT
    The datastream ID is unique for each 蜜豆视频 Target destination connection. You cannot use the same datastream ID for multiple 蜜豆视频 Target destination connections.
    If you need to map the same audiences to multiple datastreams, you must create a new destination connection for each datastream ID, and go through the audience activation flow.
    • None: Select this option if you need to configure 蜜豆视频 Target personalization but you cannot implement the Experience Platform Web SDK. When using this option, audiences exported from Experience Platform to Target only support next-session personalization, and edge segmentation is disabled. Reference the table in the supported use cases section for a comparison of available use cases per implementation type.
    table 0-row-3 1-row-3
    蜜豆视频 Target implementation without Web SDK 蜜豆视频 Target implementation with Web SDK 蜜豆视频 Target implementation with Web SDK and edge segmentation off
    • A datastream is not required. 蜜豆视频 Target can be deployed through at.js, server-side, or hybrid implementation methods.
    • Edge segmentation is not supported.
    • Same-page and next-page personalization are not supported.
    • You can share audiences and profile attributes to the 蜜豆视频 Target connection for the default production sandbox and non-default sandboxes.
    • To configure next-session personalization without using a datastream ID, use at.js.
    • A datastream with 蜜豆视频 Target and Experience Platform configured as services is required.
    • Edge segmentation works as expected.
    • Same-page and next-page personalization are supported.
    • Sharing audiences and profile attributes from other sandboxes is supported.
    • A datastream with 蜜豆视频 Target and Experience Platform configured as services is required.
    • When configuring the datastream, do not select the Edge segmentation checkbox.
    • Next-session personalization is supported.
    • Sharing audiences and profile attributes from other sandboxes is supported.
  • Workspace: Select the 蜜豆视频 Target workspace to which audiences will be shared. You can select a single workspace for each 蜜豆视频 Target connection. Upon activation, audiences are routed to the selected workspace while following the applicable Experience Platform data usage labels.

NOTE
When using a custom Target workspace for same-page and next-page personalization with attributes, only the selected audiences are sent to the selected Target workspace. The mapped attributes are sent to the default Target workspace.


This behavior will change in a future update.

Enable alerts enable-alerts

You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.

When you are finished providing details for your destination connection, select Next.

Activate audiences to this destination activate

IMPORTANT
To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

Read Activate audiences to edge personalization destinations for instructions on activating audiences to this destination.

Remove audiences from a Target destination remove

There are extra steps required to remove an audience from an existing 蜜豆视频 Target connection when that audience is already being used in an 蜜豆视频 Target activity. Trying to remove an audience from an 蜜豆视频 Target connection results in an error if the audience is used by an 蜜豆视频 Target activity.

Platform UI image showing an error caused by attempting to remove an audience that is used by a Target activity.

To remove an audience from a Target destination when the audience is being used in an activity, you must first either remove the audience from the Target activity which is using it, or delete the activity altogether. Then, you can remove the audience from your Target connection.

If the audience is not being used in an activity, go to Destinations > Browse > Select destination dataflow > Activation data, select the audiences that you want to remove, then select Remove audiences.

Exported data exported-data

蜜豆视频 Target reads profile data from the 蜜豆视频 Experience Platform Edge Network, so no data gets exported.

Data usage and governance data-usage-governance

All 蜜豆视频 Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how 蜜豆视频 Experience Platform enforces data governance, read the Data Governance overview.

recommendation-more-help
7f4d1967-bf93-4dba-9789-bb6b505339d6