Computing network for implementing a contextual navigation and action user experience framework and flattening a deep information hierarchy

Abstract

A context navigation and action user experience framework that facilitates workflows across multiple contexts and object hierarchy levels is disclosed. Exemplary features include a switcher interface, an action toolbar with context buttons and context tabs, and a toolkit that provides an overview portal to view alerts, cross-reference information, and perform actions on objects and insights important to the user across an entire product suite.

Description

Technical Field

[0001] This disclosure pertains to navigation and motion systems. Background Technology

[0002] Users of software interfaces increasingly demand user experience frameworks that provide faster navigation and contextual tools. Summary of the Invention

[0003] This disclosure relates to navigation and action systems for flattening deep information hierarchies and contextualizing actions within a multi-product platform, wherein “flattening” can be defined as making multi-level information accessible in one layer and broadening the user’s control.

[0004] The disclosed user experience framework (UX framework) may include one or more of the following components: swapper interface, action bar, and toolkit. These components work together to facilitate workflows across multiple context and object hierarchy levels.

[0005] According to one aspect of the subject matter described in this disclosure, an exchange interface can serve as a ubiquitous waypoint allowing users to select options for a layer. The exchange interface then guides the user to the options they are most likely to choose for subsequent layers. Users can also quickly switch between multiple layer contexts without having to retraceive the navigation tree. This exchange interface employs a two-level object hierarchy and transforms them into workflow contexts rather than hierarchies, thereby allowing for the efficient completion of similar sequences of operations across multiple contexts. In some embodiments, the exchange interface enables bypassing object (e.g., a communicator hub) and / or data (e.g., target communicators) hierarchies.

[0006] According to another aspect of the subject matter described in this disclosure, the action bar makes thousands of features easily discoverable and usable. The action bar floats at the top of the page, displaying buttons that trigger features supported by the page. In this context, the term "button" can be used to refer to an option. The action bar can personalize the button layout of individual pages—grouping similar buttons together, categorizing frequently used and important features to the left, importing features from other platform pages when other platform pages support a broader workflow, and showing or hiding functionality determined by the user's role and permissions.

[0007] The Actions bar provides access to features across the entire product suite and is populated by the user's context. It functions like a complete content management system, polling the user's role, object hierarchy context, page content, and supplementary product features to populate the Actions bar with features and buttons. The Actions bar shows users what is important, not just what they are interested in. Actions bar buttons can change state based on the selection in the workspace, but each page's Actions bar can visually display the full set of features and their associated buttons to support the user's feature discovery experience. Whenever a user begins a new workflow requiring additional features, they can be redirected to a new workspace with their associated Actions bar in a new core tab or contextual tab.

[0008] The action bar may also include a navigation panel that allows users to switch between platform sections that support specific workflows. Each section can contain multiple pages within a core tab for auxiliary navigation. Each core tab can open a sub-page within a context tab. Each context tab can open its own sub-page or sibling page to support the user's workflow. Context tabs can open side-by-side with core tabs, resulting in parent, child, sibling, and grandchild pages being displayed within a single level of the visual hierarchy.

[0009] The toolkit is both a user's backpack, containing useful multi-tools, and a second pair of hands to use those tools. The toolkit parses and displays insights, actions, and shortcuts based on the content of the current page, the user's role, and the communicator center or target communicator for whom they are working. Users can choose to change the context of the toolkit to contrast, compare, and cross-reference (1) the same objects, insights, and associated actions for different target communicators, or (2) different objects, insights, and associated actions for the same target communicator.

[0010] Some UX framework components can be hidden so users can focus on their content. The framework can switch between different modes: a standard execution mode, a collaborative and commenting presentation mode, an educational mode, and a recommendation mode that guides users through strategy optimization.

[0011] The UX framework is scalable and consistent. It supports pages built with a variety of different web technologies, defined as the various tools and techniques used in communication between different types of devices over the internet. The UX framework can accommodate a dramatic expansion of user types, permissions, and roles. It can also route users to the appropriate part of the platform upon login based on their organizational responsibilities. Attached Figure Description

[0012] In the accompanying figures, the present disclosure is illustrated by way of example rather than limitation, and the same reference numerals are used to refer to similar elements. Various elements shown in the following figures may be optional according to a given embodiment without departing from the principles provided in this disclosure.

[0013] Figure 1 A schematic block diagram of a system for managing campaigns and generating target communications, according to some disclosed embodiments, is shown.

[0014] Figure 2 A functional block diagram of a server for managing activities and generating target communications, associated with some embodiments of the disclosed system, is shown.

[0015] Figure 3 An example interface of a switch interface according to one embodiment is shown.

[0016] Figure 4 An example interface of an exchange with an alert badge is shown according to one embodiment.

[0017] Figure 5 An example interface with an action bar having action buttons is shown according to one embodiment.

[0018] Figure 6 An example of a difference button option, according to one embodiment, is shown that can be used in the communicator-centric view instead of the target communicator-centric view.

[0019] Figure 7 An example interface of an action bar with a core label, a context label, and a context label sibling is shown according to one embodiment.

[0020] Figure 8 An example of horizontal navigation within a label is shown according to one embodiment.

[0021] Figure 9 An example of a minimized V-shaped logo for an action bar interface is shown according to one embodiment.

[0022] Figure 10 An example of a creative toolkit according to one embodiment is shown.

[0023] Figure 11 An example of an information panel associated with a creative toolkit is shown according to one embodiment.

[0024] Figure 12 An example of an alarm and notification toolkit according to one embodiment is shown.

[0025] Figure 13An example of a health and recommendation toolkit according to one embodiment is shown.

[0026] Figure 14 An example of a site / application (app) toolkit according to one embodiment is shown.

[0027] Figure 15 An example of a location toolkit according to one embodiment is shown.

[0028] Figure 16 An example of a toolkit according to one embodiment is shown.

[0029] Figure 17 An example of a brief toolkit according to one embodiment is shown.

[0030] Figure 18 An example of a small switch according to one embodiment is shown.

[0031] Figure 19 An example of an action button according to one embodiment is shown.

[0032] Figure 20 An example of a toolkit label on a toolkit according to one embodiment is shown. Detailed Implementation

[0033] This disclosure relates to navigation and action systems for flattening deep information hierarchies and contextualizing actions within a multi-product platform, wherein “flattening” can be defined as making multi-level information accessible in one layer and broadening the user’s control.

[0034] The accompanying drawings and descriptions provided herein are simplified to illustrate aspects relevant to a clear understanding of the devices, systems, and methods described herein, while other aspects that may be found in typical similar devices, systems, and methods have been omitted for clarity. Those skilled in the art will recognize that other elements and / or operations may be desired and / or necessary for implementing the devices, systems, and methods described herein. However, because such elements and operations are well known in the art, and because they do not contribute to a better understanding of this disclosure, discussion of such elements and operations may not be provided herein. Nevertheless, this disclosure is intended to inherently include all such elements, variations, and modifications to the described aspects that would be known to those skilled in the art.

[0035] The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. For example, the singular forms “a,” “an,” and “described” as used herein may also be intended to include the plural forms unless the context clearly indicates otherwise. The terms “comprising,” “including,” “containing,” and “having” are inclusive and thus specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. Unless expressly determined as the order of execution, the method steps, processes, and operations described herein should not be construed as requiring them to be performed in the specific order discussed or shown. It should also be understood that additional or alternative steps may be employed.

[0036] Although the terms first, second, third, etc., may be used herein to describe various elements, components, regions, layers, and / or parts, these elements, components, regions, layers, and / or parts should not be limited by these terms. These terms are used only to distinguish one element, component, region, layer, or part from another. That is, unless the context clearly indicates otherwise, terms such as “first,” “second,” and other numerical terms, when used herein, do not imply order or sequence.

[0037] The disclosed UX framework can be designed to be used with desktop computers, laptops, mobile devices, or any other device capable of receiving and sending information through a user interface. As used herein, the term "button" refers to an option.

[0038] UX frameworks can be used to optimize targeted communications, particularly through a “communicator center” responsible for managing numerous targeted communication flows. In some embodiments, the term “targeted communication” can include bids, advertisements, or messages. The communicator center can be responsible for operating digital campaigns on behalf of multiple “targeted communicators.” The term “campaign” can refer to a strategy used to manage the dissemination of targeted communications to achieve desired objectives. Examples of targeted communicators can include advertisers, news agencies, or any person or entity that sends the targeted communications. To operate digital campaigns, the communicator center may employ digital campaign specialists or “managing users.” Targeted communicators share their objectives with the communicator center. The managing users translate these objectives into multiple actionable campaigns. Each campaign consists of multiple strategies or “groups.” Each group attempts to find, test, and scale ways to achieve the objectives within a set timeframe. Each group consists of a targeting rail and an optimization rail. The targeting rail provides the targeted communicator with data on how, where, and to whom to send the targeted communications. The optimization rail allows the targeted communicator to establish parameters for making campaign management decisions and optimizing campaign success.

[0039] Contextual navigation and action UX frameworks enable effective user experiences by creating dialogue with users in part by personalizing each page across a multi-product platform based on the user's role, workflow, object, and target communicator context, and by making deep information hierarchies accessible in one layer.

[0040] The UX framework employs an information hierarchy (IA) with multiple (e.g., seven) navigation levels, which requires multiple screens and browser windows to use successfully, and transforms this into a flat IA with multiple (e.g., two) levels of depth that can be used in a single browser window and guides the user to successfully complete their target communication workflow.

[0041] UX frameworks act as personalized content management systems, changing the features and tools displayed to users based on their roles, the objects they are working on, and the target communicators for which they are working.

[0042] In some embodiments, the UX framework features a visual navigation system where users do not need to lose their pages and retrace the navigation tree to change their position in the hierarchy. In some embodiments, the UX framework makes objects and features available and discoverable across multiple pages. In some embodiments, the UX framework is organized such that each product in the suite is taken with a click, rather than being hidden as a separate website or application.

[0043] Because administrators can work with multiple target communicators simultaneously, in some embodiments, the UX framework causes attention to insights, alerts, notifications, and state changes based on the single objective of each target communicator, regardless of where the administrator is within the platform. For example, if an administrator is working on object B under target communicator B, the UX framework will cause attention to insights about object A under target communicator A if relevant to target communicator A.

[0044] In some embodiments, the UX framework may also load pages written in different web technologies within a unified framework, wherein web technologies are defined as various tools and technologies used in communication between different types of devices via the Internet, and the unified framework is defined as an integrated system that processes information from such different web technologies and presents that information in a unified format.

[0045] A UX framework can include one or more unique features, including a switcher interface, action bar, and toolkit.

[0046] System Environment

[0047] Figure 1An advanced system 100 for managing targeted communication activities using multiple user interfaces is illustrated. In the illustrated embodiment, system 100 may include receiving audience behavior from one or more computing devices, either at one or more servers or on an external server. In some embodiments, audience behavior may be communication behavior targeting an audience. In the illustrated embodiment, the system may also include generating data; analyzing the data; generating one or more of smart categories 111, tags 112, or alerts 113, wherein smart categories are user-guided or context-sensitive pre-populated lists of target communicators; alerting the managing user on different computing devices; displaying the data to the managing user via exchange interface settings 101, action bar settings 102, and toolkit settings 103; generating activity adjustments via action bar settings 102 and toolkit settings 103; generating targeted communications; and transmitting the targeted communications to one or more computing devices.

[0048] According to some embodiments and such Figure 2 As shown, server 200 may include any combination of processor 260, memory 280, input / output (I / O) 210, and communication center 215, as well as other elements. As described in embodiments of the invention, each of processor 260, memory 280, I / O 210, and communication center 215 may include multiple corresponding units, subunits, and / or elements. Furthermore, each of processor 260, memory 280, I / O 210, and communication center 215 may be operatively or otherwise communicatively coupled to each other to facilitate the methods and techniques described herein.

[0049] Processor 260 can control any one or more of the memory 280, I / O 210, communication center 215, or any other unit that may include server 200, as well as any included sub-units, elements, components, devices, or functions performed by each or a combination of the memory 280, I / O 210, communication center 215, or any other unit that may include server 200. Any element or sub-element of server 200 presented herein may also be included in a similar manner. Figure 1 In any other unit, subunit, and device included in system 100. Furthermore, any action described herein as being performed by processor 260 may be taken by processor 260 alone, or by processor 260 in conjunction with one or more additional processors, units, subunits, elements, components, devices, etc. Additionally, although only one processor 260 is shown in the accompanying drawings, multiple processors may exist in or otherwise include in server 200, on an external server, or... Figure 1Other parts of system 100. Therefore, although instructions may be described as being executed by processor 260 or individual subunits 261, 262, 263, 264, 265 of the processor, instructions may be executed simultaneously, serially, or otherwise by one or more processors 260.

[0050] In some embodiments, processor 260 may be implemented as one or more computer processor (CPU) chips, graphics processing unit (GPU) chips, or some combination of CPU chips and GPU chips, and may include hardware devices capable of executing computer instructions. Processor 260 can execute any combination of instructions, code, computer programs, and scripts. Instructions, code, computer programs, and scripts may be received from, stored therein, or received from and stored therein from any combination of memory 280, I / O 210, communication center 215, sub-units of the previously described elements, other devices, and other computing environments. In some embodiments, a non-transitory computer-readable medium including code may be provided to perform one or more of the various processes, methods, functions, etc., described herein.

[0051] In some embodiments, processor 260 may include subunits and other elements. The subunits may include any combination of a profile manager 261, a content manager 262, a geolocation finder 263, a graphics processor 264, and a resource allocator 265. Each of these subunits of processor 260 may be communicatively or otherwise operably coupled to each other.

[0052] Profile Manager 261 can facilitate any combination of the generation, modification, analysis, transmission, and presentation of user profiles associated with users (e.g., first user, second user, etc.). For example, Profile Manager 261 can prompt a user via a first user device or a second user device to register by entering authentication credentials, personal identification information, contact information, preferred purchasing habits, location, or any other information that can be associated with generating a user's personal profile. Profile Manager 261 can also control or utilize the elements of I / O 210 to enable users to take pictures or videos of themselves or another person. Profile Manager 261 can receive, process, analyze, organize, transform, or any combination of these contents received from a user or another computing element to generate a user profile that may include any combination of personal information, contact information, user preferences, photos, videos, audio clips, user behavior history, user preferences, user search history, user location, settings, etc.

[0053] Content Manager 262 can facilitate any combination of the generation, modification, analysis, transmission, and presentation of media content associated with methods and systems for disintermediation of network communications. For example, Content Manager 262 can control the environment of an application during the execution of various processes. For illustrative and non-limiting purposes, the media content that Content Manager 262 can handle may include any combination of advertisements, images, text, themes, audio files, video files, documents, etc. In some embodiments, Content Manager 262 can also interface with any combination of third-party content servers, storage locations, and / or databases.

[0054] The geolocation finder 263, particularly communicating with geolocation information provided, for example, by the GPS subsystem of a user device, can facilitate any combination of the detection, generation, modification, analysis, transmission, and presentation of location information. Location information may include any combination of Global Positioning System (GPS) coordinates, Internet Protocol (IP) address, Media Access Control (MAC) address, geolocation information, address, port number, postal code, server number, agent name, agent number, device information, serial number, etc.

[0055] In some embodiments, the geolocation finder 263 may include dedicated hardware elements, any one or a combination of various sensors, for enabling the geolocation finder 263 to acquire, measure and transform location information.

[0056] The graphics processing unit (GPU) 264 can facilitate any combination of the generation, modification, analysis, processing, transmission, and presentation of visual content. The GPU 264 can be configured to render visual content for presentation on a user device and / or analyze the visual content to obtain metadata associated with the user or user device. In some embodiments, the visual content may include search results and / or a display that can activate a communication channel. The GPU 264 may include multiple GPUs and can therefore be configured to perform and / or execute multiple processes in parallel.

[0057] Resource allocator 265 can facilitate any one or a combination of the identification, monitoring, analysis, and allocation of resources throughout server 200, any component of system 100, or other computing environments. For example, resource allocator 265 can facilitate interaction between server 200, any subunit of server 200, and a large number (e.g., multiple) of users or associated user devices. Thus, the computing resources of server 200, such as processing power, data storage space, network bandwidth, etc., utilized by processor 260, memory 280, I / O 210, communication center 215, and any subunit of these units or combinations thereof, may be in high demand at various times during operation. Therefore, resource allocator 265 can be configured to manage the allocation of various computing resources as needed by specific units or subunits of server 200.

[0058] In some embodiments, the resource allocator 265 may include sensors and / or other dedicated hardware for monitoring the performance of each unit and / or subunit of server 200, and hardware for responding to the computing resource requirements of each unit or subunit. In some embodiments, the resource allocator 265 may utilize computing resources of a second computing environment separate from and distinct from server 200 to facilitate desired operation.

[0059] In some embodiments, factors influencing the allocation of computing resources by the resource allocator 265 may include the number of ongoing user equipment connections and / or other communication channel connections, the duration for which one or more components of server 200 require computing resources, etc. In some embodiments, computing resources may be allocated to and / or distributed across multiple second computing environments included in server 200 based on one or more of the aforementioned factors. In some embodiments, the allocation of computing resources by the resource allocator 265 may include one or more resource allocators 265 toggling switches, adjusting processing power, adjusting memory size, partitioning memory elements, transferring data, controlling one or more input and / or output devices, modifying various communication protocols, etc. In some embodiments, the resource allocator 265 may facilitate the use of parallel processing techniques, such as those dedicated to multiple GPUs included in processor 260.

[0060] Processor 260 and any or all processor subunits including subunits 261, 262, 263, 264 and 265 can be used to execute processes initiated by switch interface settings 101, action bar settings 102 and toolkit settings 103.

[0061] In some embodiments, memory 280 may be used to store, retrieve, receive, transmit, and / or access various files and / or information during operation of server 200, or any combination thereof. Memory 280 may also be used to store, retrieve, and / or update user profile information, etc. Memory 280 may include various types of data storage media, such as solid-state storage media, hard disk storage media, and any other type of data storage media known to those skilled in the art. Memory 280 may include dedicated hardware components, such as hard disk drives and / or servers, and software components, such as cloud-based storage drives. For example, memory 280 may include various subunits, such as operating system unit 281, application data unit 282, application programming interface (API) unit 283, profile storage unit 284, content storage unit 285, video storage unit 286, secure enclave 287, and / or cache storage unit 288.

[0062] Memory 280 and any of its subunits described herein may include any or any combination of random access memory (RAM), read-only memory (ROM), and various forms of secondary storage devices. RAM may be used to store volatile data and / or instructions that can be executed by processor 260. For example, the stored data may be any or a combination of commands, the current operating state of server 200, the expected operating state of server 200, etc. As another example, the data stored in memory 280 may include instructions related to the various methods and / or functions described herein. ROM may be a non-volatile memory device that may have a smaller memory capacity than the secondary storage device. ROM may be used to store instructions and / or data that can be read during the execution of computer instructions. In some embodiments, access to both RAM and ROM may be faster than access to the secondary storage device. The secondary storage device may include one or more disk drives and / or tape drives and may be used for non-volatile storage of data, or, if RAM is not large enough to hold all working data, the secondary storage device may be used as an overflow data storage device. The secondary storage device may be used to store programs that can be loaded into RAM when selected for execution. In some embodiments, memory 280 may include one or more databases for storing any data described herein. Alternatively, memory 280 may utilize and / or access one or more auxiliary databases located remotely from server 200.

[0063] Operating system unit 281 can facilitate the deployment, storage, access, execution, and / or utilization of the operating system used by server 200 and / or any other computing environment described herein. In some embodiments, the operating system may include various hardware and / or software elements serving as a structural framework for enabling processor 260 to perform various operations. Operating system unit 281 may also store various information and / or data associated with the operation of the operating system and / or server 200 as a whole, such as the status of computing resources (e.g., processing power, memory availability, resource utilization, etc.), runtime information, modules for directing the execution of the operations described herein, user licenses, security credentials, etc.

[0064] Application data unit 282 can facilitate the deployment, storage, access, execution, and / or utilization of applications by server 200 or any other computing environment (e.g., user equipment) described herein. For example, a user may need to download, access, and / or otherwise utilize software applications on a user device such as a smartphone or other internet-enabled device to perform the various operations described herein. Therefore, application data unit 282 can store any information and / or data associated with the application that allows the application and / or user equipment to perform methods associated with the non-mediation of network communications. Thus, the information included in application data unit 282 enables the user to perform the various operations described herein. Application data unit 282 can also store various pieces of information and / or data associated with the operation of the application and / or server 200 as a whole, such as the status of computing resources (e.g., processing power, memory availability, resource utilization, etc.), runtime information, modules used to guide the execution of the operations described herein, user licenses, security credentials, etc.

[0065] Application Programming Interface (API) unit 283 can facilitate the deployment, storage, access, execution, and / or utilization of information associated with APIs of server 200 and / or any other computing environment (e.g., user equipment) described herein. For example, server 200 may include one or more APIs to enable various devices, applications, and / or computing environments to communicate with server 200, multiple other servers, databases, or other user equipment. Therefore, API unit 283 may include an API database containing information that can be accessed and / or utilized by applications and / or operating systems of other devices and / or computing environments associated with network communication non-mediation. APIs can orchestrate communication between backend components of user equipment and server 200. In some embodiments, each API database may be associated with custom physical circuitry included in memory unit 280 and / or API unit 283. Additionally, each API database may be public and / or private, thus requiring authentication credentials to access information within the API database.

[0066] Profile storage unit 284 can facilitate the deployment, storage, access, and / or utilization of information associated with a user's profile by server 200 and any other computing environment (e.g., user equipment) described herein. For example, profile storage unit 200 may store one or more of the following: user contact information, authentication credentials, user preferences, user behavior history, personal information, search history, purchase history, user ratings, and metadata. Profile storage unit 284 may store the user's image, search history, user location history determined by the user equipment's GPS subsystem, etc. In some embodiments, profile storage unit 284 may communicate with profile management unit 261 to receive and / or transmit information associated with a user's profile.

[0067] Content storage unit 285 can facilitate the deployment, storage, access, and / or utilization of information associated with requested content by server 200 and / or any other computing environment described herein (e.g., user devices such as mobile devices). For example, content storage unit 285 can store one or more of images, text, video, audio content, advertisements, product listings, user recommendations, and metadata that will be presented to the user during the operations described herein. In some embodiments, content storage unit 285 can communicate with content management unit 262 to receive and / or transmit content files.

[0068] Media storage unit 28 can facilitate one or more of the deployment, storage, access, analysis, and utilization of media content by server 200 and any other computing environment (e.g., user equipment) described herein. Media content can be images, videos, audio files, and any other form of communication media. For example, media storage unit 286 can store one or more chat histories between users on system 100 and other users. Furthermore, media storage unit 286 can store one or more searches, results, alerts, etc., generated by any unit or subunit of server 200 or user equipment. Media content generated or used in performing any of the methods disclosed herein can be stored in media storage unit 286, allowing the media content to be analyzed in real-time and after it has been received by various components of server 200. In some embodiments, media storage unit 286 can communicate with GPU 264 to facilitate any of the processes described herein. In some embodiments, media content can include audio, images, text, video feeds, and / or any other media content associated with methods and systems for non-mediation of network communications.

[0069] Secure Enclave 287 can facilitate secure data storage. In some embodiments, Secure Enclave 287 may include a partitioned portion of the storage medium included in memory unit 280, which is protected by various security measures. For example, Secure Enclave 287 may be hardware-protected. In other embodiments, Secure Enclave 287 may include one or more firewalls, encryption mechanisms, and / or other security-based protocols. User authentication credentials may be required before granting a user access to data stored within Secure Enclave 287. In some embodiments, Secure Enclave 287 may store sensitive user information, such as credit card data, sensitive personal data, and / or data associated with a person's location over time.

[0070] Cache storage unit 288 can facilitate short-term deployment, storage, access, analysis, and / or utilization of data. In some embodiments, cache storage unit 288 can serve as a short-term storage location for data, enabling rapid access to data stored in cache storage unit 288. In some embodiments, cache storage unit 288 may include RAM and / or other storage media types that enable rapid retrieval of stored data. Cache storage unit 288 may include partitioned portions of the storage media included in memory 280.

[0071] The switch interface settings 101, action bar settings 102, and toolkit settings 103 can be stored on any one or all of the storage sub-units (including sub-units 281, 282, 283, 284, 285, 286, 287, and 288) of one or more servers.

[0072] I / O unit 210 may include hardware and / or software elements for enabling server 200 to receive, transmit, and / or present information. For example, elements of I / O unit 200 may be used to receive user input from a user via a user device, present results, alarms, or assembly responses to a user via a user device, present suggested matches to a user via a user device, etc. In this way, I / O unit 210 enables server 200 to interface with a human user in a manner that can be used by the user in the methods described herein. As described, I / O unit 210 may include sub-units, such as one or a combination of I / O device 211, I / O calibration unit 212, and / or media driver 213.

[0073] I / O device 210 can facilitate any or any combination of receiving, transmitting, processing, presenting, displaying, inputting, and outputting information as a result of the execution processes described herein. In some embodiments, I / O device 210 may include a plurality of I / O devices. In some embodiments, I / O device 210 may include one or more elements of any or a combination of user equipment, computing system, server 200, and similar devices.

[0074] I / O device 211 may include various components that enable a user to interface with server 200. For example, I / O device 211 may include a keyboard, touchscreen, buttons, sensors, biometric scanners, lasers, microphones, cameras, internet-enabled devices, and / or another component for receiving and / or collecting input from the user. Additionally and / or alternatively, I / O device 211 may include a display, screen, sensors, vibration mechanisms, light-emitting diodes (LEDs), speakers, radio frequency identification (RFID) scanners, and / or another component for presenting and / or otherwise outputting data to the user. In some embodiments, I / O device 211 may communicate with one or more components of processor 260 and / or memory unit 280 to perform the operations described herein. For example, I / O device 211 may include a display that can utilize GPU 264 to present media content stored in media storage unit 286 to a user of a user device.

[0075] I / O calibration unit 212 can facilitate the calibration of I / O device 211. For example, I / O calibration unit 212 can detect and / or determine one or more settings of I / O device 211, and then adjust and / or modify the settings so that I / O device 211 can operate more efficiently. In some embodiments, I / O calibration unit 212 can utilize media driver 213 (or multiple media drivers) to calibrate I / O device 211. Media driver 213 can be installed on user equipment so that user equipment can recognize I / O device 2114 and / or integrate with it, thereby enabling media content to be displayed, received, generated, etc. In some embodiments, I / O device 211 can be calibrated by I / O calibration unit 212 based on information included in media driver 213.

[0076] Communication center 215 facilitates the establishment, maintenance, monitoring, and / or termination of communication between server 200 and other devices (such as user equipment), other computing environments, third-party server systems, etc. Communication center 215 can also enable communication between various components (e.g., units and / or sub-units) of server 200 as needed. In some embodiments, communication center 215 may include network protocol unit 216, API gateway 217, encryption engine 218, and / or communication device 219. Communication center 215 may include hardware and / or software components.

[0077] Network protocol unit 216 can facilitate the establishment, maintenance, and / or termination of communication connections between server 200 and another device (e.g., user equipment) over a network. For example, network protocol unit 216 can detect and / or define the communication protocols required for specific networks and / or network types. The communication protocols used by network protocol unit 348 may include Wi-Fi protocols, Li-Fi protocols, cellular data network protocols, etc. Protocols such as WiMAX, Ethernet, and Power Line Communication (PLC) are included. In some embodiments, facilitating communication between server 200 and any other device and any component within server 200 may include transforming and / or converting data from a protocol compatible with a first communication protocol to a protocol compatible with a second communication protocol. In some embodiments, network protocol unit 216 may determine and / or monitor data traffic to thus determine which specific network protocol will be used to establish a connection with the user equipment, transmit data, and / or perform other operations described herein.

[0078] API gateway 217 can facilitate access to API unit 283 of memory 280 of server 200 by other devices and / or computing environments. For example, user equipment can access API unit 283 via API gateway 217. In some embodiments, API gateway 217 may need to verify user credentials associated with a user of the user equipment before granting access to API unit 283 to a user. API gateway 217 may include instructions for enabling server 200 to communicate with another device.

[0079] Encryption engine 218 can facilitate any or any combination of transformation, encryption, encoding, decryption, and decoding of information received, transmitted, and / or stored by server 200. For example, encryption engine 218 can encrypt data associated with a user's credit card information. Using the encryption engine, for security reasons, data can be encrypted, encoded, and / or transformed for each transmission, and can be encrypted, encoded, and / or transformed before any received data is processed and / or stored. In some embodiments, encryption engine 218 can generate any or any combination of encryption keys, encoding keys, transformation keys, etc., which can be transmitted along with any data content.

[0080] Communication device 219 may include various hardware and / or software specifically designed to enable communication between server 200 and another device (e.g., user equipment) and communication between components of server 200. In some embodiments, communication device 219 may include one or more radio transceivers, chips, analog front-end (AFE) units, antennas, processors, memory, other logic and / or other components to implement communication protocols (wired or wireless) and related functions to facilitate communication between server 200 and any other device. Additionally and / or alternatively, communication equipment 219 may include modems, modem groups, Ethernet devices such as routers or switches, Universal Serial Bus (USB) interface devices, serial interfaces, token ring devices, Fiber Distributed Data Interface (FDDI) devices, Wireless Local Area Network (WLAN) devices and / or device components, radio transceiver devices (such as Code Division Multiple Access (CDMA) devices, Global System for Mobile Communications (GSM) radio transceiver devices, Universal Mobile Telecommunications System (UMTS) radio transceiver devices, Long Term Evolution (LTE) radio transceiver devices, Global Microwave Access Interoperability (WiMAX) devices) and / or another device for communication purposes.

[0081] user interface

[0082] In execution Figures 3-20 During the operation shown, the example interface described herein can communicate with server 200 to access information from the server or external sources. The example interface described herein can be implemented as follows: Figure 1 Part of the system described herein. Furthermore, through... Figures 3-20 The user interface startup action described herein can be executed by processor 260 using memory 280 or an external source. Additionally, Figures 3-20 The example user interface described herein can use the communication resources of a separate server and / or computer system.

[0083] Switch Interface

[0084] The exchange interface 300 is a sophisticated filter that allows management users to select which communicator centers and / or target communicators' content to display. The exchange interface immediately narrows the view to managing the specific communicator centers and / or (one or more) target communicators with which the user wants to work, and expands the view because within that communicator center / target communicator selection, a wide range of pages and analyses related to those communicator center / target communicator specifications are readily available.

[0085] like Figure 3As shown, in some embodiments, the exchange interface may consist of three panes: a list of communicator centers from which the administrator can select to switch pages to filter on communicator centers of interest; a list of target communicators in user-guided or context-sensitive intelligent categories 111 from which the administrator can select a subset of target communicators to open a communicator center; and a list of target communicators from which the administrator can select to switch pages to filter on a specific communicator center. When the administrator clicks on a communicator center, a category can be automatically selected, allowing the administrator to immediately click on a target communicator. The administrator can select communicator centers and target communicators to allow for seamless navigation within the workflow.

[0086] Similarly, Figure 3 As shown, in some embodiments, target communicator groups allow managing users to view or select from subgroups of target communicators. These user-guided or context-sensitive smart categories 111 direct user management to pages of particular interest. Some smart categories 111 may be based on user-guided preferences, such as favorites 302 or recently visited 303. Other categories may be context-based grouping to help draw attention to pages of particular interest and aid in workflow management and planning. For example, a smart category 111 may provide a list of target communicators with activities predicted not to meet its objective 301 or with live activities 304. This draws attention to pages that managing users might want to prioritize.

[0087] The exchange interface allows administrators to navigate between multiple target communicators without backtracking. Instead of requiring administrators to view a specific page for a particular target communicator and then navigate a vertical tree to view the same page for different target communicators, the exchange interface allows for click-based navigation, bypassing the need for vertical navigation, enabling administrators to directly jump from viewing a specific page for a particular target communicator to the same page for different target communicators. In some embodiments, the communicator center and target communicators can be selected sequentially, allowing administrators to move between different tasks and switch between sections and pages in the site map without being interrupted by navigation hierarchy traversal. In some embodiments, the selected target communicator is highlighted, letting administrators know which target communicator is selected at any given time.

[0088] In some embodiments and in other cases, some pages may not support the current administrative user's view selection. This can occur when an administrative user opens a page and the exchange interface navigates to the communicator center or the target communicator selection is abnormal. For administrative users with access to both the communicator center-level view and the target communicator-level view, switching from a page displaying target communicator-level details to a page displaying communicator center-level details requires no additional navigation. The exchange interface can seamlessly and automatically switch from the target communicator view to the communicator center view, allowing administrative users to view the desired page without consciously navigating away from the target communicator view. The automatic exchange interface functionality can also switch back from the communicator center view to the target communicator view when the administrative user navigates to a page available for the target communicator-level view.

[0089] In some embodiments, the exchange interface may be part of a sticky page header and cannot be hidden. In this embodiment, unless an exception has been made, the exchange may appear at the top of every page and may always be visible, regardless of how far the managing user scrolls down the page. In other embodiments, when opened, the exchange interface scrolls to the currently selected option. In other embodiments, any changes to the exchange interface are animated. In some embodiments, an open exchange interface is closed by selecting a different area of ​​the page or by selecting ESC. In other embodiments, the exchange communicator center and target communicator list support pagination.

[0090] In some embodiments, unless an exception has been made, the page can be filtered to a single target communicator, or multiple target communicators under a single communicator center. In some embodiments, controls and other objects necessary for successful use of the software are always visually accessible, and navigation is made visible.

[0091] In some embodiments, if the current managing user's contact center list or target contact list is very long, the current selection may not be on the first page of the results. In this case, the contact center or target contact can be injected at the top of the paginated list and the scroll position of the list can be modified. Note that the injected contact center or target contact can also appear on the page containing the contact center or target contact list.

[0092] In some embodiments, the communicator center list displays communicator centers accessible to the administrator user, grouped according to communicator center groups. If the administrator user can access more than one communicator center, the communicator center list can be displayed. In some embodiments, a page having the ability to display content of target communicators accessible to the administrator user under a specific communicator center may include an inventory page, reports, locations, templates, a homepage, and target communicator groups.

[0093] like Figure 4 As shown, in some embodiments, marker 112 routes the user's attention to the communicator center, the target communicator group, and ultimately to target communicators that may need to be prioritized, such as those with activities predicted to not meet their objectives. The marker 112 for target communicators may indicate the total count of activities predicted to not meet their objectives. Target communicator groups and communicator centers may be marked to show that they contain marked target communicators.

[0094] In some embodiments, the general search can return the communicator center and the target communicator as search results. Clicking on the communicator center in the general search returns the recently viewed target communicators for that communicator center. If the communicator center does not have any recently viewed target communicators, the search can revert to the first favorite target communicator or the first target communicator in the full list. Selecting a target communicator in the general search results allows you to select the target communicator and the corresponding communicator center in the exchange.

[0095] In some embodiments, if a user opens a context tab and switches to a different target communicator, this can trigger an autosave if the page supports autosave. If the page has unsaved changes and includes a workflow of abandoned changes, the page can display an unsaved changes popup.

[0096] Action bar

[0097] The Action Bar 500 is a toolbar designed for faster and easier navigation, cross-referencing, and access to relevant interface buttons. The Action Bar showcases the richness of functionality on a page, making it easy to discover and activate platform features. In some embodiments, the Action Bar 500 appears on a non-modal page within the platform.

[0098] like Figure 5 As shown, in some embodiments of the action bar 500, all or most of the interface buttons 501 are conveniently located in one area. Some of these interface buttons 501 may include "Create New Group", "Add Track", "Upload Creative", "Edit Goals & Budget", "Edit Activity Details", "Manage Reports & Attribution", "Measure Visibility", "Manage Fees & Rates", "Edit Settings", and "View Behavior Log". The action bar may attempt to place all the buttons from all pages into the horizontal space provided to it.

[0099] like Figure 6As shown, in some embodiments, the interface buttons 501 appearing on the action bar 500 can be customized to suit the page being viewed. These contextual buttons take into account the page being viewed and are customized for their relevance to the page and their importance to the user. For example, the action bar 500 may contain multiple interface buttons 501. At the hub level, these interface buttons may include "New Target Communicator," "Bulk Edit Target Communicators," "Bulk Edit Campaign," and "Clone Campaign" buttons, while at the target communicator level, these buttons may alternatively be "Favorite Target Communicators," "Add Target Communicator Track," "New Campaign," "Import Bulk Edit," "Upload Creative," "Add Brand Enhancement Research," "Bulk Edit Campaign," "Clone Campaign," "Export Campaign," "Bulk Edit Ad Groups," "Clone Ad Groups," "Export Ad Groups," "Manage Preferences," "View Costs," "View Data Settings," "External Live TV Touch Plans," and "Generate Preview" buttons.

[0100] like Figure 7 As shown, in some embodiments, the action bar may also display a navigation panel 710 providing access to sections of interest such as "Home," "Plans," "Inventory," and "Data," as well as core tab 701. Contextual tabs 702 may be provided when a core tab is selected. Contextual tabs 702 avoid the need for excessive navigation by providing relevant tabs based on user input and remembering these tabs for easier horizontal navigation and cross-referencing. These tabs may be presented based on already selected pages, making it easy to access related pages. Selecting a specific page can automatically populate relevant tabs that the user might be interested in while viewing the selected page. Having contextual tabs 702 allows users to navigate easily without having to backtrack, thus improving the cross-referencing interface. Contextual tabs 702 allow users to return to recently used pages without consciously creating new tabs or navigating vertically. This is particularly useful for managing users who frequently cross-reference and need to repeatedly cycle through several pages.

[0101] Figure 7 It is also shown that in some embodiments, the core label 701 is used to include first-level navigation within the platform's content. For example... Figure 7As shown, core label 701 can include all "All Activities," "Creatives," "Locations," and "Groups." Unlike context label 702, core label 701 is always visible to administrative users. Core label 701 can be used to store dashboards, list views, and information hubs, corresponding to the starting point of discrete administrative user workflows. Platform sections with core label 701 can have different sets of core labels 701, but not every platform section can have core label 701. Core label 702 can appear in a section of the platform. Core label titles can be localized. Core label 701 can be bound to roles and permissions. Some administrative users can have a subset of the core labels 701 available to them. The set of core labels 701 displayed within a platform section may remain unchanged. Navigating between core labels 701 or context labels 702 within a section may not introduce or remove any core labels 701. When an administrative user navigates to a platform section, the first core label 701 can be automatically selected. Core label 701 can have the following states: selected, hovered, or not selected.

[0102] like Figure 7 As further shown, in some embodiments, context tab 702 is used to house the detail pages of existing objects, enabling administrative users to review the state of objects and modify their configurations. Context tab 702 reduces the breadth friction of the navigation platform by flattening what would otherwise be a deeply nested page hierarchy. In some embodiments, context tab 702 may open context tab sibling 703. Context tab sibling 703 contains insights that can be easily cross-referenced by switching between object details and object insights. For example, such as... Figure 7 As shown, a context label can be an "Activity" label, which can then open related "Activity Insights" context label siblings. Context label siblings 703 can be optional and can be used by a small number of context labels 702. In other embodiments, context labels 702 can open sub-context labels 704. Detailed pages that themselves include lists of objects, such as those listing group activities, can open sub-context labels 704 to display details of sub-objects. In some embodiments, sub-context labels 704 may not open their own sub-context labels 704.

[0103] In some embodiments, context tab 702 remains open in each section throughout the administrator user's session, allowing the administrator user to quickly return to their most recently opened object. Some embodiments maintain scroll position when switching back and forth between tabs in the context tab set. Some embodiments allow the administrator user to switch between pages in the platform section and the context tab set without refreshing. Some embodiments allow the administrator user to return to their most recently opened tab, rather than the section where the page tab falls, when switching between platform sections. In some embodiments, only one set of context tabs 702 can be open in each platform section at a time. A context tab set is a group of context tabs 702 associated with an object, context tab siblings 703, and child context tabs. If the administrator user selects an object to open in the context tab set, the action bar can close and replace any context tab sets already open in the platform section. When a context tab 702 is selected by selecting a button or object in the core tab 701, the context tab 702 can be automatically selected, and its parent core tab 701 can be deselected. Child context tabs 704 can be opened by selecting a button or object in the context tab 702. The child context label 704 can be automatically selected and the parent context label 702 can be deselected. If the context label 702 is associated with a sibling insight label, the context label sibling 703 can be automatically opened when the context label 702 is opened.

[0104] In some embodiments, the set of context tabs can remain open for the duration of the administrator's session, allowing the administrator to easily return to their recently viewed objects, especially when their workflow involves them across multiple platform sections. The context tabs 702 can also remain open even when the administrator switches between core tabs 701 within the same platform section or between different platform sections in the navigation panel 710.

[0105] In some embodiments, context label 702 cannot be manually closed, but is automatically closed when an administrator opens a new context label 702 at the same level in the hierarchy; opening a new context label 702 within a section closes and replaces the opened context label 702, its child context label 704, and its context label sibling 703; or opening a new child context label 704 closes and replaces the opened child context label 704 and its context label sibling 703.

[0106] In some embodiments, the exchange interface 300 selection can be changed through manual administrative user manipulation by navigating to a URL or opening the exchange. Automatic switching may not close the context tab 702. If the exchange is automatically changed when navigation leaves to another part of the navigation panel 710, the context tab 702 of one part may not close when the second part is opened, even in the event of a page anomaly, and the exchange may automatically switch to the communicator center. When the administrative user returns to the first part and the exchange automatically switches to the previously selected target communicator, the previous context tab 702 may still be relevant.

[0107] If the browser window is too small to display all core tags 701 and context tags 702 in a section, the core tags 701 can be collapsed into overflow mode, but in many embodiments, the context tags 702 are not collapsed. In extreme scenarios, all core tags 701 can be collapsed, and the context tags 702 can force the page frame to scroll horizontally. In some embodiments, the action bar options associated with a context tag can be different from the action bar options of its parent, child, or sibling tags. The context tag name can be a link. Users can click the link to copy it or open it in a new browser window or tab.

[0108] like Figure 8 As shown, in-tab navigation allows administrators to cycle through pages without opening multiple tabs. Administrators can use horizontal navigation buttons 801, such as "Next" and "Previous" within the tab, to navigate horizontally through related pages instead of opening multiple tabs.

[0109] In some embodiments, label 112 may appear on the button. Label 112 can be added to the button to alert the managing user to a label or action requiring attention based on contextual parameters. These labels may include “New” for new features, “Beta” for Beta features, and “AI” for buttons associated with AI-based recommendations. The AI ​​recommendation is based on, for example... Figure 1 The data analysis of audience behavior is shown, and recommendations aimed at optimizing campaigns and improving performance are provided using data fluctuations over time and user-guided activity adjustments.

[0110] like Figure 9As shown, in some embodiments, the action bar can be expanded and collapsed using a minimized V-shaped marker 901. The action bar can be collapsed when not needed, so the administrator user can view the expanded page without being distracted. In some embodiments, if the administrator user collapses the action bar, the action bar may remain collapsed while the administrator user switches pages during the duration of the administrator user's session. When the administrator user starts a new session, the action bar may return to its expanded default state. In some embodiments, pinned buttons are never collapsed. If there is not enough space to display all buttons even after collapsing button groups, button groups and individual buttons may be collapsed into an overflow "More" dropdown button in reverse order. Individual buttons may be collapsed into menu items. Button groups may be flattened into menu items with a button group label identifying the group.

[0111] In some embodiments, each feature and system action supported by the page has a corresponding button in the action bar. For example, action bar buttons can initiate editing, launch an activity, open a mode, and navigate to a new page. Buttons can also mark the target communicator selected in the exchange interface as liked or disliked. The interface can display visual feedback on whether the target communicator is liked.

[0112] In some embodiments, actions can initiate discrete, centralized experiences. Instead of initiating a sequence of dialog boxes that guides the user through a well-defined series of steps or a “wizard,” they can initiate an experience that may be a small part of the wizard, including a limited number of steps. In some edge-case scenarios, inline page elements can be used to initiate patterns and features. Examples may include inline searches of tables, changing table filters, or opening detailed patterns of visualizations that can modify predictions.

[0113] In some embodiments, the order, grouping, and size of the action bar buttons are intentional. Buttons that work together can be grouped together. More important buttons can be larger. More important buttons (based on usage frequency or how many should be activated) can be placed closer to one side of the action bar.

[0114] In various possible implementations, the button state can be active, hovered, pressed, or disabled. A disabled button may appear active but displays a disabled message when clicked, indicating what the administrator must do to make the button active. Button types can include simple buttons, toggles, and dropdowns. Button sizes can be large and small. In some embodiments, buttons can be pinned to the right side of the action bar. These buttons can include state toggles, behavior logs, inventory pins, and scheduled pins. Buttons can include images, labels, tooltips, and actions.

[0115] In some embodiments, each page may have no more than one action bar. In other embodiments, the action bar may be always visible as part of the sticky platform header. In some embodiments, unless otherwise specified, actions to initiate editing, open a context tab, or open a modal are initiated via the action bar.

[0116] In some embodiments, each page announces all its available buttons to the action bar upon page load. In this embodiment, the button list should not expand or shrink to manage user interaction with page content. All features are visible through the action bar. Movement between pages refreshes the action bar using the buttons associated with that page.

[0117] In other embodiments, the action bar only displays buttons associated with the administrator user's permissions, while other buttons are hidden. Action bar buttons may also be subject to the administrator user's role and permissions. Read-only pages may not have an action bar. Invalid buttons may remain invalid until content is selected.

[0118] In another embodiment, the action bar is completely hidden for the administrator user if all action bar buttons and groups are hidden. This may occur in scenarios where the administrator user only has read-only permissions. If all buttons in a button group are hidden, the button group is also hidden.

[0119] In some embodiments, if a simple button or toggle is associated with AI-based recommendations, it can be transformed into a dropdown button. The dropdown lists menu items describing the AI ​​recommendations, followed by menu items representing the original function of the launch button. The menu button with AI recommendations may have items added at the top of the menu describing the AI ​​recommendations. Clicking the AI ​​recommendations menu item opens the AI ​​modality, where the recommendations can be understood and applied.

[0120] toolkit

[0121] The toolkit allows administrators to navigate horizontally seamlessly and perform the same tasks for different clients. Figures 10-20 The toolkit is shown on the right side of the interface, but this is by no means a restriction on the toolkit's location. The toolkit can be placed anywhere.

[0122] like Figure 10As shown, in some embodiments, the toolkit 1000 may include a creative toolkit 1010, which provides an organized and navigable overview of a creative library containing creative assets of a target communicator. These creative assets include components of the target communication, including but not limited to images, text, and other media. Without having to navigate to multiple pages, the managing user can see an overview of the status of the target communicator's creative assets and interact with the assets via action buttons in the toolkit 1000. The main user interface, including a navigation panel 710 and comprising an exchange 300 and an action bar 500, remains visible while the toolkit 1000 is running. In some embodiments, the managing user can view information for multiple target communicators in the toolkit 1000 without navigating away from the current target communicator on the main page. In some embodiments, the toolkit 1000 is disconnected from the main user interface, allowing the managing user to multitask and / or monitor the toolkit 1000 information for one target communicator while simultaneously engaging in activities for another target communicator. For example, Figure 10 The exchange setup for the main user interface, designated "Target Communicator 3," is shown, where user guidance and situation-related smart categories 111, optimization tracks 1020, and orientation tracks 1030 all point to information for Target Communicator 3. Optimization track 1020 includes data analytics information for Target Communicator 3, such as "Recommendations," "Behaviors," "Bidding Snapshots," and "Targets." Orientation track 1030 includes information for Target Communicator 3, such as "Environment," "Audience," "Creativity," and "Device Type." In contrast, the Creativity Kit 1010 points to Target Communicator 2.

[0123] like Figure 11 As shown, in some embodiments of the toolkit 1000, the information panel 113 allows management users to identify problems and prioritize workflows. These alerts provide details such as the alert date 1101, the creative asset name 1102, and an explanation 1103 for why the alert was issued. In the case of the creative toolkit 1010, the information panel 113 allows management users to identify incomplete creative assets. Alerts not only allow management users to quickly identify problems but also provide a simple and easy-to-read problem overview, enabling management users to quickly assess the situation and manage workflows accordingly.

[0124] like Figure 12As shown, in some embodiments, toolkit 1000 may include alarm and notification toolkit 1200, which can provide recommendations for improving the scale or performance of an activity. In some embodiments, alarms and notifications may be distributed across the relevant platform. In some embodiments, alarms and notifications may be triggered by events. In some embodiments, alarms and notifications may be calculated in batches. In some embodiments, the alarm and notification toolkit provides this additional information tailored to the currently selected target communicator, the currently selected hub, or anything the user can access. Similar to Figure 10 The main user interface, including the action bar 500, along with the navigation panel 710, can be visible. Similarly, Figure 10 As shown, in some embodiments, an administrator can view information about multiple target communicators in the toolkit 1000 without navigating away from the information on the main page.

[0125] like Figure 13 As shown, in some embodiments, toolkit 1000 may include account health toolkit 1300, which provides insights into the overall health of target communications at the target communicator or hub level. In some embodiments, the account health toolkit provides information on how target communications and activities perform aggregatedly compared to historical and expected performance. In some embodiments, the account health toolkit may provide recommendations that positively impact performance. In some embodiments, the account health toolkit provides this additional information tailored to the currently selected target communicator or hub. Figure 12 As shown, the main user interface, including the action bar 500, along with the navigation panel 710, can be visible. Similarly, as... Figure 12 As shown, in some embodiments, an administrator user can view information about multiple target communicators in the toolkit 1000 without navigating out of the main page, as shown in the main user interface pointing to target communicator 3, while the account health toolkit 1300 points to target communicator 2.

[0126] like Figure 14 As shown, in some embodiments, toolkit 1000 may include site / application toolkit 1400, which provides the user with a list of websites and applications on which an activity should or should not run. In some embodiments, the site / application toolkit highlights a list of frequently used and currently used websites and applications and provides context about how these lists affect activity performance. In some embodiments, the site / application toolkit highlights a list of websites and applications that can improve activity performance. In some embodiments, the site / application toolkit allows the user to drag and drop a list of websites and applications into a new or existing activity to quickly add the list to the activity orientation track. In some embodiments, the site / application toolkit provides this additional information tailored to the currently selected target communicator or the currently selected hub. Figure 10 As shown, in some embodiments, an administrator user can view information about multiple target communicators in the toolkit 1000 without navigating away from the current target communicator on the main page. Similarly, as... Figure 10 As shown, the toolkit 1000 can be disconnected from the main user interface, allowing the managing user to multitask and / or monitor the toolkit 1000 information of one target communicator while simultaneously engaging in the activities of another target communicator. For example, Figure 10 The exchange setup, configured as "Target Communicator 3," is shown, where user guidance and situation-related smart categories 111, optimization tracks 1020, and direction tracks 1030 all point to information for Target Communicator 3. Optimization track 1020 includes data analytics information for Target Communicator 3, such as "Recommendations," "Behaviors," "Bidding Snapshots," and "Targets." Direction track 1030 includes information for Target Communicator 3, such as "Environment," "Audience," "Creativity," and "Device Type." In contrast, site / application toolkit 1400 points to Target Communicator 2.

[0127] like Figure 15 As shown, in some embodiments, toolkit 1000 may include location toolkit 1500, which provides the user with a list of geographic locations in which an activity should or should not run. In some embodiments, the location toolkit highlights a list of frequently used and currently used locations and provides context about how these lists affect activity performance. In some embodiments, the location toolkit highlights geographic locations that can improve activity performance. In some embodiments, the location toolkit allows the user to drag and drop a list of geographic locations into a new or existing activity to quickly add the list to the activity orientation track. In some embodiments, the location toolkit provides this additional information tailored to the currently selected target communicator or the currently selected center. Figure 10 As shown, in some embodiments, an administrator user can view information about multiple target communicators in the toolkit 1000 without navigating away from the current target communicator on the main page. Similarly, as... Figure 10 As shown, the toolkit 1000 can be disconnected from the main user interface, allowing the managing user to multitask and / or monitor the toolkit 1000 information of one target communicator while simultaneously engaging in the activities of another target communicator. For example, Figure 10The exchange setup, configured as "Target Communicator 3," is shown, where user guidance and situation-related smart categories 111, optimization track 1020, and orientation track 1030 all point to information for Target Communicator 3. Optimization track 1020 includes data analytics information for Target Communicator 3, such as "Recommendations," "Behaviors," "Bidding Snapshots," and "Targets." Orientation track 1030 includes information for Target Communicator 3, such as "Environment," "Audience," "Creativity," and "Device Type." In contrast, location toolkit 1500 points to Target Communicator 2.

[0128] like Figure 16 As shown, in some embodiments, toolkit 1000 may include toolkit 1600, which allows administrative users to adjust user and account settings. In some embodiments, the toolkit allows access to administrative, authorized user, and internal user characteristics, such as user management, billing, internal testing tools, and dashboards. In some embodiments, the toolkit provides this additional information tailored to the currently selected target communicator or the currently selected hub. Figure 10 As shown, in some embodiments, an administrator user can view information in the toolkit 1000 without navigating away from the current target communicator information on the main page. Similarly, as... Figure 10 As shown, the toolkit 1000 can be disconnected from the main user interface, allowing the managing user to multitask and / or monitor the toolkit 1000 information while simultaneously engaging in activities with selected target communicators. For example, Figure 10 The exchange setup, configured as "Target Communicator 3," is shown, where user guidance and situation-related intelligent categories 111, optimization tracks 1020, and direction tracks 1030 all point to information about Target Communicator 3. Optimization track 1020 includes data analytics information about Target Communicator 3, such as "Recommendations," "Behaviors," "Bidding Snapshots," and "Targets." Direction track 1030 includes information about Target Communicator 3, such as "Environment," "Audience," "Creativity," and "Device Type." In contrast, the toolkit 1600 provides a general set of tools.

[0129] like Figure 17 As shown, in some embodiments, toolkit 1000 may include profile toolkit 1700, which allows administrators to populate accounts using information about the user and the user's image. In some embodiments, the profile toolkit displays profile information. In some embodiments, the profile toolkit provides shortcuts for password and security management. In some embodiments, the profile toolkit displays a list of tasks. In some embodiments, the profile toolkit provides additional information customized for the currently logged-in user. Figure 10As shown, in some embodiments, an administrator user can view information in the toolkit 1000 without navigating away from the current target communicator information on the main page. Similarly, as... Figure 10 As shown, the toolkit 1000 can be disconnected from the main user interface, allowing the managing user to multitask and / or monitor the toolkit 1000 information while simultaneously engaging in activities with selected target communicators. For example, Figure 10 The exchange setup for the main user interface, designated "Target Communicator 3," is shown, where user guidance and situation-related smart categories 111, optimization track 1020, and direction track 1030 all point to information for Target Communicator 3. Optimization track 1020 includes data analytics information for Target Communicator 3, such as "Recommendations," "Behaviors," "Bidding Snapshots," and "Targets." Direction track 1030 includes information for Target Communicator 3, such as "Environment," "Audience," "Creativity," and "Device Type." In contrast, the profile toolkit 1700 provides information and tools for managing users' personal information.

[0130] like Figure 18 As shown, in some embodiments, the toolkit includes a mini-switch 1801 that displays information about which target communicator is filling the panel. The mini-switch allows switching which target communicator's information is being displayed without requiring the rest of the browser to navigate away from the current target communicator. It displays the target communicator of the currently selected communicator center in the header switch. Alternatively, the header target communicator can be selected by default in the mini-switch. Whenever the header switch is changed, the mini-switch can change to follow. If the header switch is changed to a communicator center-level selection, the mini-switch can select the administrator user's first favorite target communicator. If the administrator user does not have a favorite target communicator, the first target communicator in the "All Target Communicators" list can be selected. If there is no target communicator in the communicator center, the mini-switch can be inactive and display a "No target communicator found" watermark. Alternatively, the entire creative panel can be blank and display a "Please create a target communicator to display its creative content here" watermark. "Create Target Communicator" is a link to the target communicator creation stream. This link can be valid to manage users with target communicator creation permissions.

[0131] like Figure 19 As shown, in some embodiments, toolkit 1000 may include action button 1901. In the case of creative toolkit 1010, action button 1901 may include "Upload Creative" and "Batch Upload" buttons. These buttons may be available if the managing user has creative editing permissions for target communicators in the miniswitch. The Upload Creative button opens an "Add Creative" popup from the creative library. The Batch Upload button opens a "Batch Import" popup from the creative library.

[0132] like Figure 20 As shown, in some embodiments, tokens 2001 may be visible when toolkit 1000 is not actively used. These tokens 2001 may have symbols representing various toolkit options. Like toolkit 1000, tokens 2001 are not limited to the left side of the interface but can exist anywhere.

[0133] This disclosure provides several important technical advantages that will be apparent to those skilled in the art from the accompanying drawings, specification, and claims. Furthermore, while specific advantages have been listed above, various embodiments may include all, some, or none of the listed advantages. Any statement or representation in this disclosure may be associated with one or more embodiments. References to “one embodiment” or “embodiment” in the specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of this disclosure. The phrases “in one embodiment” or “in some embodiments” appearing in various parts of the specification do not necessarily all refer to the same implementation or embodiment.

[0134] Furthermore, the above description of embodiments of this disclosure is for illustrative and descriptive purposes only. It is not intended to be exhaustive or to limit this disclosure to the precise form disclosed. Many modifications and variations are possible in accordance with the foregoing teachings. As will be understood by those skilled in the art, this disclosure may be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, this disclosure is intended to illustrate, not limit, its scope.

Claims

1. A method for bypassing a data hierarchy when providing data associated with an object, the method comprising: Use one or more computing device processors to provide the main object collection; The processor of the one or more computing devices receives a selection of a first object from the set of main objects; In response to receiving a selection of the first object in the primary object set, the one or more computing device processors provide a secondary object set based on the selection of the first object in the primary object set, wherein the secondary object set includes a set of target communicators, communications, or activities; The processor of the one or more computing devices receives a selection of a second object from the set of auxiliary objects; In response to receiving a selection of the second object from the set of auxiliary objects, the one or more computing device processors are used to provide first data associated with the second object, wherein the first data associated with the second object includes a first data hierarchy associated with the second object; The processor of the one or more computing devices receives a selection of a first category from the first data associated with the second object; In response to receiving a selection of the first category in the first data associated with the second object, the one or more computing device processors are used to provide the first category data associated with the second object; The processor of the one or more computing devices receives a selection of a third object from the set of auxiliary objects; and In response to receiving a selection of the third object in the set of auxiliary objects, the one or more computing device processors are used to bypass the second data level associated with the third object, and the one or more computing device processors are used to provide first category data associated with the third object without providing data associated with the third object and without receiving a selection of the first category associated with the third object, wherein the first category data associated with the second object and the first category data associated with the third object are available for the second object and the third object, respectively.

2. The method according to claim 1, further comprising: A set of selectable categories is provided based on the user's profile and based on the selection of the first object in the set of primary objects or the selection of the second object in the set of secondary objects.

3. The method according to claim 2, wherein, The set of selectable categories is based on the history of categories selected by the user.

4. The method of claim 2, further comprising filtering objects based on a first selected category in the set of selectable categories.

5. The method according to claim 2, wherein, The selectable category set is included in the first category associated with the second object or the first category associated with the third object, or includes the first category associated with the second object or the first category associated with the third object.

6. The method according to claim 1, wherein, The data associated with the first object, the first category data associated with the first object, the first data associated with the second object, or the first category data associated with the second object are based on the user's profile or history.

7. The method according to claim 1, wherein, The main object set, the auxiliary object set, and the category set associated with the auxiliary object set are respectively located in the first selection pane, the second selection pane, and the third selection pane.

8. The method of claim 1, further comprising switching the visual representation of the second object from a first state to a second state in response to the selection of the second object.

9. The method according to claim 8, wherein, When the first category associated with the third object is provided without providing the data associated with the third object and without receiving a selection of the first category associated with the third object, the visual representation of the second object remains in the second state.

10. The method of claim 1, further comprising providing an exception upon receiving a selection of data that is not allowed to be accessed by the user.

11. The method of claim 1, further comprising providing a tag for at least one of the first object, data associated with the first object, the second object, or the first data associated with the second object, wherein, The marker provides the user with messages about the status.

12. The method of claim 1, further comprising searching at least one of the first object, data associated with the first object, the second object, or the first data associated with the second object.

13. The method of claim 1, further comprising storing a workflow associated with at least one of: the first object, data associated with the first object, the second object, or the first data associated with the second object.

14. The method according to claim 1, wherein, The main object set includes the communicator center set.

15. An apparatus for bypassing a data hierarchy when providing data associated with an object, the apparatus comprising one or more computing device processors configured to: Provide a collection of main objects, where, The main object set includes the communicator center set; Receive the selection of the first object in the set of main objects; In response to receiving a selection of the first object in the main object set, a secondary object set is provided based on the selection of the first object in the main object set; Receive a selection of a second object from the set of auxiliary objects; In response to receiving a selection of the second object from the set of auxiliary objects, first data associated with the second object is provided; Receive a selection of a first category in the first data associated with the second object, wherein the first data associated with the second object includes a first data hierarchy associated with the second object; In response to receiving a selection of the first category in the first data associated with the second object, first category data associated with the second object is provided; Receive selection of a third object from the set of auxiliary objects; and In response to receiving a selection of the third object in the set of auxiliary objects, the second data level associated with the third object is bypassed, and first category data associated with the third object is provided without providing data associated with the third object and without receiving a selection of the first category associated with the third object, wherein the first category data associated with the second object and the first category data associated with the third object are respectively available for the second object and the third object.

16. The apparatus according to claim 15, wherein, The device includes at least one of a server or computing device associated with a user.

17. A method for bypassing a data hierarchy when providing data associated with an object, the method comprising: Use one or more computing device processors to provide the main object collection; The processor of the one or more computing devices receives a selection of a first object from the set of main objects; In response to receiving a selection of the first object in the main object set, the one or more computing device processors provide a secondary object set based on the selection of the first object in the main object set; The processor of the one or more computing devices receives a selection of a second object from the set of auxiliary objects; In response to receiving a selection of the second object from the set of auxiliary objects, the one or more computing device processors are used to provide first data associated with the second object, wherein the first data associated with the second object includes a first data hierarchy associated with the second object; The processor of the one or more computing devices receives a selection of a first category from the first data associated with the second object; In response to receiving a selection of the first category in the first data associated with the second object, the one or more computing device processors are used to provide the first category data associated with the second object; The processor of the one or more computing devices receives a selection of a third object from the set of auxiliary objects; and In response to receiving a selection of the third object in the set of auxiliary objects, the one or more computing device processors are used to bypass the second data level associated with the third object, and the one or more computing device processors are used to provide first category data associated with the third object without providing data associated with the third object and without receiving a selection of the first category associated with the third object, wherein the first category data associated with the second object and the first category data associated with the third object are available for the second object and the third object, respectively.

18. The method according to claim 17, wherein, The second object and the third object are part of an object hierarchy associated with the first object.

19. The method of claim 18, further comprising bypassing the object hierarchy associated with the first object.

20. The method of claim 17, wherein, The data associated with the third object includes the first category associated with the third object.

Images