Browse Prior Art Database

A Method and System for Determining a View Search Conversion

IP.com Disclosure Number: IPCOM000236457D
Publication Date: 2014-Apr-29
Document File: 4 page(s) / 175K

Publishing Venue

The IP.com Prior Art Database

Related People

Visagan Vaithyanathan: INVENTOR

Abstract

A method and system is disclosed for performing a view search conversion. The method and system utilizes user actions, user ID and a device ID for determining the view search conversion.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 51% of the total text.

A Method and System for Determining a View Search Conversion

Abstract

A method and system is disclosed for performing a view search conversion.  The method and system utilizes user actions, user ID and a device ID for determining the view search conversion.

Description

Disclosed is a method and system for performing a view search conversion.

The method and system enables a consumer device to be recognized by a device Unique Identification (UID).  Here every consumer includes a unique ID and an application installed on respective consumer devices utilizes the UID.  In addition, communication with advertisement (ad) servers is performed using the UID.  The method and system caches user login information either locally or remotely in servers for each device.

The method and system serves advertisements to the consumer devices based on user information and records the URLs served.  In addition, the method and system captures feedback from the user devices based on clicks, conversions and feedback of Uniform Resource Locator (URLs) served to the user devices and user information.  Thereafter, the processed information is sent to the backend system.

The user information is retrieved based on user login information and user login history of the respective devices.  A map is then created between a user and all his associated devices.  A user uses one of a smart phone, a TV, a tablet and a smart phone to provide the login information.

For instance, an advertisement displayed on the TV is cached and fed back to the ad server.  Thereafter, the advertisement is processed by the back end system.  The backend system stores the user and device information for each advertisement delivered.  The top user searches and clicks to the URL’s are cached in any device searched by the user, such as, mobile, tablet, desktop and laptop.  At regular intervals the cached copy of the URL is fed back to the backend system.  Thereafter, a mapping and a join operation is performed by the backend system based on a time stamp of displaying the advertisement, device UID, user ID, an advertisement URL, search URL or keywords and network information.  Here, the time stamp parameter is searched with a threshold, as the user does not search for the advertisement at the same instant the advertisement is displayed.

A response is fed back to the ad server depending on a user’s frequent usage of the device, whenever there is an intersection between the above two caches based on time stamp and URL and domain match.

For instance, the data returned from the device when a match is determined is given as,

{

feedback_from_device:

{

time-­‐stamp:

deviceID:

user ID:[]

AdURL:

adIdentifier:

location:

network-­‐info:{

IP-­‐address-­‐Device:

MAC-­‐Address-­‐Router:

}

search_info:{

KeyWords:[]

DomainList:[]

URL_List:[]

}

}

}

where, [] represents the data that is fed for that key is an array, userID:[] represents a single user or multiple users.  For example, sing...