Merkury Enterprise Connections Destination
- Onderwerpen:
- Destinations
Gemaakt voor:
- Beheerder
- Gebruiker
Overview
Use the Merkury Enterprise Connections destination to securely deliver audiences to Merkury. Merkury provides marketers easy matching and delivery of person-based audiences to Merkury’s 80+ premium addressable TV/CTV, publisher, and ad-tech connections. Merkury is powered by a comprehensive US adult consumer identity graph of 268+ million people.
Follow the steps in this documentation page to create a Merkury Connections destination connection and activate audiences using the Adobe Experience Platform user interface.
Use Cases
- Digital Media Activation: Easy matching and delivery of your audience profiles to Merkury’s 50+ premium addressable publishers and ad-tech connections.
- Improve Efficiencies: Enhance your cookie-less, addressable media reach, improve targeting efficiencies and Return on Advertising Spend (ROAS).
Prerequisites
- To connect to the destination, you need the View Destinations and Manage 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.
- To export identities, you need the View Identity Graph [access control permission].!Select identity namespace highlighted in the workflow to activate audiences to destinations.
Supported identities
Supported audiences
This section describes which type of audiences you can export to this destination.
Export type and frequency
Refer to the table below for information about the destination export type and frequency.
Connect to the destination
To connect to this destination, follow the steps described in the [destination configuration tutorial]. In the destination configuration workflow, fill in the fields listed in the two sections below.
Authenticate to destination
To authenticate to the destination, fill in the required fields and select Connect to destination.
To access your bucket on Experience Platform, you need to provide valid values for the following credentials:
Fill in destination details
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
- Name (Required) - The name the destination will be saved under
- Description - Short explanation of the destination’s purpose
- Bucket Name (Required) - Name of the Amazon S3 bucket set up on S3
- Folder Path (Required) - If subdirectories in a bucket are used a path must be defined, or ‘/’ to reference the root path.
- File Type - Select the format Experience Platform should use for the exported files. Consult your Merkury team for the expected file type for your account.
Existing Account
Accounts already defined using the Merkury Enterprise Connections destination appear in a list pop-up. When selected, you can see details on the account in the right rail. View the example from the UI, when you navigate to Destinations > Accounts:
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
- 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.
- To export identities, you need the View Identity Graph access control permission.
Read Activate audience data to batch profile export destinations for instructions on activating audiences to this destination.
Mapping suggestions
The correct processing of files on the Merkury side requires name and address elements. While not all elements are required, providing as much as possible will aid in successful matching.
Mapping suggestions are provided in the table below listing attributes on your destination side that are used by Merkury processing that customers can map profile attributes to. Treat these elements as suggestions as not all elements are required, and the source values will depend on the needs of the account.
person.name.firstName
value in Experience Platform.person.name.lastName
value in Experience Platform.mailingAddress.street
value in Experience Platform.mailingAddress.city
value in Experience Platform.mailingAddress.state
value in Experience Platform. Use if the state is in the two character code form.mailingAddress.state
value in Experience Platform. Use if the state is the full state namemailingAddress.postalCode
value in Experience Platform.Validate data export
To verify if data has been exported successfully, check your Amazon S3 Storage bucket, and make sure that the exported files contain the expected profile populations.
Data usage and governance
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, read the Data Governance overview.
Next steps
By following this tutorial, you have successfully created a dataflow to export profile data from Experience Platform to your Merkury managed S3 location. Next, you need to contact your Merkury representative with the name of the account, file names, and the bucket path so that processing can set up.