METHOD AND SYSTEM OF PUBLISHING CAMPAIGN DATA

• US 20150073898A1
• Filed: 11/17/2014
• Published: 03/12/2015
• Est. Priority Date: 10/19/2006
• Status: Active Grant

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Paulson, Jedediah H.
• Granted Patent: US 9,454,770 B2
• Time in Patent Office: Days
• US Class Current: 705/14.49
• 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. (canceled)

2. 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 target channel systems; and

a campaign module including at least one processor and configured to;

read from and write to the database;

deliver the campaign metadata to the target channel system;

determine whether the target channel system includes a protocol specification for exchanging structured information in a webservice API or that the target channel system only accepts HTTP requests before packaging the campaign metadata;

package the campaign metadata as structured information according to the protocol specification based on determining that the target channel system includes a protocol specification for exchanging structured information in a webservice API; and

transfer the packaged campaign metadata to the target channel system.

3. The system of claim 2, wherein the campaign module is further configured to:

based on determining that the target channel system only accepts HTTP requests, package campaign metadata as an HTTP “

post”

request; and

transfer the packaged campaign metadata to the target channel system.

4. The system of claim 3, wherein the campaign module is further configured to:

after querying the database, aggregate one or more offer metadata with the selected campaign metadata; and

after transferring campaign metadata successfully, update the status of transferred campaign metadata in the database to identify that the campaign metadata has been transferred successfully.

5. The system of claim 3, wherein the campaign metadata comprises a user list associated with a campaign and the campaign module is further configured to:

determine whether or not the target channel includes a protocol specification for exchanging structured information in a webservice API before packing the user list;

based on determining the target channel does include a protocol specification for exchanging structured information in a webservice API, package the user list as structured information according to the protocol specification and validating the packaged user list; and

transfer the packaged user list to the target channel system.

6. The system of claim 5, wherein the campaign module is further configured to:

based on determining that the target channel system does not include a protocol specification for exchanging structured information in a webservice API, writing the user list to a flat file;

validate the flat file and validate the associated campaign metadata; and

transfer the user list by copying the flat file to the target channel system.

7. The system 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.

8. The system 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.

9. A method, comprising:

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

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

determining, by the campaign system, whether the target channel system includes a protocol specification for exchanging structured information in a webservice Application Program Interface (API) or that the target channel system only accepts HyperText Transfer Protocol (HTTP) requests before packaging the campaign metadata;

based on determining that the target channel system includes a protocol specification for exchanging structured information in a webservice API, packaging, by the campaign system, the campaign metadata as structured information according to the protocol specification; and

transferring, by the campaign system, the packaged campaign metadata to the target channel system.

10. The method of claim 9, further comprising:

based on determining by the campaign system that the target channel system only accepts HTTP requests, packaging by the campaign system the campaign metadata as an HTTP “

post”

request; and

transferring by the campaign system the packaged campaign metadata to the target channel system.

11. The method of claim 10, further comprising, after querying the database, aggregating one or more offer metadata with the selected campaign metadata, and after transferring campaign metadata successfully, updating the status of transferred campaign metadata in the database to identify that the campaign metadata has been transferred successfully.

12. The method of claim 10, wherein the campaign metadata comprises a user list associated with a campaign, the method further comprising:

determining by the campaign system whether or not the target channel includes a protocol specification for exchanging structured information in a webservice API before packing by the campaign system the user list;

based on determining the target channel does include a protocol specification for exchanging structured information in a webservice API, packaging the user list as structured information according to the protocol specification and validating the packaged user list; and

transferring the packaged user list to the target channel system by the campaign system.

13. The method of claim 12, further comprising:

based on determining by the campaign system that the target channel system does not include a protocol specification for exchanging structured information in a webservice API, writing the user list to a flat file;

validating the flat file and validating the associated campaign metadata; and

transferring the user list by copying the flat file to the target channel system by the campaign system.

14. The method of claim 13, 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.

15. The method of claim 13, 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.

16. A non-transitory computer-readable medium including instructions that, when performed by a computer in a campaign publishing system, cause the system 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 target channel systems based on a target indicating attribute of the campaign metadata;

determine that the target channel system includes a protocol specification for exchanging structured information in a webservice API or that the target channel system only accepts HTTP requests before packaging the campaign metadata;

based on determining that the target channel system includes a protocol specification for exchanging structured information in a webservice API, package the campaign metadata as structured information according to the protocol specification; and

transfer the packaged campaign metadata to the target channel system.

17. The non-transitory computer-readable medium of claim 16, further comprising instructions that cause the system to:

based on determining that the target channel system only accepts HTTP requests, package the campaign metadata as an HTTP “

post”

request; and

transfer the packaged campaign metadata to the target channel system.

18. The non-transitory computer-readable medium of claim 17, wherein the campaign metadata comprises a user list associated with a campaign, further comprising instructions that cause the system to:

determine whether or not the target channel includes a protocol specification for exchanging structured information in a webservice API before packing by the campaign system the user list;

based on determining yes, package the user list as structured information according to the protocol specification, validate the packaged user list, and

transfer the packaged user list to the target channel system by the campaign system.

19. The non-transitory computer-readable medium of claim 18, further comprising instructions that cause the machine to:

based on determining that the target channel system does not include a protocol specification for exchanging structured information in a webservice API, write the user list to a flat file;

validate the flat file and validate the associated campaign metadata; and

transfer the user list by copying the flat file to the target channel system.

20. The non-transitory computer-readable medium of claim 19, further comprising instructions that cause the machine to, when validating the flat file, if finding that the flat file is empty, abort the publishing process and send an email alert to a system administrator.

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