51黑料不打烊

Configure file-based cloud storage or email marketing destinations

Get tips during a walkthrough of the configuration of a file-based destination in 51黑料不打烊鈥檚 Real-Time Customer Data Platform (CDP). This applies to cloud storage destinations (E.g. S3 or SFTP) and also email marketing destinations. For more detailed product documentation, see:

Transcript
Hi, this is Michelle. Let鈥檚 explore the key configuration settings for file-based audiences to cloud storage or email marketing destinations. In Experience Platform, I navigated to the Destinations catalog. This video pertains to the cloud storage and email marketing categories because they are based on files that are sent out to those locations or those partners. We鈥檙e starting with the workflow after the admin sets up the credentials for the connection. If you鈥檙e a marketer or business practitioner, this is for you because it covers the day-to-day need for sending audience data to these destinations. You鈥檒l know an audience is ready to share to a destination by the call to action in the destination tile. Activate means you can proceed with sending audiences, whereas setup means your admin needs to establish valid connection credentials first. I鈥檓 in an active connection for an S3 destination. The first thing you鈥檒l do is select the audiences you want to send. Really, these are profiles you want to go out to the destination partners. The destination will already have been named, and it might be based on the kind of data being sent or on the kind of storage bucket being used. You can see that we have multiple audiences to choose from, so I鈥檒l select a couple of them now. Once I鈥檓 done, I鈥檒l choose Next at the top. There鈥檚 two main things to configure on this screen. One is to set the schedule of how often you want this data to go out, and the other is to adjust the file name, if needed. Let鈥檚 start with the scheduling. This is done per audience, so I鈥檒l jump into the first one. There鈥檚 two options at the top. You can export full files or incremental files. If you want full files for every export, you have several frequency options. Once, daily, weekly, or monthly. If you鈥檙e not sure what the data will look like when it lands, select once, and then when it鈥檚 structured as expected, come back to update this frequency as desired. You can run the job after segment evaluation, which ensures the activation job runs immediately after the daily batch segmentation job completes. Otherwise, you can select the time of day you want the file to go out. Notice this is in UTC time, so keep that in mind. Then you can set up the start and end dates here. Let鈥檚 review the options available for exporting incremental files next. I have fewer frequency options available compared to full files, which are daily and hourly. Let鈥檚 say there are emails I want to send out more than once per day based on people qualifying for this audience. In that case, I鈥檇 select hourly. If I鈥檓 sending files for use in other systems that only need a single day鈥檚 worth of data, then daily is fine. Keep in mind that the incremental setting will generate the first file with all profiles that qualify for the audience up until the time of activation, and then subsequent files will be the deltas of the profiles that qualify for that audience moving forward. This time is fine, but I鈥檒l adjust the date range. Now that I鈥檓 done, I鈥檒l select create. I鈥檒l set up the second audience with the default export configurations for export option, frequency, and time, and I鈥檒l update the date to a single day before selecting create. Next up, let鈥檚 explore the file name options. The default file name includes the destination name, the audience ID, which is a numeric value, and the current timestamp. There鈥檚 a file name preview at the top. I鈥檓 not limited to the defaults, though. Perhaps I don鈥檛 want to add the timestamp, and I鈥檇 like to add the audience name. Doing this may be more helpful on the other end for identifying what data is in a certain file, or destination partners might look for a specific file name, but also want to distinguish the date of the data. In that case, I鈥檒l add back the timestamp details. I鈥檓 done with my changes on this step, so we鈥檒l move forward. On the mapping step, we鈥檒l see recommended attributes to help you get started with your selection. The attributes selected here will be sent out in files to the destination partner. We don鈥檛 have to keep all of these, though. I鈥檒l remove the last two attributes by clicking delete mapping to the right of each. Now let鈥檚 discuss the mandatory and the duplication key settings. I鈥檒l use an example of exporting this data to an email partner. In this case, I鈥檒l need the email address. There鈥檚 no real use of sending a profile if it doesn鈥檛 have an email address, so I鈥檒l use mandatory. This means the email value must be present in the profile for it to be included in the file. I鈥檇 like to keep the first and last name, but I鈥檓 not going to require them. Deduplication ensures you don鈥檛 have multiple instances of the same profile in the exported file. I鈥檒l add a new field to demonstrate. I鈥檒l add the mobile phone number field, and I鈥檒l make this new field mandatory as well, but I also want to use it as the deduplication key. This field will deduplicate profiles based on the mobile phone number. I鈥檓 happy with the mapping settings, so I鈥檒l select next at the top. This is a review of what will be sent to the destination partner. You鈥檒l also see the marketing actions set up for this destination. In this case, the data will be used for onsite advertising. Once everything looks good, select finish to start the audience export process. Thank you for watching this walkthrough for sending data to file-based destinations.
recommendation-more-help
9051d869-e959-46c8-8c52-f0759cee3763