8.18 Automate Campaign Bookings with a centralized server (OBS integration)
1. Purpose & Background
This page provides a general overview of the Online Booking System (OBS) and the purpose of our integration with it.
OBS is a German third-party system that provides a standardized communication channel for booking advertising campaigns between agencies and publishers. It is primarily used in the print media sector (e.g., magazines).
2. The Core Concept: How OBS Works
The OBS system standardizes the booking process through a defined sequence of messages. The workflow is always initiated by the agency and the publisher responds. This exchange consists of three main transaction types:
New Booking:
Agency sends an
Order.Publisher responds with an
Order Confirmation.
Modification:
Agency sends a
Change Requestto an existing booking (e.g., to change a publication date).Publisher responds with a
Change Confirmation.
Cancellation:
Agency sends a
Cancellation.Publisher responds with a
Cancellation Confirmation.
3. Overview: The ADvendio Integration Workflow
Our integration connects ADvendio to the publisher's OBS client, integrating the exchange of these messages into ADvendio.
Step 1: Receiving a Request from an Agency
Our Gateway periodically checks the publisher's OBS client for new incoming messages (e.g., an
Order).When a new message is detected together with the PDF related, the Gateway retrieves it and creates a new message record in ADvendio.
The system creates a Media Campaign Draft in ADvendio.
Note: Instead of automatically creating a full campaign, which proved too complex due to mapping challenges, the system creates a minimal draft with only essential information.
A human-readable PDF version of the request is automatically attached to this draft.
Step 2: Processing the Request in ADvendio
A sales representative (the ADvendio user) opens the Media Campaign Draft.
Using the attached PDF as a reference, the sales rep manually configures the full campaign details, adds the campaign items, and verifies availability. This includes details like pricing with discounts and commitments, publication dates, ad formats, and "copy shipping" addresses (contacts who receive a physical copy of the magazine as proof of publication).
Step 3: Sending a Confirmation Back to the Agency
Once the sales rep confirms the campaign in ADvendio, the system triggers the message to be sent back.
This message is sent to the publisher's OBS client, which then forwards it to the agency, completing the transaction.
This same fundamental process applies to Change and Cancellation requests, with the key difference being that those requests will be linked to existing Media Campaigns in ADvendio.
4. Additional Notes
Extension Package
This feature is being built as an extension package, not as part of the core ADvendio package. This is to avoid adding a large number of fields and objects to the main package, as this functionality is currently specific to a few client's needs.
You can find a list of all created fields on this Wiki page: 8.18.2 Objects and Fields for OBS Extension package
You can find installation links and versioning history on this page: ADvendio Package Extensions | ADvendio EDI Extension
Default and Customizable mapping
We provided a default Mapping for all values mapped between OBS messages and ADvendio. If you need to apply changes to this you will be happy to hear that the mapping is customizable.
Please find more details about our default mapping and customizing it on this Wiki pages: 8.18.3 Default mapping for OBSand 8.18.4 Customization of mapping for OBS Extension
Automation
It might be that many values needed for OBS are values that should be set in the background or based on other information filled in. For this you can leverage the great automation possibilities you gain by working on the Salesforce platform: specifically Flows to update values based on changes.
We are also working on standard flows to predefine certain automation rules already.