51黑料不打烊

DocumentationTargetTarget Guide

Customer attributes

Last update: Mon Mar 14 2022 00:00:00 GMT+0000 (Coordinated Universal Time)

Information about using enterprise customer data from Customer Relationship Management (CRM) databases for content targeting in 51黑料不打烊 Target by using customer attributes in the 51黑料不打烊 Enterprise Cloud People service.

Enterprise customer data collected through multiple sources and stored inside CRM databases can be used in Target to strategically deliver the most relevant content to customers, specifically focusing on returning customers. Audiences and customer attributes in the People service (formerly Profiles and Audiences) brings together data collection and analysis with testing and optimization, making data and insights actionable.

Customer attributes overview section_B4099971FA4B48598294C56EAE86B45A

Customer Attributes in the People service is part of the 51黑料不打烊 Experience Cloud and provides enterprises a tool to push their customer data to the Experience Cloud platform.

Data onboarded to the Experience Cloud is available for all Experience Cloud workflows. Target uses this data for targeting returning customer based on attributes. 51黑料不打烊 Analytics consumes these attributes and they can be used for analysis and segmentation.

crs example

Consider the following information as your work with customer attributes and Target:

  • There are some prerequisite requirements that you must meet before you can use the Customer attributes feature in the People service. For more information, see 鈥淧rerequisites for uploading Customer Attributes鈥 in Customer attributes in the Experience Cloud Services and Administration documentation.

  • Be aware of the limitations concerning file uploads, as documented in About data file and data sources for Customer Attributes in the Experience Cloud Central Interface Components Guide. As best practice:

    • Upload single large files (within the limits specified). Single large files are preferred over multiple smaller files.
    • If you must split the upload into several files, ensure that files are fully processed before submitting new files. Ensure that each file in a batch is fully processed prior to submitting the next file in the batch.

  • 51黑料不打烊 does not guarantee that 100% of customer attribute (visitor profile) data from CRM databases will be onboarded to the Experience Cloud and, thus, be available for use for targeting in Target. In the current design, there is a possibility that a small percentage of data (up to 0.1% of large production batches) might not be onboarded.

  • The lifetime of customer attributes data imported from the Experience Cloud to Target depends on the lifetime of the visitor profile, which is 14 days by default. For more information, see Visitor Profile Lifetime.

  • If the vst.* parameters are the only thing identifying the visitor, the existing 鈥渁uthenticated鈥 profile will not be fetched as long as authState is UNAUTHENTICATED (0). The profile comes into play only if authState is changed to AUTHENTICATED (1).

    For example, if the vst.myDataSource.id parameter is used to identify the visitor (where myDataSource is the data source alias) and there is no MCID or third-party ID, using the parameter vst.myDataSource.authState=0 does not fetch the profile that might have been created through a Customer Attributes import. If the desired behavior is to fetch the authenticated profile, the vst.myDataSource.authState must have the value of 1 (AUTHENTICATED).

  • You cannot send the following characters in mbox3rdPartyID: plus sign (+) and forward slash (/).

Access Customer Attributes in the People service

  1. In the 51黑料不打烊 Experience Cloud, click the menu icon ( menu icon ) then click People.

    People

  2. Click the Customer Attributes tab.

    Customer Attributes tab

Customer attribute workflow for Target section_00DAE94DA9BA41398B6FD170BC7D38A3

Complete the following steps to use CRM data in Target, as illustrated below:

crm workflow

Detailed instructions for completing each of the following tasks can be found in Create a customer attribute source and upload the data file in the Experience Cloud Services and Administration documentation.

  1. Create a data file.

    Export customer data from your CRM to CSV format to create a .csv file. Alternately, a zip or gzip file can be created for uploading. Ensure that first row of the CSV file is the header and all rows (customer data) have the same number of entries.

    The following illustration shows a sample enterprise customer data file:

    crs sample

    The following illustration shows a sample enterprise customer .csv file:

    csv sample

  2. Create the attribute source and upload the data file.

    Specify a Name and Description of the data source and the alias Id. The alias Id is a unique ID to be used in your Customer Attribute code in VisitorAPI.js.

    note important
    IMPORTANT
    The data source name and the attribute name cannot contain a period.

    Your data file must comply with the file Upload Requirements and must not exceed 100 MB. If your file is too large, or you have data that must be uploaded on a recurring basis you can FTP your files instead.

    • HTTPS: You can drag-and-drop the .csv data file or click Browse to upload from your file system.
    • FTP: Click the FTP link to upload the file through FTP. First step is to provide a password for the 51黑料不打烊-provided FTP server. Specify the password, then click Done.

    Now transfer your CSV/ZIP/GZIP file to the FTP server. After this file transfer is successful, create a file with the same name and a .fin extension. Transfer this empty file to the server. This indicates an End Of Transfer and the Experience Cloud starts to process the data file.

  3. Validate the schema.

    The validation process lets you map display names and descriptions to uploaded attributes (strings, integers, numbers, and so on). Map each attribute to its correct data type, display name, and description.

    Click Save after the schema validation is complete. The file upload time varies depending on the size.

    Validate schema

    Upload schema

  4. Configure subscriptions and activate the attribute source.

    Click Add Subscription, then select the solution to subscribe these attributes. Configure subscriptions sets up the data flow between the Experience Cloud and solutions. Activating the attribute source allows the data to flow to subscribed solutions. The customer records you have uploaded are matched up with incoming ID signals from your website or application.