Method and system of publishing campaign data

• US 20080097928A1
• Filed: 10/19/2006
• Published: 04/24/2008
• Est. Priority Date: 10/19/2006
• Status: Active Grant

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Paulson, Jedediah H.
• Granted Patent: US 8,892,756 B2
• Time in Patent Office: Days
• US Class Current: 705/80
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates
• CPC Class Codes: G06Q 30/0211 Determining the effectiveness of discounts or incentives
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0251 Targeted advertisements
• CPC Class Codes: G06Q 30/0272 Period of advertisement exposure
• CPC Class Codes: G06Q 50/188 Electronic negotiation
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

One embodiment of the invention provides a method of publishing campaign metadata from a database to a plurality of channel systems, the method includes: querying the database to select campaign metadata ready for publishing to a target channel system; selecting the target channel system from a plurality of channel systems based on an target indicating attribute of the campaign metadata; determining whether the target channel system has a SOAP enabled webservice API or whether the target channel system only accepts HTTP posts; if the target channel system has a SOAP enabled webservice API, packaging the campaign metadata as an XML message object; if the target channel system only accepts HTTP posts, packaging the campaign metadata as an HTML request; and transferring the packaged campaign metadata to the target channel system.

Claims

1. A method, comprising:

querying a database to select campaign metadata ready for publishing to a target channel system;

selecting the target channel system from a plurality of channel systems based on a target indicating attribute of the campaign metadata;

determining whether the target channel system has a SOAP enabled webservice API or whether the target channel system only accepts HTTP posts;

if the target channel system has a SOAP enabled webservice API, packaging the campaign metadata as an XML message object;

if the target channel system only accepts HTTP posts, packaging the campaign metadata as an HTML request; and

transferring the packaged campaign metadata to the target channel system.

2. The method of claim 1, further comprising, after querying the database, aggregating one or more offer metadata with the selected campaign metadata.

3. A computer-readable medium including instructions that, when performed by a computer in a campaign publishing system, cause the computer to:

query a database to select all campaign metadata ready for publishing to a target channel system;

select the target channel system from a plurality of channel systems based on a target indicating attribute of the campaign metadata;

determine whether the target channel system has a SOAP enabled webservice API or whether the target channel system only accepts HTTP posts;

if the target channel system has a SOAP enabled webservice API, package the campaign metadata as an XML message object;

if the target channel system only accepts HTTP posts, package the campaign metadata as an HTML request; and

transfer the packaged campaign metadata to the target channel system.

4. The computer-readable medium of claim 3, further comprising instructions that cause the computer, after querying the database, to aggregate one or more offer metadata with the selected campaign metadata.

5. The computer-readable medium of claim 3, further comprising instructions that cause the computer, after transferring campaign metadata successfully, to update the status of transferred campaign metadata in the database to identify that the campaign metadata has been transferred successfully.

6. A method, comprising:

querying a database to get a user list associated to a campaign, the campaign has campaign metadata indicating a target channel system;

selecting the target channel system from a plurality of channel systems based on the campaign metadata;

determining whether or not the target channel system has a SOAP enabled webservice API; and

if yes, packaging the user list as an XML file, validating the XML file, and transferring the packaged user list to the target channel system;

if not, writing the user list to a flat file, validating the flat file, validating the associated campaign metadata, and transferring the user list by copying the flat file to the target channel system.

7. The method of claim 6, wherein after transferring the user list to the target channel system, writing the user list to a contact history table.

8. The method of claim 6, wherein validating the flat file comprises, if finding that the flat file empty, aborting the publishing process and sending an email alert to a system administrator.

9. The method of claim 6, wherein validating the flat file comprises, if finding that the flat file does not contain a required field for the targeted channel system, aborting the publishing process and sending an email alert to a system administrator.

10. The method of claim 6, wherein validating the metadata of the associated campaign comprises, if finding that the metadata of the flat file and the metadata of the associated campaign do not match, aborting the publishing process and sending an email alert to a system administrator.

11. A computer-readable medium including instructions that, when performed by a computer, cause the computer to:

query a database to get a user list associated to a campaign, the campaign has campaign metadata indicating a target channel system;

select the target channel system from a plurality of channel systems based on the campaign metadata;

determine whether or not the target channel system has a SOAP enabled webservice API;

if yes, write the user list to an XML file, validate the XML file, and transfer the packaged user list to the target channel system;

if not, write the user list to a flat file, validate the flat file, validate the associated campaign metadata, and transfer the user list by copying the flat file to the target channel system.

12. The computer-readable medium of claim 11, further comprising instructions that cause the computer, after transferring the user list to the target channel system, to write the user list to a contact history table.

13. The computer-readable medium of claim 11, further comprising instructions that cause the computer, when validating the flat file, if finding that the flat file empty, to aborting the publishing process and send an email alert to a system administrator.

14. The computer-readable medium of claim 11, further comprising instructions that cause the computer, when validating the flat file, if finding that the flat file does not contain a required field for the targeted channel system, to abort the publishing process and sending an email alert to a system administrator.

15. The computer-readable medium of claim 11, further comprising instructions that cause the computer, when validating the flat file, if finding that the metadata of the flat file and the metadata of the associated campaign do not match, to abort the publishing process and send an email alert to a system administrator.

16. A network-based system, comprising:

a database to store a campaign metadata which has an attribute indicating a target channel system from a plurality of channel systems; and

a processor to read from and write to the database, deliver the campaign metadata to the target channel system, and determine the target channel system before delivering the campaign metadata,

wherein the processor also packages the campaign metadata as an XML message object if the target channel system has a SOAP enabled webservice API, otherwise, the processor packages the campaign metadata as an HTML request if the target channel system only accepts HTTP posts.

17. A network-based system, comprising:

database to store a user list and metadata of an associated campaign; and

a processor to select the target channel system from a plurality of channel systems based on the campaign metadata, determine whether or not the target channel system has a SOAP enabled webservice API, if yes, package the user list as an XML file, validate the XML file, and transfer the packaged user list to the target channel system, if not, write the user list to a flat file, validate the flat file, validate the associated campaign metadata, and transfer the user list by copying the flat file to the target channel system,

wherein the processor, if any invalidation found, the processor aborts the process of publishing and sends an email alert to a system administrator.