Integrate Adobe Analytics with Conductor

You can download a PDF of this guide to share with stakeholders by clicking here.

This guide walks you through the process to integrate Conductor with Adobe Analytics. This integration helps you connect-the-dots to see how your natural search efforts correlate to your critical traffic, your conversions, and your revenue.

Integrating Conductor with Adobe Analytics helps you to:

• Optimize your SEO campaigns by combining in-session metrics.
• View campaign effectiveness and on-site behavior.
• View key organic metrics, paid metrics, and SERP data, side-by-side.
• See the impact of your SEO efforts.
• Prioritize SEO initiatives based on real attribution.

Your Adobe Analytics administrator will need to perform some of this set up. You can send them this integration guide to complete the configuration.

Technical Information

Before beginning this integration, review the following information and prerequisites for your Adobe Analytics and Conductor instances.

Adobe Prerequisites

To implement this integration, you must have the following:

• Adobe Analytics
• Adobe Data Warehouse

Please note the following before you begin:

Because much of this configuration occurs in your organization's Adobe Data Warehouse instance, your team is responsible for creating these .csv files and for ensuring they are sent to Conductor at the specified weekly and monthly times.

Information Security

Conductor does not collect personally identifiable information (PII) through the Adobe Analytics integration. You can learn more about Conductor’s information security practices in this article.

Process

This integration uses .csv files you configure Adobe Data Warehouse to send automatically to a SFTP server. After completing these instructions, you will have the following two (2) reports created for the integration, from which Conductor generates all of its content reports:

• One (1) page-level report sent weekly.
• One (1) page-level report sent monthly.

Once configured, Adobe Data Warehouse will automatically send these two files at regular intervals for Conductor to receive and create reports in the Conductor platform.

Integration strategy

Depending on the way your organization reports on your web analytics with your Adobe instance, you might have to carefully plan how and why you choose to configure your integration or integrations.

For example,  because of the way the Conductor platform reports data, each of these integrations must be configured for a single domain–search engine combination. If you have multiple domains in a Report Suite or multiple report suites to integrate, you’ll need to carefully consider how to integrate those domains.

If your organization needs to create many integrations with Conductor to accommodate your organization's integration strategy, contact Conductor Customer Support before beginning. We'll want to work together to confirm the best way to accommodate your setup. 

How to set it up

Get your Alias and Username and Create the Integration in Conductor Intelligence

To create an integration, you'll need two required, unique identifiers from Conductor. Note that these integrations cannot be configured without these identifiers, and that Conductor must generate them for you.

Alias

The Alias is simply a unique identifier Conductor will generate specifically for your organization to use for configuring a new integration. Note that if you plan on creating multiple integrations, you may need multiple Aliases for each integration you plan to configure, depending on your Adobe configuration.

Username

The Username is a unique username to you when configuring the SFTP integration. Your organization needs only one Username. You can use it for any integrations you need to configure.

To get your Alias (or Aliases) and your Username:

1. Click here ↗️ or follow the path Settings > Web Analytics in Conductor. 
2. Click Add a New Integration.
3. From the form, select Adobe Analytics.
   
4. Click Generate your Alias and Username. The new integration configuration form appears, and your Alias and Username appear at the top. Tip: copy your Alias and Username to a text editor file or keep this window open in your browser when you move onto your Adobe configuration described below.
5. Complete the following fields in the integration configuration screen:
   
   1. Add an Integration Display Name.
   2. Choose one or more Related Search Engines to associate your data with.
   3. Click Save and Complete.

Configure Your First Request in Data Warehouse (Weekly Report)

Now you're ready to create your new integration in Data Warehouse. Again, you'll perform these steps for each Adobe Report Suite you plan on integrating.

You'll create two new requests, which will become the reports you send to Conductor. First, you'll build the weekly page-level report, and then duplicate and modify it to create the monthly report. Then, you’ll repeat this process for any remaining Report Suite Integrations.

1. In Adobe Analytics, follow the path Tools >  Data Warehouse.
   
2. In the upper-left, select and verify the Adobe Report Suite you want to use for this integration. Remember, if you have multiple Report Suites to integrate, you’ll need to repeat this process for each.
   
3. Click Add to create the new request.
   
4. Go to the General settings tab.
5. Complete the General settings tab as follows:
   • Request Name
     This can be anything, but you'll want to make the request identifiable. Consider using a name like "Conductor Weekly Report". However, if you are creating multiple requests for each Report Suite you are migrating, you'll want to make each request identifiable. Consider using a name like "Conductor Weekly Report – [Alias for integration]". This allows you to have an identifier unique to your integration for each request to distinguish your requests for one integration from another.
   • Date Ranges and Granularity
     
     • If you report your weeks on a Sunday through Saturday cadence, select the Last Week option from the Date Ranges menu and from the Granularity menu, select Weekly.
     • If you report your weeks on a Monday through Sunday cadence, select the Last Week option from the Date Ranges menu and from the Granularity menu, select None.
       
6. Go to the Build your report tab and select the following segments, metrics, and dimensions as follows:
   • Segments
     If you want to segment the data sent to Conductor, you can choose a segment here.
   • Metrics
     From the Metrics menu, select the following metrics, in order:
     • Visits - All Visitors
     • Page Views
     • Visits
   • Metrics, continued
     Select any other metrics that you want to integrate into Conductor. In total, you can select up to 10 metrics to integrate into Conductor. These can be selected in any order.
   • Dimensions
     Select the following reporting dimensions, in order:
     • Either Page URL or Visit Start Page URL:
       
       • Choosing Page URL means you'll be reporting on pages rolled up to their base URL—any URLs with query parameters, fragments (URLs with hashes), etc. are aggregated and reported on as one page. For most organizations, this is preferable because it simplifies their reporting to only one page. However, choosing Page URL means that when Conductor reports SERP data to the page—such as the keywords that rank for the page—it will do so only for the keywords that rank for the base URL. If other iterations of the URL happen to rank in search, that SERP data will not be included with the SERP data associated with the base URL.
       • Choosing Visit Start Page URL means you'll be reporting on each iteration of a URL—URLs with query parameters, fragments (URLs with hashes), etc. will each receive its own row. Because this means reporting on a give page is disaggregated, most organizations do not choose this option. However, unlike the Page URL option, all iterations of the base URL with query parameters, fragments, etc. that rank in search will have SERP data associated with them in Conductor. If your site drives significant traffic to parameterized pages through organic search, you might consider this option to take advantage of this SERP data in Conductor.
     • Visit Start Page
       This item is optional—most Conductor customers do not choose to break down their data by Visit Start Page, and Conductor does not recommend this for your integration. Choose this option only if your organization wants to breakdown your data by Visit Start Page. If you choose not to breakdown by Visit Start Page, do not select this option.
       Note that if you do choose this option it must be chosen in this order.
       
     • Last Touch Channel
       
       
7. Go to the Report destination tab.
   1. Click Add account.
      
   2. From the Account type menu, select SFTP.
   3. Add a name and description in the Account name and Account description fields. These will help you identify the destination in the future.
   4. In the Hostname field, enter either of the following strings (do not include the quotation marks):
      
      • "adobe.conductor.com" for non-EU data residency
      • "adobe.eu.conductor.com" for EU data residency
   5. In the Username field, enter the Username your organization received from Conductor earlier in this guide.
   6. Click Add account.
      
8. Click Add location.
   
   
   1. Add a name and description in the Location name and Location description fields. These will help you identify the destination in the future. Note that this is especially important when you are creating multiple integrations with Conductor. Each location you add is tied to the specific web property and search engine you are integrating (represented by the Alias you generated earlier in these instructions). A distinct location name that includes the web property and search engine will help you tell these multiple integrations apart.
   2. In the Directory path field:
      • Delete the forward slash in the field, if one appeared by default.
      • Enter the path using the Alias your organization received from Conductor earlier in this guide. The format should be:
        [Alias for integration]/WEEKLY_PAGE/
   3. Click Add location.
      
9. Go to the Report options tab.
   
   1. Leave the File Name field unchanged and select the Append report date range to file name toggle.
   2. In the Report format section, ensure that CSV is selected, and then enable the Send report as compressed file (.zip) toggle.
      
   3. Leave the Report contents and Additional options sections unchanged. Failure to leave these unchanged may result in integration failures.
10. Go to the Scheduling options tab, select Schedule for later and configure the fields as follows:
    • If you report your weeks on a Sunday through Saturday cadence: 
      • Report frequency: Weekly
      • [Frequency] recurrence - every [X] week(s): 1
      • Day of the week: Sunday
      • Starting on: [The next corresponding Sunday]
      • Time of day: 2 AM
      • End Delivery Options: Never end
        
    • If you report your weeks on a Monday through Sunday cadence:
      • Report frequency: Weekly
      • [Frequency] recurrence - every [X] week(s): 1
      • Day of the week: Monday
      • Starting on: [The next corresponding Monday]
      • Time of day: 2 AM
      • End Delivery Options: Never end
11. Go to the Notification email tab.
12. In the Send notification email to field, enter an email to which a notification will be sent every time the report is successfully delivered or fails for any reason. Confirm this email address is where you want these notifications to be sent.
13. Click Save request.
    

Your Conductor Weekly Report is now configured. You can check its status in the Data Warehouse home.

For example, you can see whether the report was listed as:

• “Completed” when it successfully reached SFTP service.
• “Error” when it failed to send the request. In this case the issue might be in incorrect parameters or destination connectivity.

Configure Your Second Request in Data Warehouse (Monthly Report)

To create your second Data Warehouse Request, you'll duplicate your Weekly Page Report, and then make adjustments to accommodate the specific needs of the remaining Request. To do so:

1. Go to Data Warehouse home.
2. Select your Conductor Weekly Page Report in the table and click Copy to create the remaining Monthly request.
   
3. Make the changes associated with the second request listed in the table below.
4. Click Save Request.

Use this table to configure your remaining request. The table indicates the fields that require updates for the second Request. Fields not indicated in the table can remain as they are. Use the instructions above for reference.

(Do not include the brackets in the values you enter. They appear here only to distinguish the variables you need to enter in the fields.)

Location	Field	Change to...
General settings	Request name	"Conductor Monthly Report - [Alias for integration]" or similar
	Date ranges	Last Month
	Granularity	Monthly
Report destination	Add location > Directory path	[Alias for integration] /MONTHLY_PAGE/
Scheduling options	Monthly recurrence - every [x] month	1
	Day of the month	1

Repeat for Each Report Suite You Are Integrating

If you need to integrate more than one Report Suite, complete the instructions above for each Report Suite you need to integrate with Conductor.

Updating integrations from Adobe's legacy UI

In November of 2023, Adobe updated their UI in Data Warehouse. Previously created requests in Adobe continue to be sent successfully to Conductor without incident. However, were you to update previously created requests (for example, to change your selected metrics), you do need to update some information in the existing request to be compatible going forward in the new UI.

To update your requests:

1. In Adobe Analytics, follow the path Tools > Data Warehouse.
   
2. In the upper-left, select and verify the Adobe Report Suite you want to use for this integration. Remember, if you have multiple Report Suites to integrate, you’ll need to repeat this process for each.
   
3. For each existing Conductor request:
   1. Select the request in the table and click Edit.
   2. Go to the Report destination tab.
   3. Click Add account.
      
   4. From the Account type menu, select SFTP.
   5. Add a name and description in the Account name and Account description fields. These will help you identify the destination in the future.
   6. In the Hostname field, enter either of the following strings (do not include the quotation marks):
      
      • "adobe.conductor.com" for non-EU data residency
      • "adobe.eu.conductor.com/" for EU data residency
   7. In the Username field, enter the Username your organization received from Conductor earlier in this guide.
      
   8. Click Add account.
   9. Click Add location.
      
   10. Add a name and description in the Location name and Location description fields. These will help you identify the destination in the future. Note that this is especially important when you are updating multiple integrations with Conductor. Each location you add is tied to the specific web property and search engine you are integrating (represented by the Alias you use for these integrations). A distinct location name that includes the web property and search engine will help you tell these multiple integrations apart.
   11. In the Directory path field:
       • Delete the forward slash in the field, if one appeared by default.
       • Enter the path using the Alias your organization received from Conductor earlier in this guide. The format should be:
         [Alias for integration]/WEEKLY_PAGE/
   12. Click Add location.
       
   13. Click Save changes.
   14. Confirm by clicking Save changes again.
       

FAQs