U.S. patent application number 15/783891 was filed with the patent office on 2018-02-08 for automated integration of partner products.
The applicant listed for this patent is Adobe Systems Incorporated. Invention is credited to Jessica Louise Petersen, Kevin Gary Smith, Alan Adams Winters.
Application Number | 20180039998 15/783891 |
Document ID | / |
Family ID | 38541760 |
Filed Date | 2018-02-08 |
United States Patent
Application |
20180039998 |
Kind Code |
A1 |
Winters; Alan Adams ; et
al. |
February 8, 2018 |
Automated Integration of Partner Products
Abstract
Automated integration of partner products in connection with a
web analytics application is facilitated. A list of available
partner products is displayed, and the user is provided with an
opportunity to select one or more of the displayed partner
products. A wizard is presented, allowing the user to configure the
partner product by specifying and mapping metrics, dimensions, and
the like. Partner product integration then takes place
automatically, thereby simplifying the process by which such
integrations can be implemented.
Inventors: |
Winters; Alan Adams;
(Lindon, UT) ; Petersen; Jessica Louise; (Salt
Lake City, UT) ; Smith; Kevin Gary; (Pleasant Grove,
UT) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Adobe Systems Incorporated |
San Jose |
CA |
US |
|
|
Family ID: |
38541760 |
Appl. No.: |
15/783891 |
Filed: |
October 13, 2017 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11692851 |
Mar 28, 2007 |
9792614 |
|
|
15783891 |
|
|
|
|
60786868 |
Mar 28, 2006 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06Q 10/10 20130101;
G06Q 30/02 20130101; G06Q 30/0601 20130101 |
International
Class: |
G06Q 30/02 20120101
G06Q030/02; G06Q 30/06 20120101 G06Q030/06; G06Q 10/10 20120101
G06Q010/10 |
Claims
1. A computer-implemented method for integrating specific partner
applications with web analytics applications, the method
comprising: displaying, via a graphical interface of a web
analytics application executed by a computer, a listing of partner
applications available for integration, wherein the web analytics
application includes information on a plurality of data metrics,
wherein each of the partner applications is associated with a
respective web marketing service; receiving, via the web analytics
application, user selection of a specific partner application from
the listing of partner applications available for integration,
wherein the specific partner application tracks web analytics data
and provides the web analytics data from a corresponding data
source; configuring, by the web analytics application, the specific
partner application by: receiving, via the graphical interface, a
first input describing the web analytics data to be imported from
the specific partner application and selected data metrics from the
web analytics application to be integrated with the web analytics
data from the specific partner application, and grouping the
selected data metrics according to data dimensions specified by a
second input received via the graphical interface; integrating, by
the web analytics application, corresponding elements of the web
analytics data into corresponding data structures storing the data
metrics, wherein integrating the web analytics data into the
corresponding data structures causes a bidirectional flow of the
web analytics data between a data source of the specific partner
application and the corresponding data structures of the web
analytics application; and generating, by the web analytics
application, output indicating that the corresponding elements of
the web analytics data have been successfully integrated.
2. The method of claim 1, wherein receiving the user selection of
the specific partner application comprises receiving a dragging
input that moves a representation of the specific partner
application from (i) a first portion of the graphical interface
displaying a listing of partner applications compatible with the
web analytics applications to (ii) a second portion of the
graphical interface displaying the listing of partner applications
available for integration.
3. The method of claim 2, further comprising providing a web-based
form for recommending a web analytics partner application to be
added to the partner applications compatible with the web analytics
applications.
4. The method of claim 1, wherein the listing of partner
applications available for integration is specific to a current
user of the web analytics application.
5. The method of claim 1, further comprising identifying, based on
input received via the graphical interface prior to receiving user
selection of the specific partner application, associations between
data sources and the partner applications available for
integration.
6. The method of claim 1, wherein grouping the selected data
metrics according to the data dimensions comprises: accessing a
mapping between (i) a data dimension description provided by a user
and (ii) a specific data dimension from the data dimensions; and
assigning, based on the mapping, a portion of the selected data
metrics to a group for the specific data dimension.
7. The method of claim 1, further comprising performing the
bidirectional flow of the web analytics data between the data
source of the specific partner application and the corresponding
data structures of the web analytics application by: receiving
additional web analytics data from the specific partner
application; tracking visitor information for a website; selecting
a portion of the visitor information based on the additional web
analytics data; and exporting, to the specific partner application,
the selected portion of the visitor information for storage in the
data source.
8. A computing system for integrating specific partner applications
with web analytics applications, the computing system comprising: a
display device configured for displaying, via a graphical interface
of a web analytics application, a listing of partner applications
available for integration, wherein the web analytics application
includes information on a plurality of data metrics, wherein each
of the partner applications is associated with a respective web
marketing service; an input device configured for receiving, using
the graphical interface, user selection of a specific partner
application from the listing of partner applications available for
integration, wherein the specific partner application tracks web
analytics data and provides the web analytics data from a
corresponding data source; and a processing device configured for
executing the web analytics application and thereby performing
operations comprising: configuring the specific partner application
by: (i) receiving, via the graphical interface, a first input
describing the web analytics data to be imported from the specific
partner application and selected data metrics from the web
analytics application to be integrated with the web analytics data
from the specific partner application, and (ii) grouping the
selected data metrics according to data dimensions specified by a
second input received via the graphical interface, integrating
corresponding elements of the web analytics data into corresponding
data structures storing the data metrics, wherein integrating the
web analytics data into the corresponding data structures causes a
bidirectional flow of the web analytics data between a data source
of the specific partner application and the corresponding data
structures of the web analytics application, and generating output
indicating that the corresponding elements of the web analytics
data have been successfully integrated.
9. The computing system of claim 8, wherein receiving the user
selection of the specific partner application comprises receiving a
dragging input that moves a representation of the specific partner
application from (i) a first portion of the graphical interface
displaying a listing of partner applications compatible with the
web analytics applications to (ii) a second portion of the
graphical interface displaying the listing of partner applications
available for integration.
10. The computing system of claim 9, the operations further
comprising configuring the display device to display a web-based
form, the web-based form configured for recommending a web
analytics partner application to be added to the partner
applications compatible with the web analytics applications.
11. The computing system of claim 8, wherein the listing of partner
applications available for integration is specific to a current
user of the web analytics application.
12. The computing system of claim 8, the operations further
comprising identifying, based on input received via the graphical
interface prior to receiving user selection of the specific partner
application, associations between data sources and the partner
applications available for integration.
13. The computing system of claim 8, wherein grouping the selected
data metrics according to the data dimensions comprises: accessing
a mapping between (i) a data dimension description provided by a
user and (ii) a specific data dimension from the data dimensions;
and assigning, based on the mapping, a portion of the selected data
metrics to a group for the specific data dimension.
14. The computing system of claim 8, the operations further
comprising performing the bidirectional flow of the web analytics
data between the data source of the specific partner application
and the corresponding data structures of the web analytics
application by: receiving additional web analytics data from the
specific partner application; tracking visitor information for a
website; selecting a portion of the visitor information based on
the additional web analytics data; and exporting, to the specific
partner application, the selected portion of the visitor
information for storage in the data source.
15. A non-transitory computer readable storage medium comprising
program instructions stored thereon for integrating specific
partner applications with web analytics applications, wherein the
program instructions are executable by a computing system to
perform operations comprising: displaying, via a graphical
interface of a web analytics application executed by a computer, a
listing of partner applications available for integration, wherein
the web analytics application includes information on a plurality
of data metrics, wherein each of the partner applications is
associated with a respective web marketing service; receiving, via
the web analytics application, user selection of a specific partner
application from the listing of partner applications available for
integration, wherein the specific partner application tracks web
analytics data and provides the web analytics data from a
corresponding data source; configuring, by the web analytics
application, the specific partner application by: receiving, via
the graphical interface, a first input describing the web analytics
data to be imported from the specific partner application and
selected data metrics from the web analytics application to be
integrated with the web analytics data from the specific partner
application, and grouping the selected data metrics according to
data dimensions specified by a second input received via the
graphical interface; integrating, by the web analytics application,
corresponding elements of the web analytics data into corresponding
data structures storing the data metrics, wherein integrating the
web analytics data into the corresponding data structures causes a
bidirectional flow of the web analytics data between a data source
of the specific partner application and the corresponding data
structures of the web analytics application; and generating, by the
web analytics application, output indicating that the corresponding
elements of the web analytics data have been successfully
integrated.
16. The non-transitory computer readable storage medium of claim
15, wherein receiving the user selection of the specific partner
application comprises receiving a dragging input that moves a
representation of the specific partner application from (i) a first
portion of the graphical interface displaying a listing of partner
applications compatible with the web analytics applications to (ii)
a second portion of the graphical interface displaying the listing
of partner applications available for integration. wherein the
operations further comprise providing a web-based form for
recommending a web analytics partner application to be added to the
partner applications compatible with the web analytics
applications.
17. The non-transitory computer readable storage medium of claim
15, wherein the listing of partner applications available for
integration is specific to a current user of the web analytics
application.
18. The non-transitory computer readable storage medium of claim
15, further comprising identifying, based on input received via the
graphical interface prior to receiving user selection of the
specific partner application, associations between data sources and
the partner applications available for integration.
19. The non-transitory computer readable storage medium of claim
15, wherein grouping the selected data metrics according to the
data dimensions comprises: accessing a mapping between (i) a data
dimension description provided by a user and (ii) a specific data
dimension from the data dimensions; and assigning, based on the
mapping, a portion of the selected data metrics to a group for the
specific data dimension.
20. The non-transitory computer readable storage medium of claim
15, the operations further comprising performing the bidirectional
flow of the web analytics data between the data source of the
specific partner application and the corresponding data structures
of the web analytics application by: receiving additional web
analytics data from the specific partner application; tracking
visitor information for a website; selecting a portion of the
visitor information based on the additional web analytics data; and
exporting, to the specific partner application, the selected
portion of the visitor information for storage in the data source.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] 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
[0002] 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
[0003] 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' 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
[0004] 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.
[0005] 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.
[0006] 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
[0007] The Figures provide an illustration of a technique for
implementing the present invention according to one embodiment.
[0008] FIGS. 1 and 2 are screen shots depicting a user interface
for adding marketing applications to a web analytics tool.
[0009] FIG. 3 is a screen shot depicting a dialog box for
configuring a marketing application.
[0010] FIG. 4 is a screen shot depicting a list of various types of
solution partners, including information and instructions for
each.
[0011] FIG. 5 is a screen shot depicting steps for integrating a
partner that is not currently part of a solution network.
[0012] FIG. 6 is a graphical depiction of the relationship between
a web analytics tool and various partners.
[0013] FIG. 7 is a flowchart depicting a current method for
integrating a partner with a web analytics tool.
[0014] FIG. 8 is a flowchart depicting an enhanced method for
integrating a partner with a web analytics tool.
[0015] FIGS. 9A and 9B depict two examples of a UI navigation
scheme for a software application that implements the present
invention.
[0016] FIG. 10 depicts an example of a partners home page, as may
be displayed in connection with the Partners Tab box of FIG. 8.
[0017] FIG. 11 depicts a detail of the top section of the partners
home page shown in FIG. 10.
[0018] FIG. 12 depicts a detail of the bottom section of the
partners home page shown in FIG. 10.
[0019] FIG. 13 depicts an example of step 1 of a configuration
wizard as may be displayed if the user is a first-time visitor.
[0020] FIG. 14 depicts an example of step 2 of a configuration
wizard as may be displayed if the user is a first-time visitor.
[0021] FIGS. 15A, 15B, and 15C depict an example of steps 1 to 3 of
a partner data sources wizard.
[0022] FIGS. 16A, 16B, and 16C depict an example of steps 4 to 6 of
a partner data sources wizard.
[0023] FIG. 17 depicts an example of a screen for viewing and
editing the customer's marketing world.
[0024] FIG. 18 depicts a detail of the top section of the screen
shown in FIG. 17.
[0025] FIG. 19 depicts an alternative example of a screen for
viewing and editing the customer's marketing world.
[0026] FIG. 20 depicts another alternative example of a screen for
viewing and editing the customer's marketing world.
[0027] FIG. 21 depicts an example of a screen for viewing and
editing partner information in a partner showcase.
[0028] FIG. 22 depicts an example of a screen for viewing and
activating partner integrations.
[0029] FIG. 23 depicts an example of a screen for showing
integration resources.
[0030] FIG. 24 depicts an example of a screen for showing
integration tools.
DETAILED DESCRIPTION
[0031] 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.
[0032] 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.
[0033] 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's data into the web analytics tool.
[0034] 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.
[0035] The following is a sample use case illustrating the use of
PPP:
[0036] 1. A partner product is approved by business
development.
[0037] 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.
[0038] 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.
[0039] 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's data into the web analytics
tool.
[0040] The Figures provide an illustration of a technique for
implementing the present invention according to one embodiment.
[0041] 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.
[0042] In FIG. 2, the user in the process of dragging marketing
application 102 to web analytics tool 101.
[0043] 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.
[0044] FIG. 4 depicts a screen showing a list 400 of various types
of solution partners 401, including information and instructions
402 for each.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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.
[0056] 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.
[0057] 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.
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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.
[0062] FIG. 17 depicts an example of a screen 1700 for viewing and
editing the customer'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.
[0063] FIG. 18 depicts a detail of the top section of the screen
shown in FIG. 17.
[0064] FIG. 19 depicts an alternative example of a screen 1900 for
viewing and editing the customer'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.
[0065] FIG. 20 depicts another alternative example of a screen 2000
for viewing and editing the customer'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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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).
[0070] 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.
[0071] 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.
[0072] 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.
[0073] 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's registers and memories into other data similarly
represented as physical quantities within the computer system's
memories or registers or other such information storage,
transmission or display devices.
[0074] 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.
[0075] 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.
[0076] 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.
* * * * *