ÃÛ¶¹ÊÓƵ

Transcript

In this video, I’ll show you how to use templates to auto-generate assets needed for ingesting Marketo-engaged data into Experience Platform. These are the areas I’ll cover. Use the blue chapter markers below the video to advance to or replay these sections over again. Data ingestion is a fundamental step to getting data into Experience Platform, so you can use it to build robust customer profiles and use them to provide meaningful experiences. ÃÛ¶¹ÊÓƵ Experience Platform allows you to ingest data from external sources. These data can be structured, labeled, and enhanced using platform services. The focus of this video is ingesting data from Marketo, which is ÃÛ¶¹ÊÓƵ’s marketing automation and lead generation solution, using a source connector in Experience Platform. Prior to using this connector, complete the authentication and organization mapping steps in Marketo. Refer to the documentation links included below this video for more details. I’ll demonstrate using the templates workflow in the connector, which auto-generates the assets listed on this slide. Using the templates workflow compared to the standard workflow provides the benefits shown here. The standard workflow requires upfront work that can be time-consuming, namely setting up B2B namespaces and schemas, which are done through API calls. The template workflow, on the other hand, does this for you, so you save a lot of time. It’s also flexible in that you can customize the assets after they’re generated. Okay, time for the demo. I’m logged into Experience Platform. I’ll display sources by selecting the navigation link from the left. Now I’ll select the ÃÛ¶¹ÊÓƵ Applications category to jump to those connectors. Selecting Add Data under Marketo Engage will kick off the workflow. There are two workflows available here. I can use templates, which accelerates data ingestion, since it auto-generates all the assets needed. Or, if I’d already set up the identity namespaces and schemas for the data I want to ingest, I’d use the second workflow. I’ll proceed with using templates. My organization has an existing authenticated Marketo account. If this is a first-time setup, start with New Account. Here you provide the authentication credentials for your account. The fields with an asterisk are required. You’d then choose Connect to Source. Just a reminder, refer to the documentation links included below this video for more details. I’ll go back to my existing account to show you the remaining workflow. Once I select the account name, I’m presented with a list of templates I can choose to generate the assets needed. There’s an option for both B2B and B2C business types. This account is B2B. Some templates for this account have already been configured. The check boxes for these data tables are grayed out. This means the assets associated with them have been generated in the system already. I’m going to choose additional templates for other Marketo data tables I want to ingest. I’ll select Program Memberships and Programs. Now I’ll select Finish, and this is when the magic happens. The system is doing all the work to generate the assets needed for this data ingestion. This usually takes a minute or so to finish, so be patient. Once the process finishes, the Review Template Assets page displays. A status is shown at the bottom as well. This page lists the data flows, datasets, schemas, and identity namespaces created or reused for the data tables selected in the previous step. The status for some of the assets may be set to Reused if they were created as a result of a previous template workflow. This is the case for all the schemas and identity namespaces. Other assets are net new because they’re unique. Earlier I spoke about the benefits of using the templates workflow. I’ll open one of the generated schemas in a new browser tab. Again, the schema was generated by the system. You can see the breadth and depth of the hierarchies used here for the different fields. Plus, this is only one of the many schemas generated. That’s an impressive time saver. Back in the Review Templates Assets screen, let’s take another look at the identity namespaces. These have all been generated by the system. This would have to be manually done using the other workflow, including the relationships of these identities across the schemas. The datasets are newly generated because they’re unique to the data table templates selected earlier. Just a quick high-level callout, the datasets contain the data, whereas the schemas validate the format of the data to ensure you’re ingesting quality data into Experience Platform. The data flows are newly generated too. Not only that, but these are set to draft status. This is because you’ll want to review and confirm the mappings between Marketo and Experience Platform before enabling them to accept data. I’ll show you preview mappings first from the 3Picker menu. This opens a modal and shows you the field mappings between Marketo and Experience Platform. You can review this here, but you can’t make changes in this modal. Now I’ll choose Update Dataflow from the 3Picker. This takes you through a workflow where you can make some changes, including enabling the data flow to start ingestion. Once the data flow opens, I’ll select Next in the upper right corner. The setting to enable partial ingestion lets you configure an error threshold percentage for a batch. If errors exceed this threshold, the batch fails. Toward the bottom, you can configure alerts. Alerts allow you to receive notifications on the status of your source’s data flow. You can get updates when your data flow has started, is successful, has failed, or didn’t ingest any data. If you want to save these changes and come back to finish the mapping validation, select Save as Draft here. Otherwise, select Next. The mapping step is where you can confirm or change mappings between the source fields from Marketo and the target fields in Experience Platform. At the top, it provides a high level status for the number of mapped fields, required fields, and identity fields, and whether it found any errors. Below that is the detail for the mappings. On the right side are the fields for the Experience Platform schema, and on the left are the fields from Marketo. Calculated fields are also automatically generated by the system, which is super helpful. Once I select Next, the mapping validation happens. If there’s an issue, you’d see it in the next step. Otherwise, you’re taken to the review step. Now that everything looks good, I’ll select Save and Ingest. Once this is done, I’m redirected back to the Marketo account for the data connector. From there, I see the data flow I just reviewed and saved, updated to enabled status. You would go through the same process for the other data flows that aren’t enabled. Now that the data flow is enabled, an initial bootstrap job begins to ingest historical data from Marketo into Platform. Once this is complete, incremental records are ingested through streaming. Because of this, there’s no scheduling option for this type of data flow. You should now feel comfortable configuring data flows using templates from the Marketo Engage data connector workflow in Experience Platform. Thanks and good luck!

Transcript

Hi, I’m Margaret Trinh, Senior Product Manager here today to share with you more about the Source Data Connector for Marketo and Gage. In this video, we’ll discuss how to set up the Marketo Connector, how to work with custom attributes and custom objects, and to understand the data flow between Marketo and Experience Platform. Before watching this video, we will assume that you’ve already created the B2B namespaces and schemas in your instance, and if you’re using any custom attributes, the schemas have been modified to include those. First, setting up the Marketo Connector. We will go through these steps in detail once we reach the demo. RT-CDP customers will have the Marketo Connector visible in their Sources catalog. Before the setup, you’ll need to have a user setup within Marketo dedicated to the data ingestion. There will also be a required mapping between your IMS organization and your Marketo subscriptions. Do keep in mind that you are allowed to map multiple Marketo subscriptions to a single IMS organization. Once these are configured, you can begin creating your flows for data ingestion. The Marketo Connector utilizes ÃÛ¶¹ÊÓƵ’s Business XDMs to map data from Marketo into ÃÛ¶¹ÊÓƵ Experience Platform. In addition, the Connector will present users with a pre-mapped template so that standard attributes from Marketo are automatically mapped to the target schema. Please make sure to review these mappings and ensure that custom attributes are also mapped. To add custom attributes from Marketo, you can leverage custom field groups and add them to your schema. After you’ve configured your data flow from Marketo, we will initiate a bootstrap job to begin ingesting all historical data from Marketo into Experience Platform. The time will vary depending on the size of your subscription. Once a historical backfill is complete, we will switch over to ingest data via streaming that will put incremental records in near real-time. Because of this, users will not see a scheduling step when setting up the data flow. If you have a CRM synced to your Marketo subscription such as Salesforce or Microsoft Dynamics, the Postman utility will also create namespaces and schemas for these platforms. These namespaces will help distinguish the identities coming from each platform, so that the Unified Identity Service can stitch and merge similar records together. Now that you have a solid understanding, let’s see all of this in action. Before we dive in to setting up the MarketoEngage Source Connector, it’s assumed that you’ve already utilized Automated Utility to create the B2B namespaces and schemas. In addition, if you’re ingesting any custom attributes that you have not yet defined in the classes or field groups, you’ve also built your schema to include those custom attributes. Now, to get started on setting up the connector, there are a couple steps that will be handled within MarketoEngage. But before we head over there, let’s first take note of our organization ID, which we’ll use to map to our Marketo subscription. You can find your IMS organization ID by going to the Experience Cloud homepage and scrolling to the very bottom. At the bottom right, you’ll find your organization ID listed here. You can take note of this. Now, over to MarketoEngage. As an admin, you’ll first navigate over to the admin page and click on the Users and Roles page. Let’s first start off by creating a new role for an API user. This user will access the Marketo API to pull data from Marketo into ÃÛ¶¹ÊÓƵ Experience platform. So let’s give it a role name with a description of and give it the permission to access API and click Create. Now, to create the user, you’ll navigate to the Users tab and invite a new user. Note that there will not be an actual email sent to this user, so it does not need to be a real email address. For this dedicated user, we’ll set the email to… After I click Next, I’ll select the AEP API user role that I just created from the previous step. And be sure that this is an API user only by checking the checkbox. Once I click Next, I can go ahead and hit Send to save the new user. Lastly, I’m going to create a custom service that will provide the authentication token to speak between the two services. From the Launch Point tab, create a new service. First we’ll select a name for the service. And this is going to be custom. Then we’ll add a brief but useful description. Then select the user that we just created from the earlier step. Go ahead and click Create. And to show you how to retrieve the client ID and client secret that you’ll need for the next step, you’ll need to open the new service that you just created by clicking View Details to get those values. Keep this open so that you can copy and paste it into AEP shortly. Now the last step in Marketo is to use the IMS organization ID that we copied from ÃÛ¶¹ÊÓƵ Experience Cloud earlier. Let’s do that again. From the homepage of Experience Cloud, scroll to the very bottom. At the bottom right, you’ll find the org ID located here. Take everything except for the at ÃÛ¶¹ÊÓƵ org suffix at the end. Please be aware that you’ll need to be an admin for your ÃÛ¶¹ÊÓƵ organization in order to complete the mapping. Now go to ÃÛ¶¹ÊÓƵ Organization Mapping and click Edit to enter your org ID. Click OK, then confirm. And you may be prompted to log back in to ÃÛ¶¹ÊÓƵ Experience Cloud to finalize the mapping. Now let’s go back to the custom service that you created so that we can grab the client ID and client secret. I’ll first grab the client ID. From here, let’s go back and launch Experience Platform, then head to the Sources menu. Along with other ÃÛ¶¹ÊÓƵ applications, you’ll see the Marketo engaged connector located here. If you haven’t authenticated before, you’ll select the Configure button. Otherwise you may see the text Add Data, in which case you can select an account that has already been connected. If you haven’t authenticated, you’ll land on the option to set up a new account. We’ll enter some details for our new connection and from the custom service that we just created, we’ll grab the client ID and client secret and paste it here. To find your Munchkin ID, navigate back to Marketo to the My Account tab. Copy the Munchkin ID from the bottom. Now you can go ahead and click Connect to Source to move on to the next step. You’ll now be presented with the 10 datasets that can be imported from Marketo Engage. For this demo, we’ll ingest accounts, or rather companies from the Marketo API. By clicking the dataset, you should expect to see a preview of the data on the right-hand side. After you click Next, you’ll set up a name related to accounts for your dataset. Then go ahead and select the schema related to accounts once again that was auto-generated from the utility. If you created a custom schema to include custom field groups and attributes, make sure that you select that one instead. After selecting the schema, the mapping from the Marketo source dataset and the AEP target dataset will appear. For most standard attributes, Marketo has included predefined mappings that can be modified to your preference. For any custom attributes, you’ll want to make sure that you revisit those to make sure that the mappings are correct. Lastly, make sure to enable the dataset profile. Then click Next. The final step here is to name the data flow to make it identifiable to reference later on. In this case, it’s already been auto-populated to include the name of the entity. We would also suggest keeping error diagnostics enabled so that you can find any issues with data ingestion. Also, enable the partial data ingestion, keeping the default threshold at 5%, meaning that batches with less than 5% of errors will be considered successful, although you’ll still be able to retrieve the error logs. Now after you click Next, you’ll be presented with a quick review of your setup for the specific dataset, and the ingestion will begin once you click Save & Ingest. You’ll notice that unlike other connectors, there’s no scheduling step. That’s because Marketo’s data ingestion automatically runs multiple batches to ingest all of your historical data. And once that’s complete, Marketo will automatically switch over to stream any new records or updated records by scanning for anything that’s been modified. You’ll want to make sure that you repeat these steps for all additional datasets that you’ll need for your B2B use cases. And that wraps it up for knowing how to use the Marketo Engage Source Data Connector. So in summary, within this video, we have successfully set up the data flows using the Marketo Source Connector, understood how to handle custom attributes, and learned how data ingestion works between Marketo and Experience Platform. Thank you for watching.