Patent Publication Number: US-2018039998-A1

Title: Automated Integration of Partner Products

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 11/692,851, filed Mar. 28, 2007, now allowed, which claims the benefit of U.S. Provisional Patent Application No. 60/786,868 filed Mar. 28, 2006, for “Automated Integration of Partner Products,” the entire disclosures of which are incorporated herein by reference in their entireties. 
    
    
     TECHNICAL FIELD 
     The present invention is related to data integration, and more particularly to techniques for integrating data from multiple partners into a web analytics application. 
     BACKGROUND 
     The present invention provides a technique for integrating data from multiple partners into a web analytics application such as SiteCatalyst (available from Omniture, Inc. of Orem, Utah). Many prior art data sources&#39; interfaces are not intuitive, and do not provide sufficient visibility into partners with which customers can integrate. In addition, prior art systems do not generally present those partners, or the ability to integrate with them, in a way that motivates customers, partners, or press/analysts. 
     SUMMARY 
     The present invention provides techniques for improving integration of user interfaces for web analytics software tools, for simplifying and clarifying the ability to integrate with partner products, and also for branding the integration with the provider of the web analytics software with a global partner network. 
     In addition, the present invention provides techniques for improving communication to customers as to which partners have integration agreements with the provider of the web analytics software. In one user scenario, a customer has data within a partner product that is relevant to data in the web analytics tool and creates an integration to tie the two data sets together. 
     In another user scenario, a customer seeks to understand which partners have partnered with the web analytics software provider and wants to understand how to utilize that partnership. The customer views partners within a partner showcase to learn more. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The Figures provide an illustration of a technique for implementing the present invention according to one embodiment. 
         FIGS. 1 and 2  are screen shots depicting a user interface for adding marketing applications to a web analytics tool. 
         FIG. 3  is a screen shot depicting a dialog box for configuring a marketing application. 
         FIG. 4  is a screen shot depicting a list of various types of solution partners, including information and instructions for each. 
         FIG. 5  is a screen shot depicting steps for integrating a partner that is not currently part of a solution network. 
         FIG. 6  is a graphical depiction of the relationship between a web analytics tool and various partners. 
         FIG. 7  is a flowchart depicting a current method for integrating a partner with a web analytics tool. 
         FIG. 8  is a flowchart depicting an enhanced method for integrating a partner with a web analytics tool. 
         FIGS. 9A and 9B  depict two examples of a UI navigation scheme for a software application that implements the present invention. 
         FIG. 10  depicts an example of a partners home page, as may be displayed in connection with the Partners Tab box of  FIG. 8 . 
         FIG. 11  depicts a detail of the top section of the partners home page shown in  FIG. 10 . 
         FIG. 12  depicts a detail of the bottom section of the partners home page shown in  FIG. 10 . 
         FIG. 13  depicts an example of step  1  of a configuration wizard as may be displayed if the user is a first-time visitor. 
         FIG. 14  depicts an example of step  2  of a configuration wizard as may be displayed if the user is a first-time visitor. 
         FIGS. 15A, 15B, and 15C  depict an example of steps  1  to  3  of a partner data sources wizard. 
         FIGS. 16A, 16B, and 16C  depict an example of steps  4  to  6  of a partner data sources wizard. 
         FIG. 17  depicts an example of a screen for viewing and editing the customer&#39;s marketing world. 
         FIG. 18  depicts a detail of the top section of the screen shown in  FIG. 17 . 
         FIG. 19  depicts an alternative example of a screen for viewing and editing the customer&#39;s marketing world. 
         FIG. 20  depicts another alternative example of a screen for viewing and editing the customer&#39;s marketing world. 
         FIG. 21  depicts an example of a screen for viewing and editing partner information in a partner showcase. 
         FIG. 22  depicts an example of a screen for viewing and activating partner integrations. 
         FIG. 23  depicts an example of a screen for showing integration resources. 
         FIG. 24  depicts an example of a screen for showing integration tools. 
     
    
    
     DETAILED DESCRIPTION 
     For purposes of the present invention, an integration is a process of incorporating partner data into a data structure of a web analytics tool. For example, it may be desirable to integrate email campaign information, CRM system information, ad serving, search terms, and the like. Integrations can cause data to be sent from the partner to the web analytics tool, or vice versa. In some cases, integrations can facilitate a bidirectional flow of data. For example, for an email integration, the web analytics tool might receive campaign data from a partner, track visitor information to the site, and export information about visitors that behave a certain way and send it to the partner. 
     The present invention provides a user interface to allow partners to easily integrate with a web analytics tool via an intuitive, drag-and-drop interface. The techniques described herein facilitate a smooth and straightforward integration path for most partner data elements. 
     In one embodiment, a Partner Product Palette (PPP) assists in the automation of data integration from various online marketing ecosystem partners. A backend tool allows marketing to add to and customize the partner products displayed within the PPP. This tool allows marketing to associate a partner product with an appropriately typed data source (data import tool). For example, an e-mail vendor can be associated with an e-mail type data source. Once added, the partner product appears within the Partner Product Palette and the customers can begin the process of integrating their vendor&#39;s data into the web analytics tool. 
     The addition of new partner products instantly provides an automated data integration system for existing customers who currently use the added product. The PPP also allows marketing to control the visibility of each partner product and to organize these products by industry without writing any code to control the partner products. The tool gives them the ability to associate white papers, help links, logos, training videos, and other pertinent data regarding the data integration. 
     The following is a sample use case illustrating the use of PPP: 
     1. A partner product is approved by business development. 
     2. Business development adds the partner product through a user interface to manage the mechanism by which a partner product resides in the Partner Product Palette. The data entered include the product name, product information, company information, a product logo, product help documents, html links to training videos, the rank of product use, the industry to which this product belongs, and which data source type this product should use for integration. 
     3. A customer visits the Solutions Network page in the web analytics tool and can view the Partner Product Palette containing partner product logos and sort the partners by product name and by product industry. 
     4. A customer can then drag the partner product logo from the Partner Product Palette to the integrations area and begin the process of integrating that partner&#39;s data into the web analytics tool. 
     The Figures provide an illustration of a technique for implementing the present invention according to one embodiment. 
       FIG. 1  depicts a screen shot of a user interface for adding marketing applications to a web analytics tool. In one embodiment, the user can initiate integration of one or more marketing application(s)  102  by dragging and dropping marketing application(s)  102  from a repository  100  to a representation of the web analytics tool  101 . 
     In  FIG. 2 , the user in the process of dragging marketing application  102  to web analytics tool  101 . 
       FIG. 3  depicts a screen shot of a dialog box  103  for configuring the marketing application that was dragged to the web analytics tool  101 . In one embodiment, dialog box  103  presents a wizard that guides the user through the various steps involved, including for example naming the integration, providing details about an account associated with the marketing application, designating an eVar, mapping metrics to events, and reviewing a summary of the setup. Clicking on Next button  104  causes the wizard to proceed through the various steps involved. 
       FIG. 4  depicts a screen showing a list  400  of various types of solution partners  401 , including information and instructions  402  for each. 
       FIG. 5  depicts a screen showing steps  501 ,  502  for integrating a partner that is not currently part of the solution network: the user can set up a custom data source  503  by defining a specific set of data via a standardized template, or can insert data into the data processing engine via XML request  504 . Alternatively, the user can fill out a web-based form  505  for recommending a partner to be added to the network. 
       FIG. 6  is a graphical depiction of the relationship between a web analytics tool  101  and various marketing applications  102  associated with partners. For purposes of the following description, marketing applications  102  are also referred to herein simply as partners  102 . 
       FIG. 7  is a flowchart depicting one method for integrating a partner  102  with a web analytics tool. A user logs in  700 , configures data sources  701 . The user then configures an import/naming tool referred to as SiteCatalyst Attribute Import and Naming Tool (SAINT)  702 . SAINT can be used to bulk-import additional campaign attributes or classifications to the data. Next, the user configures  703  a data warehouse to act as a source and/or destination for data associated with the partner  102 . The integration is then complete  704 . 
       FIG. 8  is a flowchart depicting an enhanced method for integrating a partner with a web analytics tool, according to one embodiment of the present invention. 
     A user logs in  801  and selects a partners tab  802  in a user interface, so as to indicate that he or she is interested in integrating a partner  102 . A determination is made  803  as to whether the user is a first-time visitor. If so, the user is presented with a wizard to implement configuration  804  of his or her marketing world. First, the user is given an opportunity to identify  805  partners  102  to be integrated. Then, the user is given an option  806  to integrate partners  102  now or later. If the user chooses to do it later, he or she exits the integration mechanism and is presented with a display  807  of the marketing world. 
     If the user, in  806 , chooses to integrate partners  102  now, steps  808  through  814  are performed in the form of a data sources wizard. First, the user provides  808  a name and email address. Then, he or she chooses  809  the metrics that he or she wishes to apply to the data from the partner  102 . These metrics are then mapped  810  with the data available from the partner  102 . The user can then choose data dimensions  811  for breaking down the selected metric(s), and the dimensions are mapped  812 . The user is presented  813  with a summary of the integration, and can then choose to activate  814  it. 
     If the user wishes to integrate  815  another partner  102 , he or she is returned to step  805 . Otherwise, the integration is complete. The user exits the integration mechanism and is presented with a display  807  of the marketing world. 
     If, in  803 , the user is not a first-time visitor, he or she is given options to view or edit the marketing world  818 , or to view the partner showcase  819 , or to view and modify  820  partner integrations, or partner data sources  821 , or to control integration tools  822 . 
       FIGS. 9A and 9B  depict two examples of a UI navigation scheme for a software application that implements the present invention. In  FIG. 9A , a SiteCatalyst tab  901  provides access to various functions such as reports  902 , settings  903 , tools  904 , permissions  905 , data sources  906 , message boards  907 , and advanced analysis  908 . In  FIG. 9B , a PartnerWorld tab  909  has been added, providing access to the various functions described in connection with  FIG. 8 , including marketing world  818 , partner showcase  819 , viewing and modifying  820  partner integrations to information from one or more partners, partner data sources  821 , and integration tools  822 . 
       FIG. 10  depicts an example of a partners home page  1000 , as may be displayed in response to user activation of PartnerWorld tab  909  in  FIG. 9B . Page  1000  provides another navigation path to the same functions described in connection with  FIG. 8 , including marketing world  818 , partner showcase  819 , viewing and modifying  820  partner integrations to information from one or more partners, partner data sources  821 , and integration tools  822 . Page  1000  provides additional description of each of these options in an expandable/collapsible segment of the overall display. The currently active segment (marketing world  818 ) includes a configuration wizard  1102  of configuring the marketing world. Configuration wizard  1102  includes various links for adding  1103 , editing  1104 , and/or deactivating  1105  partner integrations. 
       FIG. 11  depicts a detail of the top section of the partners home page  1000  shown in  FIG. 10 . In one embodiment, scrolling banner  1101  is included, showing various partner logos. Configuration wizard  1102  includes various links for adding  1103 , editing  1104 , and/or deactivating  1105  partner integrations. Also provided is a link  1106  to a directory of alliance partners. 
       FIG. 12  depicts a detail of the bottom section of the partners home page  1000  shown in  FIG. 10 . Links to marketing world  818 , partner showcase  819 , viewing and modifying  820  partner integrations to information from one or more partners, partner data sources  821 , and integration tools  822  are included. Adjacent to each link is a description of the associated functionality. 
       FIG. 13  depicts an example of step  1  of a configuration wizard (ID partners)  1300  as may be displayed for identifying  805  partners  102 . The user selects a partner  102  from list  1301 . “Your partners” window  1302  tracks partners identified by the user. This data is used to populate the marketing world display  807 . 
       FIG. 14  depicts an example of step  2  of a configuration wizard (integrate partners)  1400  as may be displayed for integrating  806  partners  102 . The user selects a partner  102  with which to integrate by selecting from list  1401 . Information for the selected (highlighted) partner  102  is shown in box  1402 . “Integrate Now” button  1403  causes the system to proceed to step  808  to initiate the integration. “Integrate Later” button  1404  causes the system to proceed to marketing world display  807 . 
       FIGS. 15A, 15B, and 15C  depict an example of steps  1  to  3  of a partner data sources wizard, corresponding to steps  808 ,  809 , and  810  of  FIG. 8 . In  FIG. 15A , screen  1501  is shown for step  808 . The user can enter a name in field  1502  and an email address in field  1503 . In  FIG. 15B , screen  1504  is shown for step  809 . The user can enter, in fields  1505 , one or more metrics to be imported, and can click on checkboxes  1506  to indicate which metric(s) are active. In  FIG. 15C , screen  1509  is shown for step  810 . For each metric entered in screen  1504 , the user can map the metric description  1507  to a metric in the site analysis program, by selecting from pull-down menu  1508 . 
       FIGS. 16A, 16B, and 16C  depict an example of steps  4  to  6  of a partner data sources wizard, corresponding to steps  811 ,  812 , and  813  of  FIG. 8 . In  FIG. 16A , screen  1601  is shown for step  811 . In fields  1602 , the user can enter one or more data dimensions for breaking down the selected metric(s). Checkboxes  1603  allow the user to specify which dimension(s) are active. In  FIG. 16B , screen  1604  is shown for step  812 . For each dimension description entered in screen  1601 , the user can map the dimension description  1605  to an attribute associated with the site analysis program, by selecting from pull-down menu  1606 . 
       FIG. 16C  depicts screen  1607 , where a summary  1608  of data sources is presented, including data and selections made in previous steps. The user can click on “Save/Integrate Another Partner” button  1609  or “Save/Exit” button  1610 . 
       FIG. 17  depicts an example of a screen  1700  for viewing and editing the customer&#39;s marketing world, after partners  102  have been integrated. Screen  1700  is similar to screen  1000  shown in  FIG. 10 , but includes Edit links  1104  allowing the user to edit a previously-added integration, as well as Deactivate links  1105  allowing the user to deactivate a previously-added integration. 
       FIG. 18  depicts a detail of the top section of the screen shown in  FIG. 17 . 
       FIG. 19  depicts an alternative example of a screen  1900  for viewing and editing the customer&#39;s marketing world. Here, Edit links  1104  and Deactivate links  1105  are shown in a different configuration than that of  FIG. 17 . Partners  102  are arranged by marketing operation type  1107 . Also, Activate New buttons  1106  allow a user to activate new activations for a particular type  1107  of marketing operation. 
       FIG. 20  depicts another alternative example of a screen  2000  for viewing and editing the customer&#39;s marketing world. Here, partners  102  are arranged by marketing operation type  1107 . Activate New buttons  1106  allow a user to activate new activations for a particular type  1107  of marketing operation. 
       FIG. 21  depicts an example of a screen for viewing and editing partner information in a partner showcase as displayed in connection with step  819  of  FIG. 8 . The user can view partner information in many different ways. He or she can specify a sort order by selecting from options in box  2101 , and can select by partner name by clicking on an item in box  2102 , and can select by partner industry by clicking on an item in box  2103 . 
       FIG. 22  depicts an example of a screen  2200  for viewing and activating partner integrations, as may be displayed in connection with step  820  of  FIG. 8 . The user can see active partner integrations in boxes  2201 . The user can activate a new partner integration by selecting a partner  102  from list  2202 . A description appears in box  2203 , and the user can click on button  2204  to activate the integration. 
       FIG. 23  depicts an example of a screen  2300  for showing integration resources, as may be displayed in connection with step  821  of  FIG. 8 . Various resources  2301  can be shown, to allow the user to access white papers, training modules, and the like to help with partner integration efforts. The user can click on various links and icons to access the resources  2301 . 
       FIG. 24  depicts an example of a screen for showing integration tools, as may be displayed in connection with step  822  of  FIG. 8 . Various tools  2401  can be shown, including for example data warehouse and SAINT (an attribute import and naming tool). 
     In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the invention. 
     Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. 
     Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. 
     It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system&#39;s registers and memories into other data similarly represented as physical quantities within the computer system&#39;s memories or registers or other such information storage, transmission or display devices. 
     The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. 
     The algorithms and displays presented herein are not inherently related to any particular computer, network of computers, or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the required method steps. The required structure for a variety of these systems appears from the description. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein. 
     As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, the particular architectures depicted above are merely exemplary of one implementation of the present invention. The functional elements and method steps described above are provided as illustrative examples of one technique for implementing the invention; one skilled in the art will recognize that many other implementations are possible without departing from the present invention as recited in the claims. Likewise, the particular capitalization or naming of the modules, protocols, features, attributes, or any other aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names or formats. In addition, the present invention may be implemented as a method, process, user interface, computer program product, system, apparatus, or any combination thereof. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.