UNIVERSAL TAG FOR PAGE ANALYTICS AND CAMPAIGN CREATION

• US 20140282036A1
• Filed: 06/21/2013
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Abandoned Application

• Current Assignee: Turn (Nexxen International Ltd.)
• Original Assignee: Turn (Nexxen International Ltd.)
• Inventors: SHOTTAN, Jonathan, SHAH, Vishal, GILL, Kevinjeet
• Application Number:
  US13/924,286
• Publication Number:
  US 20140282036A1
• Time in Patent Office: Days
• US Class Current: 715/738
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/0486 Drag-and-drop
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/14 Tree-structured documents parsing G06F40/205; validation G06F40/226
• CPC Class Codes: G06N 5/02 Knowledge representation; Symbolic representation
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 30/0269 based on user profile or attribute
• CPC Class Codes: G06Q 30/0277 Online advertisement

Abstract

A system for creating and using a universal tag to gather consumer data from a website for the purposes of targeted advertising is provided. The universal tag system has two main subsystems. The first subsystem is a configuration system that is used to define the consumer data to be collected from the website and to define taxonomy and transformation rules to be applied to the collected consumer data. The second subsystem is a runtime system that runs a universal tag client-side script, which is triggered when a consumer lands on a webpage of the website, for collecting the defined consumer data. The runtime system then applies the transformation rules to the collected data and updates a user profile corresponding to the consumer with the transformed data. As well, the runtime system applies the taxonomy rules to the collected data and categorizes the consumer for the purposes of subsequent targeted advertising.

Claims

1. A computer implemented method for creating a universal tag collection using a graphical user interface, comprising:

a processor performing the following on the graphical user interface;

selecting a data provider with universal tag availability;

responsive to selecting the data provider, validating allowed domain names corresponding to the data provider;

responsive to selecting the domain names, deciding to use an event inspector tool or to enter event data definitions manually;

responsive to deciding to enter event data manually, entering the event data definitions and designating type and attribute of each event;

responsive to deciding to use the event inspector tool, performing the following;

dragging and dropping an event bookmarklet onto a bookmark bar of a particular website;

entering a URL which launches a first page of the website for event capture;

responsive to the first page loading, selecting the bookmarklet on the bookmark bar;

responsive to selecting the bookmarklet, displaying an event inspector panel;

displaying, by the event inspector panel, any previously captured events in a corresponding data provider tab;

adding new events interactively or by searching;

responsive to adding the new events, navigating to and loading a new page of the website and repeating the process iteratively by starting from selecting the bookmarklet on the bookmark bar;

deciding no new events need to be added;

responsive to deciding no new events need to be added for the website, deciding if new events for a different website need to be added and, if yes, then repeating the process iteratively by starting from entering a URL which launches a first page of the different website for event capture; and

deciding no new events need to be added for the different website.

2. The method of claim 1, wherein the allowed domain names are allowed for reasons of security.

3. The method of claim 1, wherein a name and notes for a particular universal tag are displayed.

4. The method of claim 1, wherein a data provider configuration page is displayed and refreshed with captured events.

5. An apparatus for creating a universal tag collection using a graphical user interface, comprising:

a graphical user interface for performing the following by using at least one processor coupled to a memory;

selecting a data provider with universal tag availability;

responsive to selecting the data provider, selecting allowed domain names corresponding to the data provider;

responsive to selecting the domain names, deciding to use an event inspector tool or to enter event data definitions manually;

responsive to deciding to enter event data manually, entering the event data definitions and designating type and attribute of each event;

responsive to deciding to use the event inspector tool, performing the following;

dragging and dropping an event bookmarklet onto a bookmark bar of a particular website;

entering a URL which launches a first page of the website for event capture;

responsive to the first page loading, selecting the bookmarklet on the bookmark bar;

responsive to selecting the bookmarklet, displaying an event inspector panel;

displaying, by the event inspector panel, any previously captured events in a corresponding data provider tab;

adding new events interactively or by searching;

responsive to adding the new events, navigating to and loading a new page of the website and repeating the process iteratively by starting from selecting the bookmarklet on the bookmark bar;

deciding no new events need to be added;

responsive to deciding no new events need to be added for the website, deciding if new events for a different website need to be added and, if yes, then repeating the process iteratively by starting from entering a URL which launches a first page of the different website for event capture; and

responsive to deciding no new events need to be added for the different website, exiting the graphical user interface.

6. The apparatus of claim 5, wherein the allowed domain names are allowed for reasons of security.

7. The apparatus of claim 5, wherein a name and notes for a particular universal tag are entered.

8. The apparatus of claim 5, wherein a data provider configuration page is displayed and refreshed with captured events.