SYSTEM AND METHOD FOR MANAGING ADVERTISING CAMPAIGN DATA

• US 20120095847A1
• Filed: 12/19/2011
• Published: 04/19/2012
• Est. Priority Date: 07/15/2004
• Status: Abandoned Application

• Current Assignee: Adobe Systems Incorporated (Adobe Inc.), Google Inc. (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Wolkoff, Steven, Sinaniyev, Vladislav, Suljoti, Dritan, Grossman, Gary Steven, Johnson, Suzanne Mattis, Drieu, Gilles
• Application Number:
  US13/329,944
• Publication Number:
  US 20120095847A1
• Time in Patent Office: Days
• US Class Current: 705/14.73
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0276 Advertisement creation
• CPC Class Codes: G06Q 30/0277 Online advertisement

Abstract

A method and system for managing ad campaign data. According to one embodiment, an application receives a request to store data associated with an ad campaign, and responsive to the request, stores one or more output files and context information associated with the data, the context information assembled according to a pre-defined data format defining a role of the data within the ad campaign.

Claims

1-23. -23. (canceled)

24. A computer-implemented method for managing ad campaign data, comprising:

receiving, by at least one processor, a request to store data associated with an ad campaign;

obtaining, by at least one processor, context information based on information received in the request, the context information including information regarding an ad type;

validating, by at least one processor and based on the information regarding the ad type, the context information when the context information is sufficient to define a valid ad campaign of a type associated with the ad type; and

responsive to the request, storing, by at least one processor, one or more output files and the validated context information associated with the data in a package file.

25. The method of claim 24, wherein the request is received through a graphical user interface of an authoring tool.

26. The method of claim 25, wherein the data associated with the ad campaign corresponds to a creative.

27. The method of claim 26, wherein the authoring tool is a software application for generating the creative.

28. The method of claim 27, wherein the one or more output files include an asset file associated with the creative generated by the authoring tool.

29. The method of claim 28, wherein the asset file is one of an audio file, video file and an image file.

30. The method of claim 28, wherein the asset file is a vector graphic animation file.

31. The method of claim 25, wherein the data associated with the ad campaign corresponds to a media plan.

32. The method of claim 25, wherein the authoring tool is a word processing application for generating the media plan.

33. The method of claim 32, wherein the one or more output files include a word processing file associated with the media plan generated by the authoring tool.

34. The method of claim 24, wherein the pre-defined data format is based on an extensible markup language schema.

35. The method of claim 24, wherein the context information is stored in an extensible markup language document.

36. The method of claim 24, wherein the context information is stored in one or more of the one or more output files.

37. The method of claim 24, wherein the context information is stored in an e-mail.

38. The method of claim 24, wherein the context information relates to the ad campaign associated with the data.

39. The method of claim 38, wherein the context information includes at least one of a campaign name, a campaign start time and a campaign end time.

40. The method of claim 24, wherein the context information relates to the data associated with the ad campaign.

41. The method of claim 40, wherein the context information includes at least one of output file name associated with a creative and type of creative.

42. The method of claim 40, wherein the context information includes at least one of an output file name associated with a media plan and media buy information.

43. The method of claim 24, further comprising determining whether additional context information is required based on validating the obtained context information, and obtaining supplemental context information if additional context information is necessary.

44. A machine-readable medium having stored thereon a plurality of executable instructions for managing ad campaign data, the plurality of executable instructions causing a processor to:

receive a request to store data associated with an ad campaign;

obtain context information based on information received in the request, the context information including information regarding an ad type;

validate, based on the information regarding the ad type, the context information when the context information is sufficient to define a valid ad campaign of a type associated with the ad type; and

responsive to the request, store one or more output files and the validated context information associated with the data in a package file.

45. The machine-readable medium of claim 44, wherein the plurality of executable instructions further cause the processor to:

determine whether additional context information is required based on validating the obtained context information; and

obtain additional context information when additional context information is necessary.

46. A system for managing ad campaign data, comprising:

means for receiving a request to store data associated with an ad campaign;

means for obtaining context information based on information received in the request, the context information including information regarding an ad type;

a processor operable to determine whether the obtained context information is sufficient to define a valid ad campaign of a type associated with the ad type based on analysis of obtained context information;

means for obtaining additional context information when the obtained context information is not sufficient to define a valid ad campaign of the type associated with the ad type; and

means for storing, in response to the request and when the obtained context information is valid, one or more output files and the obtained context information associated with the data in a package file.