Connect Tableau to Query Service

Learn how to connect to Query Service from a variety of desktop client applications that supports PostgreSQL protocol and how to use PostgreSQL tools and drivers to connect and write queries. For more information, please visit the Query Service documentation.

Hi there. Adobe Experience Platform ingests data from a wide variety of sources. A major challenge for marketers is making sense of this data, to gain insights about their customers. Adobe Experience Platform Query Service facilitates that, by allowing you to use standard SQL to query data in-platform. Data ingested into platform can be cleaned and prepared, to generate valuable customer insights, using platform Query Service capabilities. Generated insights get stored in-platform. Adobe Experience Platform allows third-party applications, that use PostgreSQL protocol, to connect to Query Service. This integration helps marketers create a view, and a visual representation of customer data, in their favorite business intelligence tool, and make valuable decisions. For this video, I will be using the Tableau desktop application, to demonstrate the capability. From your Experience Platform Homepage, navigate to Data Sets, under Data Management. For this video, we’re using a fictional retail brand, called Luma. Luma loyalty dataset contains information about customers’ loyalty details, geography details, etc. Luma web data contains web-traffic information about customers’ interaction on the Luma site, including products viewed by a customer, visited pages, products purchased, etc. Let’s take a use-case, where a marketer needs to create a report of what orders placed by a loyalty customer, and it should include customer details and product details. So, clearly, we need to get information from two different datasets, Luma loyalty data, and Luma web data, to create this report. A data-engineer can query the datasets, combine them, extract the necessary information, and store it as a dataset, in-platform. In our case, it’s the Order Summary Table. Let’s quickly check the Order Summary dataset, to verify the data stored in it. The Order Summary Table contains information about users, personal details, such as name, contact, and geographical details. It also contains information about products purchased and the price of each item. The marketer can now access the Order Summary dataset from a BI tool of his or her choice, that supports PostgreSQL protocol to connect to Query Service, to make valuable decisions. From Experienced Platform Homepage, let’s navigate to Queries. Click on the Credentials Tab, and make a note of the Postgres credentials. Make a note of the credentials’ expiry date and time. Let’s switch to a BI tool that supports a PostgreSQL protocol. I’m using Tableau for this video. Let’s set up a connection to the PostgreSQL server. Enter the credentials noted from the previous step onto the sign-in screen, and let’s proceed. Knowing that the Postgres credentials contain an expiry date and time, so to re-initiate the connection, you need to provide the password generated by platform, from the Credentials Tab. You have now connected with Adobe Experience Platform, with a list of your tables displayed on the side. Double-click on the Order Summary table, to load data. Let’s create a new worksheet, to create a graphical representation of the Order Summary table. Take a note of the table fields displayed under the data-pane. Imagine a scenario where a marketer needs to plot Order Summary details on a map-view, and identify the total revenue from each city. To do that, let’s drag-drop the longitude field onto columns, and set it as a dimension. Similarly, let’s add the latitude field onto rows, and set it as a dimension. For better visualization, and easy analysis, let’s choose the map-view. Based on the longitude and latitude details, each Order Summary record gets plotted on a map-view. Now, let’s add the Total Price Measure to the Marks Card. The data-point on the map updates, to show the amount of sales, for each city. If you would like to filter the sales-data to a specific state, let’s add the state field to Filters, and add a value for the state field. You can interact with the map, and each data point contains information about the total revenue. Based on the data, a marketer can now make a valuable decision. For example, based on the total revenue from a location, the Luma brand can now gain insights about where to open their next in-store location. Adobe Experience Platform allows third-party applications that use PostgreSQL protocol to connect to Query Service. This integration helps marketers create and weave a visual representation of customer data, in their favorite BI tool, and make valuable decisions. -